Am 10.08.2010 06:37, schrieb Kay Sievers:
On Tue, Aug 10, 2010 at 00:37, Josua Dietze<digidietze@xxxxxxxxxxxxxxx> wrote:
Up to now I have used a rule to add a symlink to the "right" port; the check
is done by a script via "PROGRAM". If the port is not right, the result of
the script is empty, thus no symlink:
ACTION=="add", KERNEL=="ttyUSB*", PROGRAM="<script> %p", SYMLINK="%c"
Who needs these custom links? Why don't you just use the stuff in
/dev/serial/ which should already work?
There is a symlink to *every* port in the /dev/serial folders. Again,
only *one* of them is usable for connecting through
wvdial/umtsmon/networkmanager. The latter often auto-selects a wrong
port, BTW.
I add *one* symlink called "gsmmodem[x]" to make life easier for users.
Examples:
Huawei E160 ttyUSB0,1,2 gsmmodem -> ttyUSB0
ZTE MF110 ttyUSB0,1,2 gsmmodem -> ttyUSB2
These interfaces all have a class of 0xff. Some are even accepting AT
commands, but are only intended for diagnostic purposes, misleading
users and probers.
Thanks,
Josua Dietze
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
