linux-kernel - Re: [PATCH] x86/mrst: add SFI platform device parsing code

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:	Wed, 22 Sep 2010 16:39:44 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Grant Likely <grant.likely@...retlab.ca>,
	Alan Cox <alan@...ux.intel.com>, linux-kernel@...r.kernel.org,
	x86@...nel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] x86/mrst: add SFI platform device parsing code

On Wed, Sep 22, 2010 at 04:35:17PM +0100, David Woodhouse wrote:
> On Wed, 2010-09-22 at 16:33 +0100, Mark Brown wrote:

> > This is roughly what it's doing except that it's going to native Linux
> > bus types and platform data rather than to device tree.

> It still means that drivers for chips which are seen both on this
> bizarre abomination and also on other machines which use a device-tree
> will need to support *both* probe types.

No, the drivers don't see any of this but instead someone has to
write (and maintain) explicit code to do the translation in arch/x86
outside the drivers.  The drivers just see platform data and regular bus
probes which they'll be doing anyway until such time as device tree is
well enough established for people to stop doing platform data.
--
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/