public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Pete Zaitcev <zaitcev@redhat.com>, Greg KH <greg@kroah.com>,
	dtor_core@ameritech.net, akpm@osdl.org,
	linux-kernel@vger.kernel.org, caphrim007@gmail.com,
	david-b@pacbell.net, linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] Re: Lost keyboard on Inspiron 8200 at 2.6.13
Date: Sat, 17 Sep 2005 09:08:23 +0100	[thread overview]
Message-ID: <1126944503.26447.5.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0509170005450.689-100000@netrider.rowland.org>

On Sad, 2005-09-17 at 00:12 -0400, Alan Stern wrote:
> Where does early handoff install a fake interrupt handler for UHCI?  I 
> don't see any in drivers/pci/quirks.c.

Fedora patches for 2.6.9 rather than the current code.

> > You need them because an IRQ could be pending on the channel at the
> > point you switch over or triggered on the switch and a few people saw
> > this behaviour.
> 
> Yes, that would be needed if you have edge-triggered interrupts.  But 
> isn't PCI supposed to be level-triggered?

Yes and at the time several people saw hangs on the changeover unless we
cleared pending IRQ bits in the IRQ handler. That may have been related
to various ACPI problems from back then. I don't know for sure.

> > I'd like to see it shared but that means handoff belongs in the input
> > layer code and the USB layer needs to call into it if appropriate.
> 
> Why does it mean that?  And why the input layer as opposed to the PCI 
> layer, where it is now?

PCI layer makes even more sense yes


      reply	other threads:[~2005-09-17  7:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16  4:29 Lost keyboard on Inspiron 8200 at 2.6.13 Tim Rupp
2005-09-16  4:57 ` Dmitry Torokhov
2005-09-16  5:13   ` Tim Rupp
2005-09-16  9:53   ` Andrew Morton
2005-09-16 15:25     ` Dmitry Torokhov
2005-09-16 16:00       ` Alan Cox
2005-09-16 18:44         ` Greg KH
2005-09-16 19:00           ` [linux-usb-devel] " Alan Stern
2005-09-16 19:45           ` David Brownell
2005-09-16 22:24           ` [linux-usb-devel] " Pete Zaitcev
2005-09-16 22:32             ` Greg KH
2005-09-16 23:54             ` Alan Cox
2005-09-17  4:12               ` Alan Stern
2005-09-17  8:08                 ` Alan Cox [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=1126944503.26447.5.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --cc=caphrim007@gmail.com \
    --cc=david-b@pacbell.net \
    --cc=dtor_core@ameritech.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    --cc=zaitcev@redhat.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