There is no DMI support yet in MRST FW. We have a new x86 HW subarch ID in boot_param, then we use it to select x86_init abstractions. Both boot_param and x86_init are x86 arch specific so I guess we can use them in 8042 driver under CONFIG_X86. Not sure if it is possible to move x86 i8042_platform_init under x86_init (the x86 part). >-----Original Message----- >From: Dmitry Torokhov [mailto:dmitry.torokhov@xxxxxxxxx] >Sent: Monday, June 28, 2010 3:45 PM >To: Pan, Jacob jun >Cc: Randy Dunlap; Stephen Rothwell; linux-next@xxxxxxxxxxxxxxx; LKML; >linux-input@xxxxxxxxxxxxxxx; akpm; chuck.lever@xxxxxxxxxx; H. Peter >Anvin >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-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
