From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Pan, Jacob jun" <jacob.jun.pan@intel.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
akpm <akpm@linux-foundation.org>,
"chuck.lever@oracle.com" <chuck.lever@oracle.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: problem: Re: [PATCH] input: fixup X86_MRST selects
Date: Mon, 28 Jun 2010 15:44:40 -0700 [thread overview]
Message-ID: <20100628224440.GA19087@core.coreip.homeip.net> (raw)
In-Reply-To: <43F901BD926A4E43B106BF17856F0755EA339079@orsmsx508.amr.corp.intel.com>
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
next prev parent reply other threads:[~2010-06-28 22:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 3:34 linux-next: Tree for June 9 Stephen Rothwell
2010-06-09 17:36 ` linux-next: Tree for June 9 (niu) Randy Dunlap
2010-06-09 18:06 ` David Miller
2010-06-09 18:08 ` Randy Dunlap
2010-06-09 22:44 ` [PATCH 1/2 -next] of_device.h: provide struct of_device even when not enabled Randy Dunlap
2010-06-09 23:47 ` Grant Likely
2010-06-09 23:47 ` Grant Likely
2010-06-09 22:44 ` [PATCH 2/2 -next] niu: always include of_device.h Randy Dunlap
2010-06-09 23:45 ` Grant Likely
2010-06-10 0:29 ` David Miller
2010-06-09 22:29 ` [PATCH] input: fixup X86_MRST selects Randy Dunlap
2010-06-09 22:40 ` Dmitry Torokhov
2010-06-09 22:42 ` Randy Dunlap
2010-06-10 19:04 ` Dmitry Torokhov
2010-06-15 15:17 ` Randy Dunlap
2010-06-28 19:03 ` problem: " Randy Dunlap
2010-06-28 20:18 ` Dmitry Torokhov
2010-06-28 20:23 ` Randy Dunlap
2010-06-28 21:12 ` Pan, Jacob jun
2010-06-28 22:44 ` Dmitry Torokhov [this message]
2010-06-28 23:22 ` Pan, Jacob jun
2010-07-02 4:46 ` Dmitry Torokhov
2010-07-02 6:27 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100628224440.GA19087@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chuck.lever@oracle.com \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@intel.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.