public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: David Brownell <david-b@pacbell.net>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linux-usb-devel@lists.sourceforge.net,
	Paul Mackerras <paulus@samba.org>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [linux-usb-devel] Re: Commit "[PATCH] USB: Always do usb-handoff" breaks my powerbook
Date: Mon, 31 Oct 2005 22:39:56 -0500	[thread overview]
Message-ID: <200510312239.57601.dtor_core@ameritech.net> (raw)
In-Reply-To: <200510311909.32694.david-b@pacbell.net>

On Monday 31 October 2005 22:09, David Brownell wrote:
> > > > I'm not sure it's legal to do pci_enable_device() from within a pci
> > > > quirk anyway. I really wonder what that code is doing in the quirks, I
> > > > don't think it's the right place, but I may be wrong.
> > > 
> > > Erm, what "code is doing" what, that you mean ??
> > 
> > What _That_ code is doing in the quirks... shouldn't it be in the
> > {U,O,E}HCI drivers instead ?
> 
> Not for PCI.  Vojtech, this is your cue to explain some of how late handoff
> borks the input layer, as observed by SuSE on way too many BIOS/hardware combos
> for me to remember ... :)
> 

Not Vojtech, but here is goes... Not everyone has USB compiled in and
even then I think USB is registered after serio. So when we probe for
i8042 BIOS still has its dirty hands on USB controllers and pretends
that they are in fact PS/2 devices. Crazy stuff like that... That's
why we can't keep that code in HCI drivers. 

-- 
Dmitry

  parent reply	other threads:[~2005-11-01  3:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31  5:23 Commit "[PATCH] USB: Always do usb-handoff" breaks my powerbook Paul Mackerras
2005-11-01  0:16 ` Benjamin Herrenschmidt
2005-11-01  1:41   ` [linux-usb-devel] " David Brownell
2005-11-01  2:41     ` Benjamin Herrenschmidt
2005-11-01  3:09       ` David Brownell
2005-11-01  3:30         ` Benjamin Herrenschmidt
2005-11-01  4:17           ` David Brownell
2005-11-01  4:52             ` Paul Mackerras
2005-11-01  5:08               ` Benjamin Herrenschmidt
2005-11-01  9:28           ` Alan Cox
2005-11-01 13:40             ` Glenn Maynard
2005-11-01 21:09             ` Benjamin Herrenschmidt
2005-11-01  3:39         ` Dmitry Torokhov [this message]
2005-11-01  4:06         ` Kyle Moffett
2005-11-01  4:39           ` David Brownell
  -- strict thread matches above, loose matches on Subject: below --
2005-11-02  4:21 Aleksey Gorelov

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=200510312239.57601.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=benh@kernel.crashing.org \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=paulus@samba.org \
    --cc=stern@rowland.harvard.edu \
    /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