| 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: <20100628224440.GA19087@core.coreip.homeip.net> Date: Mon, 28 Jun 2010 15:44:40 -0700 From: Dmitry Torokhov <dmitry.torokhov@...il.com> To: "Pan, Jacob jun" <jacob.jun.pan@...el.com> Cc: Randy Dunlap <randy.dunlap@...cle.com>, Stephen Rothwell <sfr@...b.auug.org.au>, "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, "linux-input@...r.kernel.org" <linux-input@...r.kernel.org>, akpm <akpm@...ux-foundation.org>, "chuck.lever@...cle.com" <chuck.lever@...cle.com>, "H. Peter Anvin" <hpa@...or.com> Subject: Re: problem: Re: [PATCH] input: fixup X86_MRST selects On Mon, Jun 28, 2010 at 02:12:03PM -0700, Pan, Jacob jun wrote: > > > We do intend to maintain binary compatibility between generic kernel and Moorestown. > I guess the challenge is not having enumeration of i8042 pass to the driver. Do you > prefer abort i8042_platform_init() based on #define CONFIG_X86_MRST? It is no safe > to probe HW on Moorestown, unfortunately. Any check based on CONFIG_X86_MRST means that kernel is not generic. We'd need a runtime check (but not necessarily one that bangs ports). Is there something in processor flags, or DMI, or similar that woudl allow i8042 to see that it runs on Moorestown? -- Dmitry -- 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