From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] boot: only show vendor-specific bootloaders for applicable arm variant
Date: Thu, 02 Feb 2012 17:11:03 +0100 [thread overview]
Message-ID: <87ehud9pwo.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20120202170059.42c7b05e@skate> (Thomas Petazzoni's message of "Thu, 2 Feb 2012 17:00:59 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Le Thu, 02 Feb 2012 16:56:25 +0100,
Thomas> Peter Korsgaard <jacmet@uclibc.org> a ?crit :
>> True. Is that a common use case? If so then I'll revert.
Thomas> I don't know if it's a common use case. But I would suspect that many
Thomas> newcomers do not necessarily select the right sub-architecture. But I
Thomas> don't have a strong opinion with your regard to your patch. I just
Thomas> think that people may not discover that those bootloaders are available
Thomas> in Buildroot.
If that's the case, then we have the same problems with SoC specific
packages like gst-dsp or armv7 only things like valgrind.
Thomas> However, as discussed on IRC, we might see an increase of
Thomas> platform-specific packages (3D drivers and libraries, codecs
Thomas> and DSP stuff, etc.), so maybe we'll need some way of selecting
Thomas> the platform in order to show only the relevant packages? Or
Thomas> maybe simply by organizing the packages like:
Thomas> Platform specific packages ->
Thomas> Texas Instruments OMAP packages ->
Thomas> Freescale i.MX packages ->
Thomas> ...
Yes, I guess something like that is needed. We should make sure we don't
make it too complicated though.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-02-02 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 22:46 [Buildroot] [git commit] boot: only show vendor-specific bootloaders for applicable arm variant Peter Korsgaard
2012-02-02 15:47 ` Thomas Petazzoni
2012-02-02 15:56 ` Peter Korsgaard
2012-02-02 16:00 ` Thomas Petazzoni
2012-02-02 16:11 ` Peter Korsgaard [this message]
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=87ehud9pwo.fsf@macbook.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