Re: KConfig and DTS files

[Eric Nelson <eric.nelson-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>]

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.

I've heard (and appreciate) the pointers about how to get
past our current issue(s), but what's the rationale
for not allowing the inclusion of autoconf.h and
conditionals in the DTS?

Is it a concern that things will become polluted and
hard to read?

Please advise,


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