From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: Robert Hancock <hancockrwd@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
pjones@redhat.com
Subject: Re: [PATCH] Disable i8042 checks on Intel Apple Macs
Date: Thu, 21 Jan 2010 18:31:53 -0800 [thread overview]
Message-ID: <4B590E19.5080903@gmail.com> (raw)
In-Reply-To: <1264126146.28766.0.camel@localhost.localdomain>
On 01/21/10 18:09, Bastien Nocera wrote:
> On Thu, 2010-01-21 at 17:20 -0800, Justin P. Mattock wrote:
>> On 01/21/10 16:29, Robert Hancock wrote:
> <snip>
>>> cat /sys/bus/pnp/devices/*/id
>>>
>>> and see if any of these are present?
>>>
>>> PNP0303
>>> PNP030b
>>> FJC6000
>>> FJC6001
>>> PNP0f03
>>> PNP0f0b
>>> PNP0f0e
>>> PNP0f12
>>> PNP0f13
>>> PNP0f19
>>> PNP0f1c
>>> SYN0801
>>>
>>
>>
>> both macbook pro, and iMac9,1
>> have:
>> PNP0a08
>> PNP0a03
>
> # cat /sys/bus/pnp/devices/*/id
> PNP0a08
> PNP0a03
> PNP0c02
> APP0001
> PNP0200
> INT0800
> PNP0103
> PNP0c01
> PNP0c04
> PNP0c02
> PNP0b00
>
> On a MacbookAir1,1
>
>
duh!! I only did one device
here's the two machines I have:
iMac9,1
PNP0a08
PNP0a03
PNP0c02
APP0001
PNP0200
PNP0103
PNP0c01
PNP0c04
PNP0c02
PNP0b00
MacBookPro2,2
PNP0a08
PNP0a03
PNP0c02
APP0001
PNP0200
INT0800
PNP0103
PNP0c01
PNP0c04
PNP0c02
PNP0b00
Justin P. Mattock
next prev parent reply other threads:[~2010-01-22 2:30 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 18:23 [PATCH] Disable i8042 checks on Intel Apple Macs Bastien Nocera
2010-01-20 19:14 ` Justin P. Mattock
2010-01-20 19:37 ` Bastien Nocera
2010-01-20 19:54 ` Justin P. Mattock
2010-01-21 0:41 ` Robert Hancock
2010-01-21 1:31 ` Bastien Nocera
2010-01-21 2:19 ` Robert Hancock
2010-01-21 18:55 ` Dmitry Torokhov
2010-01-21 21:39 ` Robert Hancock
2010-01-21 21:42 ` Bastien Nocera
2010-01-21 21:49 ` Justin P. Mattock
2010-01-22 0:29 ` Robert Hancock
2010-01-22 1:20 ` Justin P. Mattock
2010-01-22 2:09 ` Bastien Nocera
2010-01-22 2:30 ` Robert Hancock
2010-01-22 2:53 ` Bastien Nocera
2010-01-22 2:31 ` Justin P. Mattock [this message]
2010-01-21 22:17 ` Dmitry Torokhov
2010-01-22 0:26 ` Robert Hancock
2010-01-22 17:46 ` H. Peter Anvin
2010-01-22 18:15 ` Bastien Nocera
2010-01-22 22:33 ` Robert Hancock
2010-01-22 22:49 ` H. Peter Anvin
2010-01-25 16:34 ` Vojtech Pavlik
2010-01-25 21:32 ` H. Peter Anvin
2010-01-25 22:15 ` Dmitry Torokhov
2010-01-25 22:18 ` H. Peter Anvin
2010-01-25 22:30 ` Dmitry Torokhov
2010-01-25 23:05 ` H. Peter Anvin
2010-01-25 23:28 ` Dmitry Torokhov
2010-01-25 23:31 ` H. Peter Anvin
2010-05-04 17:06 ` Bastien Nocera
2010-05-04 17:23 ` Dmitry Torokhov
2010-05-04 17:37 ` Bastien Nocera
-- strict thread matches above, loose matches on Subject: below --
2010-05-04 17:36 Bastien Nocera
2010-05-04 17:55 ` Pekka Enberg
2010-05-04 18:02 ` Dmitry Torokhov
2010-05-05 9:18 ` Bastien Nocera
2010-05-05 21:27 ` Kyle McMartin
2010-05-12 0:11 Bastien Nocera
2010-05-12 10:51 ` Felipe Contreras
2010-05-12 11:00 ` Felipe Contreras
2010-05-12 17:51 ` 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=4B590E19.5080903@gmail.com \
--to=justinmattock@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pjones@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).