In message <43F4E065.306@tadpole.com>, "Garrett D'Amore" writes:

>> What is the "device" I'd use with 'drvctl -d'?  ohci0?  Or do I have to 
>> do it recursively, starting with ucom0 and uhub5?  And what bus (and 
>> perhaps locator or attribute) do I use with 'drvctl -r'?
>>   
>Those are excellent questions. Unfortunately, I don't have an answer.
>Experiment and see what happens.
>
>As they say, "use the Source, Luke".

I had looked at drvctl.c and kern_drvctl.c before I posted, but they're 
both short and sweet and led to a complex maze of configuration 
routines...


		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb