atom feed13 messages in org.freebsd.freebsd-archnewbus flaw
FromSent OnAttachments
Dag-Erling SmørgravMay 11, 2004 7:39 am 
Doug RabsonMay 11, 2004 8:08 am 
Poul-Henning KampMay 11, 2004 8:12 am 
John-Mark GurneyMay 11, 2004 6:02 pm 
Dag-Erling SmørgravMay 12, 2004 6:27 am 
John-Mark GurneyMay 12, 2004 10:41 am 
Dag-Erling SmørgravMay 12, 2004 10:48 am 
John-Mark GurneyMay 12, 2004 10:53 am 
Dag-Erling SmørgravMay 12, 2004 1:30 pm 
Doug RabsonMay 13, 2004 1:27 am 
Dag-Erling SmørgravMay 13, 2004 3:46 am 
Doug RabsonMay 13, 2004 5:34 am 
M. Warner LoshMay 13, 2004 9:06 am 
Subject:newbus flaw
From:M. Warner Losh (im@bsdimp.com)
Date:May 13, 2004 9:06:27 am
List:org.freebsd.freebsd-arch

In message: <xzps@dwp.des.no> de@des.no (Dag-Erling Sm?rgrav) writes: : Doug Rabson <df@nlsystems.com> writes: : > When the old module unloaded, its driver will have detached from the : > device which it created. There is no reference to an old driver_t. Its : > perfectly safe for the new driver to use the old device. : : so why do you say I "shouldn't reset the old driver and desc"?

subr_bus.c does that already on detach. The association between devclass and device_t is done just prior to probe being called on a per device basis.

Warner