View Single Post
Old 10-15-2007, 10:31 PM   #1
timekiller
Newbie
 
Join Date: Mar 2005
Location: NJ
Posts: 51
USB Adapter for XM Direct

Anyone buy the mp3car usb adapter for xm ? I just bought both units and am having trouble getting my linux both to recognize it. I tried it in winblows and it seems to work (and seems to use the ftdi usb-serial driver). I have ftdi compiled into my kernel, but my system is not associating the device with the driver. I have manually loaded the module, but when I plug in the device in, this is all i get in dmesg:

-- modprobe ftdi_sio --
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device
usbcore: registered new interface driver ftdi_sio
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
-- plug in the unit --
usb 2-2: new full speed USB device using ohci_hcd and address 5
usb 2-2: configuration #1 chosen from 1 choice


Notice no /dev/ttyUSB creation ? lsusb -v gives me this:

Bus 002 Device 005: ID 6846:0002
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x6846
idProduct 0x0002
bcdDevice 6.00
iManufacturer 1 Mp3Car
iProduct 2 Mp3Car USB Adapter for XM Direct
iSerial 3 A1PRFSIQ
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 Mp3Car USB Adapter for XM Direct
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0


So I know the device is there, I think I just need to know how to make the kernel know the unit is an ftdi device.

So - anyone else try this ?
__________________
Mazda 3
Via Epia M10k w/ Lilliput 7"
Gentoo,MythTV,iGuidance v3
See the hardware and software
timekiller is offline   Reply With Quote
Advertisement
 
Advertisement
Sponsored links