I'm working on booting OS from usb drive.
But it already works. What exactly are you trying to do?
I tried to walk minor nodes of type DDI_NT_UGEN (c file attached)
DDI_NT_UGEN are ugen(7D) driver links, why would you want them.
The raw address of plugged in flash drive is (from rmformat):
/devices/[EMAIL PROTECTED],0/pci1019,[EMAIL PROTECTED],7/[EMAIL
PROTECTED]/[EMAIL PROTECTED],0
and i can mount it as fat using
mount -F pcfs /devices/[EMAIL PROTECTED],0/pci1019,[EMAIL PROTECTED],7/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:r /mnt/
Look at prtconf:
pci1022,7464, instance #0 (driver name: ohci)
storage, instance #0 (driver name: scsa2usb)
disk, instance #2 (driver name: sd)
.../[EMAIL PROTECTED],0 corresponds to scsa2usb - USB SCSA HBA (nexus) driver. scsa2usb
does not create mountable block devices.
.../[EMAIL PROTECTED]/[EMAIL PROTECTED],0 corresponds to sd - common SCSI target driver. sd creates
block devices (minor nodes) that can be mounted.
Now find that sd instance in 'prtconf -v' and look at the list of minor nodes
hanging off of it [1]. These are the ones you're looking for. USB block devices
are just like any other storage. And in general, it doesn't make much sense to
separate it. USB block devices do have the 'usb' boolean property, though it's
not a public interface [2].
-Artem.
[1] If you see "disk, instance #2 (driver not attached)", you can e.g. mount the
drive to keep the driver attached.
[2] http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
