From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Bastien Nocera <hadess@hadess.net>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org
Subject: Re: [git pull] Input updates for 2.6.34-rc6
Date: Thu, 13 May 2010 21:15:32 +0100 [thread overview]
Message-ID: <20100513201532.GA20473@srcf.ucam.org> (raw)
In-Reply-To: <20100513155031.GA22238@core.coreip.homeip.net>
On Thu, May 13, 2010 at 08:50:31AM -0700, Dmitry Torokhov wrote:
> Indeed most of them do just work. My Dell T110 for example boots just
> fine and it only has USB, no PS/2 ports. However there is a rather
> important difference I think - these other boxes are supposed to work
> with multiple versions of Windows which, as far as I know, do probe for
> the i8042. Apple only supports bootcamp on certain BIOSes and does not
> really expect anything to touch these ports.
If you're not using bootcamp then you're booting via EFI, and in that
case I think it's probably reasonable to require that the keyboard be
provided via PNP or flagged in the XDST.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-05-13 20:15 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 7:57 [git pull] Input updates for 2.6.34-rc6 Dmitry Torokhov
2010-05-13 14:35 ` Linus Torvalds
2010-05-13 14:47 ` Bastien Nocera
2010-05-13 15:04 ` Linus Torvalds
2010-05-13 15:19 ` Linus Torvalds
2010-05-13 15:50 ` Dmitry Torokhov
2010-05-13 16:16 ` Linus Torvalds
2010-05-13 16:38 ` Randy Dunlap
2010-05-13 20:15 ` Matthew Garrett [this message]
2010-05-13 16:01 ` Dmitry Torokhov
2010-05-13 16:54 ` Linus Torvalds
2010-05-13 16:58 ` Linus Torvalds
2010-05-13 17:16 ` Dmitry Torokhov
2010-05-13 17:30 ` Linus Torvalds
2010-05-13 18:10 ` Dmitry Torokhov
2010-05-13 19:55 ` Linus Torvalds
2010-05-14 7:56 ` Eric W. Biederman
2010-05-14 14:54 ` Linus Torvalds
2010-05-14 15:38 ` Matthew Garrett
2010-05-14 15:42 ` Linus Torvalds
2010-05-14 15:49 ` Matthew Garrett
2010-05-20 4:53 ` Len Brown
[not found] ` <alpine.LFD.2.00.1005131232350.3711@i5.linux-foundation.org>
2010-05-13 21:05 ` Dmitry Torokhov
2010-05-13 21:21 ` Linus Torvalds
2010-05-13 23:39 ` Matthew Garrett
2010-05-20 4:56 ` Len Brown
2010-05-20 7:08 ` Dmitry Torokhov
2010-05-27 6:22 ` Robert Hancock
2010-05-27 6:43 ` Dmitry Torokhov
2010-05-27 17:06 ` Linus Torvalds
2010-05-27 23:03 ` Robert Hancock
2010-05-28 0:46 ` Linus Torvalds
2010-05-28 1:03 ` Dmitry Torokhov
2010-05-28 4:05 ` Robert Hancock
2010-05-28 5:10 ` Dmitry Torokhov
2010-05-14 14:55 ` Matthew Garrett
2010-05-14 15:16 ` Linus Torvalds
2010-05-14 16:28 ` Dmitry Torokhov
2010-05-14 18:47 ` david
2010-05-14 18:49 ` Matthew Garrett
2010-05-14 18:55 ` david
2010-05-14 18:59 ` Matthew Garrett
2010-05-14 19:05 ` david
2010-05-28 2:38 ` Mike Frysinger
2010-08-04 6:20 ` Dmitry Torokhov
2010-08-04 6:29 ` Dmitry Torokhov
2010-05-14 16:29 ` Dmitry Torokhov
2010-05-14 16:35 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2010-05-05 6:41 Dmitry Torokhov
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=20100513201532.GA20473@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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.