From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Beaglebone Black support
Date: Tue, 02 Jul 2013 23:43:02 +0200 [thread overview]
Message-ID: <87d2r0sknt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20130702071112.d2bed52344e1786c14494b36@lavabit.com> (rh's message of "Tue, 2 Jul 2013 07:11:12 -0700")
>>>>> "rh" == rh <richard_hubbe11@lavabit.com> writes:
rh> On Tue, 2 Jul 2013 09:34:15 +0200
rh> Thomas Petazzoni <thomas.petazzoni-wi1
rh> +55ScJUtKEb57/3fJTNBPR1lH4CV8 at public.gmane.org> wrote:
rh> --8<--
>> To handle such a bizarre stuff, I don't see any other option that
>> adding a new kconfig option to specify a shell script to be executed
>> at "patch" time of the kernel, so that one can do whatever funky
>> things (s)he wants. That's ugly, but I don't see a nice and generic
>> way of handling such a bizarre distribution of kernel code.
rh> It's not a good situation. 3.8 kernel is EOL and it seems that TI
rh> has no resources to get the code upstream.
Well, things are moving - Just not always as fast as you could hope. TI
is certainly not the worst vendor, but we're not there yet for am335x.
I think the best way forward in the short term would be if somebody
would maintain a git tree containing the kernel sources and Koen's patch
set applied on top, and once in a while sync / send a patch to buildroot
to update the git revision the bbb config uses.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-07-02 21:43 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
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 [this message]
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=87d2r0sknt.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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