linux-kernel - Re: [RFC] [PATCH] Device Tree on ARM platform

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]

Date:	Mon, 1 Jun 2009 08:37:32 +0000 (UTC)
From:	Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux-arm-kernel@...ts.arm.linux.org.uk
Subject:  Re: [RFC] [PATCH] Device Tree on ARM platform

Kyle Moffett wrote:

> On Sat, May 30, 2009 at 7:22 AM, Pavel Machek <pavel@....cz> wrote:
>>> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig index
>>> f430e15..b0ee851 100644
>>> --- a/arch/arm/Kconfig
>>> +++ b/arch/arm/Kconfig
>>> @@ -158,6 +158,17 @@ config ARCH_MTD_XIP
>>>  config GENERIC_HARDIRQS_NO__DO_IRQ
>>>       def_bool y
>>>
>>> +config OF
>>> +        def_bool y
>>> +
>>> +config PROC_DEVICETREE
>>> +        bool "Support for device tree in /proc"
>>
>> It certainly should not be in /proc.
> 
> There is unfortunately a relatively large legacy base of existing tools

And the keyword is *legacy* IMO. We have had legacy things like /proc/acpi,
/proc/ide etc. for years. However one by one they are being dropped and
replaced with more vivid interfaces. IMO one shouldn't hang around legacy
things for years. Just define and implement the replacement and delcare
that legacy interface will fade out and will be removed in a year or two.



With best wishes
Dmitry


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/