[coreboot] [PATCH] RFC: autocreate Kconfig from DTS
Carl-Daniel Hailfinger
c-d.hailfinger.devel.2006 at gmx.net
Fri Aug 22 13:56:41 CEST 2008
On 22.08.2008 08:54, ron minnich wrote:
> On Thu, Aug 21, 2008 at 11:24 PM, Stefan Reinauer <stepan at coresystems.de> wrote:
>
>> Actually running the produced stuff through Kconfig is wrong, because it
>> has nothing to do with user configuration. Instead both Kconfig and the
>> tree parser should produce similar output for the data each of them
>> collects.
>>
>
>
> That's a key point. I agree.
>
I had something like that in an earlier iteration, but I threw it away.
The big problem here are configuration options which are available only
for some targets.
Look at USBDEBUG:
- Some chipsets simply don't support it, so there's no point in offering
it in Kconfig.
- For the chipsets which support USBDEBUG, we may not want to enable it.
- It is conceptually the same as serial console support, so enabling it
unconditionally is bad.
Feeding the dts-produced config variables into Kconfig solves that
problem nicely.
The only other alternative would be to handle this in the dts, but
enabling a certain sort of console is definitely not hardware
description and does not belong in the dts.
One possible cop-out would be to offer all options in Kconfig even if
they are unavailable on the selected hardware. That would allow us to
keep Kconfig and DTS separate.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
More information about the coreboot
mailing list