From: Balaji Rao <balajirrao@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Yanko Kaneti <yaneti@declera.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@elte.hu, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.25-rc5.git4 regression PS/2 mouse not detected/working
Date: Wed, 2 Apr 2008 23:00:13 +0530 [thread overview]
Message-ID: <200804022300.14164.balajirrao@gmail.com> (raw)
In-Reply-To: <20080402113043.ZZRA012@mailhub.coreip.homeip.net>
On Wednesday 02 April 2008 09:03:28 pm Dmitry Torokhov wrote:
> Hi Blaji,
>
> On Wed, Apr 02, 2008 at 08:38:33PM +0530, Balaji Rao wrote:
> >
> > Coincidentally even I hit upon this bug a couple of days ago after enabling
> > HPET in my BIOS. A quick check told me that IRQ 12 which the patch assigns to
> > the HPET device is used by the PS/2 mouse as well. This makes the mouse
> > inactive.
> >
> > I am working on this.. I am not sure if the PS/2 code is misbehaving though..
> >
>
> Normally IRQ12 can not be shared on X86 if PS/2 mouse is present.
> If PCI side tries to grab the IRQ then ISA (legacy) side will never
> see its interrupts coming.
>
OK. So, I need to specifically check for IRQ12 being assigned and avoid it ?
--
regards,
balaji rao
Dept. of Mechanical Engineering,
National Institute of Technology Karnataka, India
next prev parent reply other threads:[~2008-04-02 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1205775229.25146.11.camel@indigo.declera.com>
2008-03-17 18:55 ` 2.6.25-rc5.git4 regression PS/2 mouse not detected/working Dmitry Torokhov
2008-03-17 18:58 ` Yanko Kaneti
2008-03-18 15:54 ` Dmitry Torokhov
2008-03-19 8:35 ` Yanko Kaneti
2008-04-01 23:17 ` Yanko Kaneti
2008-04-02 14:59 ` Dmitry Torokhov
2008-04-02 15:08 ` Balaji Rao
2008-04-02 15:33 ` Dmitry Torokhov
2008-04-02 17:30 ` Balaji Rao [this message]
2008-04-02 17:44 ` 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=200804022300.14164.balajirrao@gmail.com \
--to=balajirrao@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yaneti@declera.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).