All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Gyarmati <mr.zoltan.gyarmati@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Beaglebone Black support
Date: Mon, 01 Jul 2013 12:10:40 +0200	[thread overview]
Message-ID: <51D155A0.3010205@gmail.com> (raw)
In-Reply-To: <20130624124933.e7983d6a3730922581985bf4@lavabit.com>

On 06/24/2013 09:49 PM, rh wrote:
> On Mon, 24 Jun 2013 08:22:56 -0400
> Frank Hunleth
> <fhunleth@troodon-software.com> wrote:
>
>> If you'd like to try out my repository for the BBB, feel free to look
>> at:
>>
>> https://github.com/fhunleth/buildroot-bbb
>>
>> I don't have much in the line of instructions right now, but it should
>> build for you. Check out the bbb branch and run "make
>> beagleboneblack_defconfig" and make. I can run the images from both a
>> microSD card and eMMC, and things seem to be coming up.
> Thanks for sharing!  You're way more organized than I am.
> Mine is not ready for prime-time, I'm not sure if it even boots.
> I don't have a working serial cable yet.
>
>> Also, I just put in the PRU's PASM assembler and interface libraries.
>> I haven't checked it out yet except that it builds and can assemble
>> the examples.
>>
>>>> The point of my email is just that the
>>>> github.com/beagleboard/kernel repository is not in a form that
>>>> nicely integrates with buildroot due to it just containing patches
>>>> for a Linux kernel. I'm just looking for pointers on how best to
>>>> handle this.
>>> I think the answer is in the other reply, but I'm not sure yet.
>>> From the brief time I've used buildroot it seems flexible enough to
>>> allow pulling stuff from lots of places.
>> Despite using br for the past few years on a handful of projects, it
>> seems like every time I update my tree that I learn about a few new
>> features.
> Buildroot has lots of possibilities for sure. I'm used to building kernels
> but the BBB and buildroot adds a new level of complexity for me.
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot


Hello,

checked the linked config from fhunleth, it seems in the used kernel
tree (
http://files.troodon-software.com/br/beagleboard-kernel-b37928553c8de3598d8a259d7ce5c4be713c2908.tar.xz
), the usb and the ethernet support is broken (or, as it always
possible, i failed something).
 So to get a working kernel, i used the patchset from
https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.8 ,
( which patches are extracted from the Angstrom build tree ), applied
them manually on the mainline tree, created a tarball, and used that to
build with Buildroot.
So far everything works well (UART,USB host/gadget, ethernet, GPIO
tested). I wondering, would it be possible to apply those subdir-style (
https://github.com/RobertCNelson/linux-dev/tree/am33x-v3.8/patches )
patches automatically in Buildroot on an elegant way? Or better to
create a git tree with applied patches somewhere online and use that in
Buildroot?

Thanks, best regards,
zgyarmati



-- 
br, 
Zoltan Gyarmati
mail: mr.zoltan.gyarmati at gmail.com
freenode nick: zgyarmati

  parent reply	other threads:[~2013-07-01 10:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-23 19:21 [Buildroot] Beaglebone Black support Frank Hunleth
2013-06-23 20:02 ` Stefan Peter
     [not found] ` <20130623161357.136be827bdb312f43bda51a6@lavabit.com>
2013-06-23 23:23   ` Charles Krinke
2013-06-24  3:30   ` Frank Hunleth
2013-06-24  4:28     ` Baruch Siach
2013-06-24 12:07       ` Frank Hunleth
     [not found]     ` <20130623214133.6249f43e6e2d8bda20aa971a@lavabit.com>
2013-06-24 12:22       ` Frank Hunleth
     [not found]         ` <20130624124933.e7983d6a3730922581985bf4@lavabit.com>
2013-07-01 10:10           ` Zoltan Gyarmati [this message]
2013-07-01 13:21             ` Frank Hunleth
2013-07-02  6:07             ` Arnout Vandecappelle
2013-07-02  7:34               ` Thomas Petazzoni
2013-07-02 16:46                 ` Arnout Vandecappelle
     [not found]                 ` <20130702071112.d2bed52344e1786c14494b36@lavabit.com>
2013-07-02 21:43                   ` Peter Korsgaard
2013-07-03 11:54                     ` Frank Hunleth
2013-07-03 13:45                       ` Peter Korsgaard
2013-07-04  8:16                         ` Zoltan Gyarmati
2013-07-07  1:07                           ` Frank Hunleth
2013-06-24 16:54 ` Arnout Vandecappelle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51D155A0.3010205@gmail.com \
    --to=mr.zoltan.gyarmati@gmail.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.