From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Chuck Ebbert" <cebbert@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PS/2 mouse port missing with kernel >=2.6.19, Sis chipset
Date: Wed, 7 Mar 2007 15:15:29 -0500 [thread overview]
Message-ID: <d120d5000703071215w5d08d2b2ve3519f73bdd39b7e@mail.gmail.com> (raw)
In-Reply-To: <45EF1AAB.40104@redhat.com>
On 3/7/07, Chuck Ebbert <cebbert@redhat.com> wrote:
> We have multiple reports of PS/2 mouse port not being found
> on Sis 630 and 730 chipsets, starting with Fedora kernel 2.6.19:
>
> 2.6.18:
> Jan 19 08:59:39 mtranch kernel: PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M]
> at 0x60,0x64 irq 1,12
> Jan 19 08:59:39 mtranch kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
> Jan 19 08:59:39 mtranch kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
> Jan 19 08:59:39 mtranch kernel: mice: PS/2 mouse device common for all mice
>
> 2.6.19:
> Jan 20 09:22:30 mtranch kernel: PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M]
> at 0x60,0x64 irq 1,12
> Jan 20 09:22:30 mtranch kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
> Jan 20 09:22:30 mtranch kernel: mice: PS/2 mouse device common for all mice
>
> I'm pretty sure Fedora doesn't patch any input code, so I wonder
> if some change was made here that could cause this?
There were some issues with AUX IRQ delivery test that is part of AUX
port probe. They should be fixed in the latest mainline. You might be
inetrested in this commit:
1e4865f8d469b1...
--
Dmitry
prev parent reply other threads:[~2007-03-07 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 20:03 Chuck Ebbert
2007-03-07 20:15 ` Dmitry Torokhov [this message]
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=d120d5000703071215w5d08d2b2ve3519f73bdd39b7e@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®