On Fri, Apr 29, 2016 at 8:39 AM, Gaurav Minocha
<gaurav.minocha.os@xxxxxxxxx> wrote:
> On Thu, Apr 28, 2016 at 3:32 PM, Rob Herring <robh+dt@xxxxxxxxxx> wrote:
>> On Thu, Apr 28, 2016 at 4:46 PM, Frank Rowand <frowand.list@xxxxxxxxx> wrote:
>>> From: Frank Rowand <frank.rowand@xxxxxxxxxxx>
>>>
>>> Determining which kernel config options need to be enabled for a
>>> given devicetree can be a painful process. Create a new tool to
>>> find the drivers that may match a devicetree node compatible,
>>> find the kernel config options that enable the driver, and
>>> optionally report whether the kernel config option is enabled.
>>
>> I would find this more useful to output a config fragment with all the
>> options enabled. The hard part there is enabling the options a given
>> option is dependent on which I don't think kbuild takes care of.
>
> Do you mean to generate something like .config? If yes, then IMO it would
> not be a correct configuration file.
A fragment to be appended to your current .config.
After that, an additional run of "make oldconfig" should (hopefully) bring
everything into good shape.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
