As said below, modify usbdevs/umass.c to recognise your device and then
see whether it behaves. If not, try adding the quirks to scsi_da.c (no
READS_6 and no cache sync) and see whether that improves things.
If it is an ATAPI based device it might be more work to get this device
working.
Nick
Nick,
As said below, modify usbdevs/umass.c to recognise your device and then
see whether it behaves. If not, try adding the quirks to scsi_da.c (no
READS_6 and no cache sync) and see whether that improves things.
Since I started this, I ought to say that while I enjoy new challenges I
don't
* Andrew J Caines [EMAIL PROTECTED] [010902 22:12] wrote:
Nick,
As said below, modify usbdevs/umass.c to recognise your device and then
see whether it behaves. If not, try adding the quirks to scsi_da.c (no
READS_6 and no cache sync) and see whether that improves things.
Since I
Hackers,
The overwhelming lack of response on -questions suggests I might do better
here. I though this would be an easy one.
In short, I simply want to know what device to mount and what to do get
that device configured.
# usbdevs -v
Controller /dev/usb0:
addr 1: self powered, config
Matthew Emmerton wrote:
Hackers,
The overwhelming lack of response on -questions suggests I might do better
here. I though this would be an easy one.
In short, I simply want to know what device to mount and what to do get
that device configured.
# usbdevs -v
Controller /dev/usb0:
addr 1: self
Hackers,
The overwhelming lack of response on -questions suggests I might do better
here. I though this would be an easy one.
In short, I simply want to know what device to mount and what to do get
that device configured.
I have a Rio 600 MP3 player connected via USB. The device is recognised
6 matches
Mail list logo
