Re: [Gta04-owner] [PATCH] Documentation: usb: serial: fixed how to provide vendor and product id

From: Johan Hovold
Date: Mon Mar 30 2015 - 06:11:03 EST


On Mon, Mar 30, 2015 at 11:40:20AM +0200, Dr. H. Nikolaus Schaller wrote:

> >>> diff --git a/Documentation/usb/usb-serial.txt b/Documentation/usb/usb-serial.txt
> >>> index 947fa62..9f184d8 100644
> >>> --- a/Documentation/usb/usb-serial.txt
> >>> +++ b/Documentation/usb/usb-serial.txt
> >>> @@ -466,11 +466,13 @@ Generic Serial driver
> >>> is required of your device is that it has at least one bulk in endpoint,
> >>> or one bulk out endpoint.
> >>>
> >>> - To enable the generic driver to recognize your device, build the driver
> >>> - as a module and load it by the following invocation:
> >>> - insmod usbserial vendor=0x#### product=0x####
> >>> - where the #### is replaced with the hex representation of your device's
> >>> - vendor id and product id.
> >>> + To enable the generic driver to recognize your device, configure
> >>> + USB_SERIAL_GENERIC=y and build the driver as a module. Then load it by the
> >>
> >> You don't need to build the driver as a module when using the sysfs
> >> method.
> >
> > Ok, that is right and my formulation is too narrow on that.
>
> Well, I should add that not my formulation was too narrow but already
> the original.

Since you change the description so that the context becomes invalid,
you are responsible for updating the context as well.

> >
> > So we just s/ as a module//.
> >
> >>
> >>> + following invocation:
> >>> + modprobe usbserial
> >>> + echo #### #### >/sys/bus/usb-serial/drivers/generic/new_id
> >>> + where the the first #### is replaced with the hex representation of your
> >>> + device's vendor id and the second #### by the product id.
> >>>
> >>> This driver has been successfully used to connect to the NetChip USB
> >>> development board, providing a way to develop USB firmware without

Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/