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.212730.183576278.davem@davemloft.net>
Date:	Wed, 27 May 2009 21:27:30 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	david@...son.dropbear.id.au
Cc:	linux@....linux.org.uk, jonsmirl@...il.com,
	devicetree-discuss@...abs.org, linux-kernel@...r.kernel.org,
	timur@...escale.com, scottwood@...escale.com,
	yuan-bo.ye@...orola.com, linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: [RFC] [PATCH] Device Tree on ARM platform

From: David Gibson <david@...son.dropbear.id.au>
Date: Thu, 28 May 2009 12:52:58 +1000

> The of_platform bus model is conceptually completely broken, but in
> practice only slightly broken for all common cases.

The fact that every single SBUS and EBUS driver for sparc is now an
of_platform driver, and the fact that as a further result joint
SBUS/PCI drivers are now almost completely unified, speaks volumes to
the fact that it is not broken.

Yes, you'll have some non-shared probing code, one to fetch the
resources from PCI/platform_device/whatever and one for of_device.

But, I say big deal.

The rest remains entirely unified, even the DMA calls are all the
same in unified SBUS/EBUS/PCI device drivers.  It just works.
--
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/