| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
I wonder if someone on this list is willing to explain to me why IOUSBMassStorageClass directly instantiates an IOSCSILogicalUnitNub, rather than allowing the registry to match IOSCSIPeripheralDeviceNub, as the FireWire and ATAPI SCSI Protocol Service providers do?
Is there a reason for the difference?
In particular, this interferes with my driver that depends on beating IOSCSIPeripheralDeviceNub in the probe(). I've got a customer that would like to use my driver to inspect the SCSI CDB's that are causing his USB Mass target to behave strangely. Of course, a bus analyzer will eventually do the trick, but it is more expensive and less convenient.
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.