| 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
| ||
|
Message-ID: <20100923105438.GE25663@rakim.wolfsonmicro.main> Date: Thu, 23 Sep 2010 11:54:39 +0100 From: Mark Brown <broonie@...nsource.wolfsonmicro.com> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: Grant Likely <grant.likely@...retlab.ca>, Alan Cox <alan@...ux.intel.com>, linux-kernel@...r.kernel.org, x86@...nel.org, David Woodhouse <dwmw2@...radead.org>, Thomas Gleixner <tglx@...utronix.de> Subject: Re: [PATCH] x86/mrst: add SFI platform device parsing code On Thu, Sep 23, 2010 at 11:48:45AM +0100, Alan Cox wrote: > > any of this code could ever be made generic. The spec seems to only > > cover the data structure, and relationships between devices seem to be > > left to whatever convention the firmware writer feels like using, or > > am I missing something? > Not really no. It's basically little more than a component and IRQ list. > The GPIO table in 0.8 exposes the GPIO lines a bit more sanely. > In fact all that SFI provides generically pretty much fits into > platform_foo() already because there is so little - or into the I²C or > SPI bus data. I believe the issue here is the handling of things where the functionality Linux needs is implemented over multiple chips so we need a way for the chips to find each other. -- 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