linux-kernel - Re: RFC: build config via DT names

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: <1b395f6c-5a07-6f44-3b16-7a06a273e291@gmx.de>
Date:   Tue, 13 Feb 2018 13:16:59 +0000
From:   "Enrico Weigelt, metux IT consult" <metux@....de>
To:     Frank Rowand <frowand.list@...il.com>
Cc:     linux-kernel@...r.kernel.org,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: RFC: build config via DT names

On 12.02.2018 23:24, Frank Rowand wrote:

> There is a tool to aid this process: scripts/dtc/dt_to_config.  It is not
> a 100% solution, but it is very helpful.
> 
> The problem is difficult enough that this tool led to a conference talk.
> The slides are at https://elinux.org/images/5/50/Dt_debugging_part_2.pdf
> which is linked to from
> https://elinux.org/Device_Tree_presentations_papers_articles#linux_kernel_configuration

I believe my approach can make this much simpler, at least for most
drivers: the maintainers would explicitly add proper config flags,
instead of letting the tool guess it.

Of course, it would take some amount of work to do that for all drivers,
but we could do that step by step.


--mtx