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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090527.170234.69075052.davem@davemloft.net>
Date:	Wed, 27 May 2009 17:02:34 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	scottwood@...escale.com
Cc:	r.schwebel@...gutronix.de, grant.likely@...retlab.ca,
	devicetree-discuss@...abs.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk, yuan-bo.ye@...orola.com,
	timur@...escale.com, rmk@....linux.org.uk
Subject: Re: [RFC] [PATCH] Device Tree on ARM platform

From: Scott Wood <scottwood@...escale.com>
Date: Wed, 27 May 2009 18:58:24 -0500

> Because it's better to have a little platform specific code than a lot
> of it?

Judging by some of the questions I see popping up over and over again,
I suspect that many people resisting OF device trees lack much of an
understanding of what they provide and can do.

Questions like "How do we determine attribute X of a given device" has
an obvious answer if you understand device node properties and that
you can encode arbitrary things into them to provide arbitrary bits of
information on a per-device-instance basis.
--
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/