From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] What's the buildroot attitude to u-boot building?
Date: Tue, 18 Mar 2014 06:21:25 +0100 [thread overview]
Message-ID: <20140318062125.772bd2e8@skate> (raw)
In-Reply-To: <87k3cknbyk.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Mon, 24 Feb 2014 09:37:07 +0100, Peter Korsgaard wrote:
> >> While I don't find it particularly pretty, I kind of fail to see what
> >> troubles you think it could cause. Could you give more details about
> >> this?
>
> > I have used buildroot in the past to generate u-boot + MLO and have just
> > ignored these special options, using my u-boot config instead.
>
> > Now I am looking at adding some configs, or working with existing ones, to add
> > SOCFPGA handling. so I wanted to understand why things were done as they are
> > so that I could do a better job.
>
> I've also never used them (and disliked when they got added). Perhaps
> the time has come to deprecate those options?
>
> Anybody disagrees?
I agree that those options are weird. I don't think we should be poking
into the U-Boot header files.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-18 5:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 1:53 [Buildroot] What's the buildroot attitude to u-boot building? Charles Manning
2014-02-21 14:49 ` Grant Edwards
2014-02-21 23:04 ` Thomas Petazzoni
2014-02-22 20:45 ` Grant Edwards
2014-02-23 0:05 ` Mike Zick
2014-02-23 10:18 ` Thomas Petazzoni
2014-02-23 18:50 ` Grant Edwards
2014-02-23 19:56 ` Mike Zick
2014-02-21 23:13 ` Thomas Petazzoni
2014-02-24 1:33 ` Charles Manning
2014-02-24 8:37 ` Peter Korsgaard
2014-03-18 5:21 ` Thomas Petazzoni [this message]
2014-03-18 8:05 ` Peter Korsgaard
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=20140318062125.772bd2e8@skate \
--to=thomas.petazzoni@free-electrons.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