lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdUBq7XUTDrWenNy7tsnvLQdp9H5hUmzqUZ2F6wVUQn21g@mail.gmail.com>
Date:	Fri, 29 Apr 2016 08:44:01 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Gaurav Minocha <gaurav.minocha.os@...il.com>
Cc:	Rob Herring <robh+dt@...nel.org>,
	Frank Rowand <frowand.list@...il.com>,
	Grant Likely <grant.likely@...aro.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Geert Uytterhoeven <geert+renesas@...der.be>,
	Pavel Machek <pavel@....cz>,
	Alison Chaiken <alison_chaiken@...tor.com>
Subject: Re: [PATCH] scripts/dtc: dt_to_config - report kernel config options
 for a devicetree

On Fri, Apr 29, 2016 at 8:39 AM, Gaurav Minocha
<gaurav.minocha.os@...il.com> wrote:
> On Thu, Apr 28, 2016 at 3:32 PM, Rob Herring <robh+dt@...nel.org> wrote:
>> On Thu, Apr 28, 2016 at 4:46 PM, Frank Rowand <frowand.list@...il.com> wrote:
>>> From: Frank Rowand <frank.rowand@...sony.com>
>>>
>>> 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@...ux-m68k.org

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ