Subject: RE: USB device attachment
To: 'email@example.com' <firstname.lastname@example.org>
From: Adam Glass (Exchange) <adamg@Exchange.Microsoft.com>
Date: 07/25/1999 10:54:33
How do you handle resources consumed by ISAPNP or PCI cards that we're
turned on by the BIOS but for which you have no driver? Are they properly
accounted for so that you do not put something else on top of them without
first turning them off?
From: email@example.com [mailto:firstname.lastname@example.org]
Sent: Friday, July 23, 1999 1:16 PM
To: Lennart Augustsson
Subject: Re: USB device attachment
this seems reasonable. i wish both SCSI and PCI had 'target'/'card'
abstractions like this, actually.
How does a 'compound' device present itself to the user?
for simple devices, it seems obvious:
allow access via device driver if attached, else
allow "raw" access via udev.
for compound devices what do you do? It looks from your drawing like
you'll have only one 'udev' for such a case, which makes doing the
right thing harder: it means that you have to have the user do the
sub-"udev" device selection themselves... That seems ... more complex
than it perhaps should be (and that complexity then has to spill over
into the simple device raw access case, too).
Chris Demetriou - email@example.com -
Disclaimer: Not speaking for NetBSD, just expressing my own opinion.