Re: Possible to force ttyUSB2 for Prolink PH-300?
- From: Dan Williams <dcbw redhat com>
- To: Ascanio Alba <ascanio alba4 gmail com>
- Cc: networkmanager-list gnome org
- Subject: Re: Possible to force ttyUSB2 for Prolink PH-300?
- Date: Fri, 27 May 2011 10:05:52 -0500
On Fri, 2011-05-27 at 22:36 +0800, Ascanio Alba wrote:
> The same udev rules used for 1e0e:9200 work for 1e0e:9100:
>
> Tks for the pointer.
Could you grab the lsusb output for me too?
lsusb -v -d 1e0e:9100
Thanks!
Dan
> #! create the serial ports
> modprobe -v option
> echo "1e0e 9100" > /sys/bus/usb-serial/drivers/option1/new_id
>
> #/etc/udev/rules.d/77-mm-9100.rules
> # do not edit this file, it will be overwritten on update
>
> # Simtech makes modules that other companies rebrand, like:
> #
> # A-LINK 3GU
> # SCT UM300
> #
> # Most of these values were scraped from various SimTech-based Windows
> # driver .inf files. *mdm.inf lists the main command ports, while
> # *ser.inf lists the aux ports that may be used for PPP.
>
>
> ACTION!="add|change", GOTO="mm_simtech_port_types_end"
> SUBSYSTEM!="tty", GOTO="mm_simtech_port_types_end"
>
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="1e0e",
> GOTO="mm_alink_vendorcheck"
> GOTO="mm_simtech_port_types_end"
>
> LABEL="mm_alink_vendorcheck"
> SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}=="?*",
> ENV{.MM_USBIFNUM}="$attr{bInterfaceNumber}"
>
> ATTRS{idProduct}=="9100", ENV{.MM_USBIFNUM}=="03",
> ENV{ID_MM_SIMTECH_PORT_TYPE_MODEM}="1"
> ATTRS{idProduct}=="9100", ENV{.MM_USBIFNUM}=="01",
> ENV{ID_MM_SIMTECH_PORT_TYPE_AUX}="1"
> ATTRS{idProduct}=="9100", ENV{ID_MM_SIMTECH_TAGGED}="1"
>
> GOTO="mm_simtech_port_types_end"
>
> LABEL="mm_simtech_port_types_end"
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]