Steve Clark wrote:
Fredrik Lindberg wrote:
Marcin Cieslak wrote:
It maybe a good idea to add 0xFFF to the usbdevs.
Does the "umass" driver attach to the 0xFFF device? I would
recommend adding this as a quirk to umass.c then.
There are patches attached (ubsa.c_patch, umass_c.patch,
usbdevs
Fredrik Lindberg wrote:
Marcin Cieslak wrote:
It maybe a good idea to add 0xFFF to the usbdevs.
Does the "umass" driver attach to the 0xFFF device? I would recommend
adding this as a quirk to umass.c then.
There are patches attached (ubsa.c_patch, umass_c.patch, usbdevs.patch)
I am using t
Marcin Cieslak wrote:
Steve Clark wrote:
Is there any detailed documentation on the FreeBSD usb device driver
api?
This chapter helped me a lot to understand how this all works:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/usb.html
I sort of have it working by hacking ub
Fredrik Lindberg wrote:
This should be enough to switch the device, given that pass0
is the modem (use camcontrol devlist)
camcontrol cmd pass0 -c “01 00 00 00 00 00″ -i 1 i1
camcontrol might give you an error but the device will be switched.
Note that this is ONLY for Option based devices, I
Marcin Cieslak wrote:
It maybe a good idea to add 0xFFF to the usbdevs.
Does the "umass" driver attach to the 0xFFF device? I would recommend
adding this as a quirk to umass.c then.
There are patches attached (ubsa.c_patch, umass_c.patch, usbdevs.patch)
I am using to kill the "zeroconf" CD o
Steve Clark wrote:
Is there any detailed documentation on the FreeBSD usb device driver
api?
This chapter helped me a lot to understand how this all works:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/usb.html
I sort of have it working by hacking ubsa.c to look for the sierr