I can try a patch, but the testing will have to fit in between the primary uses
of the machine (we have entirely too few Linux boxes at work, and far too many
Windows ones), so there might be a little latency in getting to it. Shouldn't
be more than a couple of days though.
I was unaware of the sysfs method, yet another undocumented (or at least I
didn't find it in in my google searching when trying to figure out why modprobe
wasn't working and wasn't generating ANY feedback) method. It is in my notes
now! Much cleaner. Thanks. I bet I could put it in a udev script and
automate this... but a proper patch would be better.
The Novatel seems to work fine as it is currently configured, although I have
not tried to receive any binary logs over USB on the Linux box yet.
Below is the relevant portion of the 'lsusb -v' output.
The device I am actually testing with is a NovaTel FlexPac6 rev 2 with a OEM628
board in it. This is NovaTel's middle of the line civilian GPS receiver
hardware, although I understand that all of their hardware with a USB port uses
the same USB hardware (and vender and product IDs).
Kirk
Bus 001 Device 005: ID 09d7:0100 Novatel Wireless NovAtel FlexPack GPS receiver
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 255
bMaxPacketSize0 64
idVendor 0x09d7 Novatel Wireless
idProduct 0x0100 NovAtel FlexPack GPS receiver
bcdDevice 1.01
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 60
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 5
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
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 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 0x04 EP 4 OUT
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 0x85 EP 5 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 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
-----Original Message-----
From: Johan Hovold [mailto:[email protected]] On Behalf Of Johan Hovold
Sent: Wednesday, August 13, 2014 01:16
To: Kirk Madsen
Cc: [email protected]
Subject: Re: usbserial_generic
On Tue, Aug 12, 2014 at 09:53:41AM -0600, Kirk Madsen wrote:
> After a great deal of searching, I discovered that instead of doing a
> simple "/sbin/modprobe usbserial vendor=0x09d7 product=0x0100", with
> fedora 20 you now have to edit your grub2 config to add a generic
> serial device. Dmesg reported the following, so I am following
> directions. Please add this device to a proper driver.
>
> [ 1.391259] usb 1-1.1: new full-speed USB device number 3 using
> ehci-pci [ 1.478121] usb 1-1.1: New USB device found,
> idVendor=09d7, idProduct=0100 [ 1.478127] usb 1-1.1: New USB device
> strings: Mfr=1, Product=2, SerialNumber=3 [ 1.478130] usb 1-1.1:
> Product: Novatel GPS Receiver [ 1.478133] usb 1-1.1: Manufacturer: Novatel
> Inc.
> [ 1.478135] usb 1-1.1: SerialNumber: BFN14190250 [ 1.479205]
> usbserial_generic 1-1.1:1.0: The "generic" usb-serial driver is only for
> testing and one-off prototypes.
> [ 1.479209] usbserial_generic 1-1.1:1.0: Tell [email protected] to
> add your device to a proper driver.
> [ 1.479212] usbserial_generic 1-1.1:1.0: generic converter detected
> [ 1.479345] usb 1-1.1: generic converter now attached to ttyUSB0 [
> 1.479420] usb 1-1.1: generic converter now attached to ttyUSB1 [
> 1.479448] usb 1-1.1: generic converter now attached to ttyUSB2
Thanks for reporting back. What is the full "lsusb -v" output for this device?
Could you test a patch for Novatel GPS support if I send you one?
Note that you can also add a VID/PID using sysfs, e.g.:
echo 09d7 0100 >/sys/bus/usb-serial/drivers/generic/new_id
Thanks,
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
