From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/7] linux: add option to rely on a bootloader-provided DTB
Date: Fri, 02 Jan 2015 00:15:24 +0100 [thread overview]
Message-ID: <87k3169joz.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20150101231700.75d142fd@free-electrons.com> (Thomas Petazzoni's message of "Thu, 1 Jan 2015 23:17:00 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
> Dear Yann E. MORIN,
> On Thu, 1 Jan 2015 22:58:45 +0100, Yann E. MORIN wrote:
>> However, I beg to disagree on that last part: I think we should have
>> this as an option in Buildroot.
>>
>> The reason is that some platforms can be built with or without support
>> for the device tree. The Raspberry Pi is but one such platform; there
>> are others. Their defconfig do not always enable USE_OF by default, it
>> must be a volunteer selection from the user.
>>
>> In that case, your opinion is to delegate to the user the responsibility
>> to enable that on his own, right? So, it would no longer be possible to
>> use in-tree defconfigs for those boards, for example.
> Well, to me this is a slippery slope. There are gazillions of kernel
> options that do platform-specific stuff. So far, we really tried hard
> to limit how much Buildroot modifies the kernel options, and tried to
> limit that to cases related to userspace components enabled by the user
> that really need some feature in the kernel.
> Let's see what Peter thinks about this, he might very well have a
> different opinion on this.
I must say I'm with Thomas on this one. Let's not fiddle with the kernel
.config unless we really _HAVE_ to.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-01-01 23:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 20:23 [Buildroot] [PATCH 0/7] RPi: enable building a device-tree-enabled kernel (branch yem/rpi-dt) Yann E. MORIN
2015-01-01 20:23 ` [Buildroot] [PATCH 1/7] package/rpi-firmware: bump version Yann E. MORIN
2015-01-01 21:25 ` Thomas Petazzoni
2015-01-01 20:23 ` [Buildroot] [PATCH 2/7] linux: add option to rely on a bootloader-provided DTB Yann E. MORIN
2015-01-01 21:24 ` Thomas Petazzoni
2015-01-01 21:44 ` Yann E. MORIN
2015-01-01 21:51 ` Thomas Petazzoni
2015-01-01 21:58 ` Yann E. MORIN
2015-01-01 22:17 ` Thomas Petazzoni
2015-01-01 22:26 ` Yann E. MORIN
2015-01-01 23:15 ` Peter Korsgaard [this message]
2015-01-01 23:21 ` Yann E. MORIN
2015-01-01 20:23 ` [Buildroot] [PATCH 3/7] docs/manual: document LIBFOO_INSTALL_IMAGES Yann E. MORIN
2015-01-01 21:28 ` Thomas Petazzoni
2015-01-01 20:23 ` [Buildroot] [PATCH 4/7] package/rpi-firmware: only install images Yann E. MORIN
2015-01-01 21:58 ` Thomas Petazzoni
2015-01-01 20:23 ` [Buildroot] [PATCH 5/7] package/rpi-firmware: add DT-aware marking script Yann E. MORIN
2015-01-01 20:23 ` [Buildroot] [PATCH 6/7] package/rpi-firmware: install DTB blobs Yann E. MORIN
2015-01-01 20:23 ` [Buildroot] [PATCH 7/7] package/rpi-firmware: append the DTOK footer for DT-aware kernel Yann E. MORIN
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=87k3169joz.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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