From: Rogan Dawes <rogan@dawes.za.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] RFQ: Makefile cleanup
Date: Thu, 07 Oct 2010 08:27:17 +0200 [thread overview]
Message-ID: <4CAD6845.904@dawes.za.net> (raw)
In-Reply-To: <20101007052250.151801539A0@gemini.denx.de>
On 2010/10/07 7:22 AM, Wolfgang Denk wrote:
> Dear Rogan Dawes,
>
> In message <4CAD569E.3020706@dawes.za.net> you wrote:
>>
>> Keep in mind that the Linux folk are looking for an alternative to the
>> defconfig mess that they have currently.
>>
>> Linus has stated that he will delete all the ARM defconfigs soon.
>
> I think the current Linux approach is focussed on generating single
> kernel images that can be used on as many as possible platforms. This
> is needed for things like building Linux distributions and such.
>
> U-Boot, on the other hand, is very much bound to specific hardware
> configurations, and at least so far (*) we will always need secial
> configurations for each board. This makes a pretty much fundamental
> difference.
>
> (*) We discussed before to auto-configure U-Boot for example based on
> a device tee description of the hardware. But it is still a long way
> to go.
>
> Best regards,
>
> Wolfgang Denk
My understanding of it (although I have not followed it closely) was
that they were looking for a mechanism to specify those things that
should be in the configuration at a high level, that would then lead to
the rest of the dependent items being selected automatically.
So, rather than having a *full* config file (and all the associated
churn as individual settings are changed within the kernel), they would
only have a snippet that selects the specific features for the board,
that would then cascade-select the rest of the settings for a full
kernel config.
That was considered acceptable, afaik.
Rogan
next prev parent reply other threads:[~2010-10-07 6:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 19:54 [U-Boot] RFQ: Makefile cleanup Wolfgang Denk
2010-10-06 20:16 ` Albert ARIBAUD
2010-10-06 20:32 ` Wolfgang Denk
2010-10-06 20:42 ` Scott Wood
2010-10-06 21:19 ` Wolfgang Denk
2010-10-10 15:14 ` Wolfgang Denk
2010-10-10 15:46 ` Wolfgang Denk
2010-10-10 18:24 ` Mike Frysinger
2010-10-10 19:10 ` Wolfgang Denk
2010-10-10 19:57 ` Mike Frysinger
2010-10-10 21:04 ` Wolfgang Denk
2010-10-06 21:21 ` Graeme Russ
2010-10-07 0:46 ` Reinhard Meyer
2010-10-07 5:11 ` Rogan Dawes
2010-10-07 5:22 ` Wolfgang Denk
2010-10-07 6:27 ` Rogan Dawes [this message]
2010-10-07 5:19 ` Wolfgang Denk
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=4CAD6845.904@dawes.za.net \
--to=rogan@dawes.za.net \
--cc=u-boot@lists.denx.de \
/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