From: Vojtech Pavlik <vojtech@suse.cz>
To: Dmitry Torokhov <dtor@insightbb.com>
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 01:44:23 +0200 [thread overview]
Message-ID: <20060727234423.GC4907@suse.cz> (raw)
In-Reply-To: <200607270029.05066.dtor@insightbb.com>
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).
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.
Btw, on standard x86, the AUX and KBD IRQs cannot be shared.
> --
> Dmitry
>
> Input: i8042 - get rid of polling timer
>
> Remove polling timer that was used to detect keybord/mice hotplug and
> register both IRQs right away instead of waiting for a driver to
> attach to a port. If mouse is really missing and IRQ can be used for
> something else user can boot with i8042.noaux.
--
Vojtech Pavlik
Director SuSE Labs
next prev parent reply other threads:[~2006-07-27 23:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 4:29 [RFC/RFT] Remove polling timer from i8042 Dmitry Torokhov
2006-07-27 23:44 ` Vojtech Pavlik [this message]
2006-07-28 12:57 ` Dmitry Torokhov
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=20060727234423.GC4907@suse.cz \
--to=vojtech@suse.cz \
--cc=davej@redhat.com \
--cc=dtor@insightbb.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 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.