From: Eric Nelson <eric.nelson-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
To: Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>
Cc: Bjorn Andersson <bjorn-UYDU3/A3LUY@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: KConfig and DTS files
Date: Thu, 08 May 2014 08:06:46 -0700 [thread overview]
Message-ID: <536B9D86.3020806@boundarydevices.com> (raw)
In-Reply-To: <20140508115532.GJ28159-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
Hi Jason,
On 05/08/2014 04:55 AM, Jason Cooper wrote:
> On Wed, May 07, 2014 at 04:06:49PM -0700, Eric Nelson wrote:
>> Hi Bjorn,
>>
>> On 05/07/2014 03:20 PM, Bjorn Andersson wrote:
>>> On Wed, May 7, 2014 at 12:52 PM, Eric Nelson
>>> <eric.nelson-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org> wrote:
>>> [...]
>>>>
>>>> I still wonder about the choice of not allowing inclusion
>>>> of at least include/generated/autoconf.h.
>>>
>>> Because what you just showed is the use case where you have 1 defconfig, build 1
>>> zImage and then you can have a completely separate delivery of X number of
>>> dtbs, all defining some variant of your original board.
>>> All without recompiling, or even have the source available.
>>>
>>
>> I agree that there's some benefit in being able to generate
>> different DTBs, and it's an advantage (size, speed) to customize
>> the .config as well.
>>
>> When those clearly go together, it seems natural to define them as
>> such.
>
> But they don't. The end goal is that the dtb and the Linux kernel
> _aren't_ tied together. The dtb is shipped with the board, and you
> configure/build your kernel how you want, and boot it.
>
> Look at the dtb as replacement for the mach-type or boardid number.
> It's handed to the OS (not necessarily Linux) by the bootloader to say
> "Here's what you're running on". It's *not* a reflection of the
> configuration of the Linux Kernel. The dtb describes the hardware for a
> specific board. Nothing more, nothing less.
>
Therein lies the rub...
In these days of SOCs with pin-muxing, a single description of
"the board" is overly simplistic.
> Several other projects use the dts files from the kernel tree. Ian
> Campbell even set up a filter-branch version of the dts files and the
> binding docs so that other projects could clone that repo without
> getting the entire Linux commit history. If we tied the dts files to
> Kconfig symbols, we'd make other projects lives much more difficult.
> Not to mention possibly driving Ian to drink excessively. :)
>
Again, this highlights differing goals.
My original question stemmed from a **desire** for customized
DTBs to reflect customization of a board. We have dozens
of custom and semi-custom versions of our tying these parts
together would make things a bit easier.
Regards,
Eric
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-08 15:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 17:12 KConfig and DTS files Eric Nelson
[not found] ` <536A697D.3020002-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
2014-05-07 17:24 ` Olof Johansson
[not found] ` <CAOesGMiHRQV+XngH4ABSeT8KDeP=iKn1ogvTA0j1BdyBwAaWSA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-07 17:47 ` Eric Nelson
[not found] ` <536A71AF.1010907-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
2014-05-07 17:55 ` Olof Johansson
[not found] ` <CAOesGMhMeLkzEeVKHM2G9Vqth6qypURN6mxbNdySVvKhQBCs5A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-08 3:25 ` Maxime Ripard
2014-05-08 6:57 ` David Gibson
2014-05-07 18:10 ` Arnd Bergmann
2014-05-07 18:35 ` Eric Nelson
[not found] ` <536A7CE0.6070005-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
2014-05-07 18:38 ` Arnd Bergmann
2014-05-07 19:07 ` Eric Nelson
[not found] ` <536A8456.1040208-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
2014-05-07 19:15 ` Arnd Bergmann
2014-05-07 19:52 ` Eric Nelson
[not found] ` <536A8F03.5070509-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
2014-05-07 22:20 ` Bjorn Andersson
[not found] ` <CAJAp7OjNdmsomhm9jJ9-jP01z1Uz9snVgRCD07zOFdMYAhQ6Lw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-07 23:06 ` Eric Nelson
[not found] ` <536ABC89.8060301-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
2014-05-08 10:37 ` Arnd Bergmann
2014-05-08 14:56 ` Eric Nelson
2014-05-08 11:55 ` Jason Cooper
[not found] ` <20140508115532.GJ28159-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2014-05-08 15:06 ` Eric Nelson [this message]
2014-05-07 18:01 ` Jason Cooper
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=536B9D86.3020806@boundarydevices.com \
--to=eric.nelson-q5rjgjkts06cy9shamctrueocmrvltnr@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=bjorn-UYDU3/A3LUY@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.