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]

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

From: Robert Schwebel <r.schwebel@...gutronix.de>
Date: Thu, 28 May 2009 01:48:01 +0200

> My impression is that oftree only works in a perfect world. But we
> don't have one, so the fundamental design decision is broken.

It is imperfect, that's why it all determined by software we
control and thus we can fix.  _THAT_ is the whole point.

Bringing up SMSC over and over again is just a scarecrow.  So
one driver went insanely bad and if an ifdef platform specific
hacks nightmare, big deal.

That has no bearing on whether OF device trees constructed by
bootloader software or onboard firmware is a good idea or not.
--
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/