Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 May 1999 16:55:25 +0200 (CEST)
From:      Nick Hibma <nick.hibma@jrc.it>
To:        Peter Wemm <peter@netplex.com.au>
Cc:        cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sys/pci pcisupport.c 
Message-ID:  <Pine.BSF.3.96.990510163918.8928E-100000@elpc36.jrc.it>
In-Reply-To: <19990510143213.E2FD91F72@spinner.netplex.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help

How would you unbind those stubs in case a module is loaded?

As in, not load USB support at boottime. The stub would prevent the
module loaded later on from obtaining the device.

In USB land we already have that problem (the generic driver that
attaches to anything not taken by any other driver).  The solution there
is to detach anything called ugen\d+ when a module is loaded/before a
probe is done. 

An option would be to return as a priority PRIORITY_STUB, and, when
a new driver for PCI is loaded, detach anything that has attached at
this priority.


Or more general (for PCI that is): reprobe all the devices. If the
device is probed at a higher priority detach it from the old one and
reattach it to the new one. This assumes probes with no side effects.
This also is not compatible with the statement that anything that
probes at maximum priority can expect the device structs to be as it
left it after the probe.


Cheers,

Nick

On Mon, 10 May 1999, Peter Wemm wrote:

 > Nick Hibma wrote:
 > > n_hibma     1999/05/10 07:07:16 PDT
 > > 
 > >   Modified files:
 > >     sys/pci              pcisupport.c 
 > >   Log:
 > >   Remove VIA USB controller (was '#if 0' out), to make sure
 > >   no one adds it back. Chip handled by uhci_pci.c .
 > 
 > I was thinking of doing this, the same as alpm and intpm:
 > 
 >     case 0x<devid>:
 > #if NUHCI > 0
 > 	return NULL;
 > #else
 > 	return "VIA blah USB controller";
 > #endif
 > 
 > Once Doug commits his tweaks to enable preferential probing or driver
 > priorities or whatever he has in mind, this should come back so that we can
 > see the identification if the USB code isn't activated. Without it, the
 > devices go anonymously and it's easy to not even notice that you've got
 > supported motherboard services that you could be taking advantage of.  This
 > is more useful in the power management area though, it's hard to miss USB
 > ports. :-)
 > 
 > Cheers,
 > -Peter
 > 
 > 
 > 




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990510163918.8928E-100000>