From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Vojtech Pavlik" <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org, "Dave Jones" <davej@redhat.com>
Subject: Re: [RFC/RFT] Remove polling timer from i8042
Date: Fri, 28 Jul 2006 08:57:31 -0400 [thread overview]
Message-ID: <d120d5000607280557w2aa476b2y45d8cfc866296adf@mail.gmail.com> (raw)
In-Reply-To: <20060727234423.GC4907@suse.cz>
On 7/27/06, Vojtech Pavlik <vojtech@suse.cz> wrote:
> On Thu, Jul 27, 2006 at 12:29:04AM -0400, Dmitry Torokhov wrote:
> > Hi,
> >
> > OK, I had it in works for quite some time and Dave's talk in Ottawa
> > made me finish it ;)
>
> Good work.
>
> However I believe you need to test the AUX IRQ in this case before you
> use it, otherwise you'll have a lot of people with non-working keyboards
> (the input queue is shared), and probably also non-working PCI cards
> (BIOSes like to assign IRQ12 to PCI if no mouse is detected by the
> BIOS).
>
What do you mean by testing AUX IRQ? Use I8042_CMD_AUX_LOOP to see if
interrupt fires off? The new code releases IRQ if it can't find a
working AUX port...
> You'll see whether this test is necessary if a lot of people report
> problems without i8042.noaux.
>
> That can only be seen after extensive testing on a lot of machines,
> though. Fortunately 386's and 486's are more or less extinct now, and
> with them a lot of the weirder keyboard controllers.
>
I think I will forward the patch to Andrew and we will see how bad it
is. It works on couple of boxes here but I don't have a lot of
hardware to test on...
--
Dmitry
next prev parent reply other threads:[~2006-07-28 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 4:29 Dmitry Torokhov
2006-07-27 23:44 ` Vojtech Pavlik
2006-07-28 12:57 ` Dmitry Torokhov [this message]
2006-07-28 13:32 ` Vojtech Pavlik
2006-07-28 14:20 ` Dmitry Torokhov
2006-07-28 20:27 ` Vojtech Pavlik
2006-07-31 2:33 ` [RFC/RFT] Remove polling timer from i8042 - V2 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=d120d5000607280557w2aa476b2y45d8cfc866296adf@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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
Powered by JetHome