From: Stefan Peter <st3fanp3t3r@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Beaglebone Black support
Date: Sun, 23 Jun 2013 22:02:06 +0200 [thread overview]
Message-ID: <51C7543E.3080402@gmail.com> (raw)
In-Reply-To: <CA+-urNQPUunJ4se0apcfimNRAK4iq1u_mLaCYRvcPJWS6Uq+HQ@mail.gmail.com>
Hi Frank
On 23.06.2013 21:21, Frank Hunleth wrote:
> I just got a Beaglebone Black and wanted to try out Buildroot with it.
> The 3.8 kernel from TI that was referenced in beaglebone_defconfig
> didn't boot all the way for me. I could probably do a better job of
> getting it to work since it looked close, but I was interested in some
> of the cape and PRU code that was in the beaglebone.org kernel
> patches. The good news was that as soon as I applied all of the
> beaglebone.org kernel patches to a plain 3.8.13 kernel, the
> buildroot-built images started booting with the peripherals of
> interest working (minor issues, but it looks promising.)
>
> I'd like to get things in a form that I could contribute upstream and
> I'm not sure how to deal with the kernel. Both "kernels" referenced by
> people on the beageboard mailing lists, the beaglebone.org kernel and
> the Robert J. Nelson kernel, are really a list of patches (100s of
> them) and a shell script to download the 3.8.13 kernel and apply them.
> See here for an example:
>
> https://github.com/beagleboard/kernel/tree/3.8
Getting these patches upstream into Linus kernel is the final solution.
Customers like you putting pressure to do so on TI (or whoever provides
these patches) are the key to reach this target.
Regards
Stefan Peter
next prev parent reply other threads:[~2013-06-23 20:02 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 [this message]
[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
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=51C7543E.3080402@gmail.com \
--to=st3fanp3t3r@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox