[aprssig] Tomtom's For APRS (Question)

[Steve]

on linux, I add http://www.nongnu.org/halevt and use it to fire
per-device scripts (kissattach/gpsd-hotplug/etc...) halevt needs a
little extra attention to detail when it's being customized for your
setup and to make sure you match specific usb id's when you want to,
but it can make sure the same thing happens every time a usb device is
inserted/ejected. Ymmv, but I've had much better luck with halevt
handeling individual usb devices where udev/hotplug always got
confused when two of the same make/model were inserted.

73, AB3LT



On Mon, Apr 2, 2012 at 3:08 PM, Jason KG4WSV <kg4wsv at gmail.com> wrote:
> On Mon, Apr 2, 2012 at 12:25 PM, Tom Hayward <esarfl at gmail.com> wrote:
>> If your distribution uses udev, you can write a udev rule to match the
>> D72's serial number and assign it to a specific device name every
>> time.
>
> Only if either a) the device has a unique identifier, or b) you plug
> it in to the same place in the USB tree _every_ _time_.  FTDI is the
> only vendor I'm aware of that assigns a unique ID to each device.
>
> I'd really like to know if the USB CDC specification allows for a unique ID.
>
>> Here's example instructions for doing this for an FTDI USB serial converter:
>
> Not sure why the folks who wrote the linux FTDI driver failed to take
> advantage of the FTDI unique identifier, but it's an unnecessary
> gyration, IMO.  Look at how it works on Mac OS
> (/dev/tty.usbserial-12345678, where 12345678 is the device's serial
> number).
>
> -Jason
> kg4wsv
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig