From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Aleksey Gorelov <Aleksey_Gorelov@Phoenix.com>
Cc: Greg KH <greg@kroah.com>, Alexandre Oliva <aoliva@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Vojtech Pavlik <vojtech@suse.cz>,
Dmitry Torokhov <dtor_core@ameritech.net>
Subject: RE: forcing PS/2 USB emulation off
Date: Thu, 21 Oct 2004 10:35:17 +0100 [thread overview]
Message-ID: <1098351305.17095.6.camel@localhost.localdomain> (raw)
In-Reply-To: <5F106036E3D97448B673ED7AA8B2B6B3017FC327@scl-exch2k.phoenix.com>
On Iau, 2004-10-21 at 00:22, Aleksey Gorelov wrote:
> Isn't this interrupt disabled at that point, and status are cleared
> right
> after handoff ? Have you actually been able to see a problem with such
> an interrupt with this patch applied ?
I've seen one Nvidia case where flipping the USB over caused an
immediate IRQ on that line.
next prev parent reply other threads:[~2004-10-21 10:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 23:22 forcing PS/2 USB emulation off Aleksey Gorelov
2004-10-21 9:35 ` Alan Cox [this message]
2004-10-21 16:48 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2004-10-21 20:47 Aleksey Gorelov
[not found] <mailman.1098042300.20451.linux-kernel2news@redhat.com>
2004-10-21 6:26 ` Pete Zaitcev
2004-10-17 19:34 Alexandre Oliva
2004-10-17 22:57 ` Greg KH
2004-10-18 18:22 ` Alexandre Oliva
2004-10-20 19:54 ` Alan Cox
2004-10-18 3:48 ` Dmitry Torokhov
2004-10-18 16:45 ` Greg KH
2004-10-18 18:31 ` Alexandre Oliva
2004-10-20 19:55 ` Alan Cox
2004-10-21 16:45 ` Alexandre Oliva
2004-10-19 6:30 ` Vojtech Pavlik
2004-10-19 6:48 ` Dmitry Torokhov
2004-10-20 4:05 ` Dmitry Torokhov
2004-10-20 19:56 ` Alan Cox
2004-10-21 6:21 ` Vojtech Pavlik
2004-10-21 17:53 ` Tim Hockin
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=1098351305.17095.6.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Aleksey_Gorelov@Phoenix.com \
--cc=aoliva@redhat.com \
--cc=dtor_core@ameritech.net \
--cc=greg@kroah.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