All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stelian Pop <stelian.pop@fr.alcove.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: USB host drivers test results (2.5.19) and problem.
Date: Fri, 31 May 2002 11:55:50 -0700	[thread overview]
Message-ID: <20020531185549.GF1886@kroah.com> (raw)
In-Reply-To: <20020531133429.GF8310@come.alcove-fr> <21481.1022856842@redhat.com> <20020531163914.GB1250@kroah.com> <20020531184442.GB10621@come.alcove-fr>

On Fri, May 31, 2002 at 08:44:42PM +0200, Stelian Pop wrote:
> On Fri, May 31, 2002 at 09:39:14AM -0700, Greg KH wrote:
> 
> > > >  1. Shouldn't the ehci/ohci drivers give some error on loading, since
> > > > I obviously don't have the hardware ? 
> > > 
> > > How do they know that? You could have it in your hand and be just about to
> > > insert it.
> > 
> > They should not load, like any other pci driver that should not load if
> > you don't have the hardware present for it.
> 
> What about the PCI hotplug case, as David suggested ?

When the pci hotplug core sees a new device it calls out to
/sbin/hotplug to load any available driver (if necessary).  So if you
later plug in the device, everything will work just fine.

Well, that's the way it's _supposed_ to work, but the pci core changes
in 2.5.19 seem to have broken this too :(

/me looks for Pat Mochel...

thanks,

greg k-h

  reply	other threads:[~2002-05-31 18:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-31 13:34 USB host drivers test results (2.5.19) and problem Stelian Pop
2002-05-31 14:54 ` David Woodhouse
2002-05-31 15:07   ` Stelian Pop
2002-05-31 22:41     ` Brad Hards
2002-05-31 16:39   ` Greg KH
2002-05-31 18:44     ` Stelian Pop
2002-05-31 18:55       ` Greg KH [this message]
2002-05-31 16:38 ` Greg KH
2002-05-31 18:43   ` Stelian Pop

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=20020531185549.GF1886@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stelian.pop@fr.alcove.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 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.