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]

Message-ID: <20100923115818.0cac8d06@lxorguk.ukuu.org.uk>
Date:	Thu, 23 Sep 2010 11:58:18 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
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, 23 Sep 2010 11:27:08 +0100
Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote:

> On Thu, Sep 23, 2010 at 11:27:03AM +0100, Alan Cox wrote:
> 
> > > To be honest I'd actually be inclined to go more towards the way the
> > > non-DT embedded platforms have gone and just ignore the data we get
> > > from SFI as much as possible and have board specific initialisation in
> > > code; it's boring and repetitive but it's also clear and *relatively*
> > > robust.
> 
> > And even more unmaintainable. Won't happen.
> 
> So what is the plan for coping with OEM systems?  Right now the code
> makes no provision at all that I can see for system-specific handling
> of the SFI data which seems very optimistic.

There are various system specific drivers which have their own sfi entry
and name. Telling platforms apart is a problem with SFI but the latest
firmware also supports DMI so we can get platform identification via the
normal PC interfaces.

Alan
--
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/