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
| ||
|
Date: Sat, 30 May 2009 21:29:56 -0400 From: Kyle Moffett <kyle@...fetthome.net> To: Pavel Machek <pavel@....cz> Cc: Janboe Ye <yuan-bo.ye@...orola.com>, linux-arm-kernel@...ts.arm.linux.org.uk, linux-kernel@...r.kernel.org, jwboyer@...ux.vnet.ibm.com, grant.likely@...retlab.ca, paulus@...ba.org, rmk@....linux.org.uk Subject: Re: [RFC] [PATCH] Device Tree on ARM platform 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 which depend on the device-tree (specifically, the representation of the OF device tree that the kernel generates at boot-time) present in proc, especially on platforms (PowerPC/Sparc) which have a real OpenFirmware implementation. On the other hand, since this is a new port, we can just assume that (for this port) we're going to fix the tools to use a different path. Cheers, Kyle Moffett -- 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/
Powered by blists - more mailing lists