I notice in recent Linux (Fedora specifically) that USB devices get pretty
consistently listed by a reasonably consistent and recognizable name in
/dev/serial/by_id.
I haven't looked to closely at all the USB fields yet, but some devices
have unique identifiers rather than the generic USB/serial. I was hoping to
scan for known patterns, apply any optimizations, and then connect. The
upcoming USB HobbyBoards hub will have that.
My dream is that owfs will be as "automatic" as possible. Currently we can
automatically scan for:
i2c
DS9490R
HA7Net
OWSERVER-ENET
w1
Hardware serial will always be a problem, but some USB-serial might be
possible.
Paul
On Mon, Sep 22, 2014 at 2:59 AM, Johan Ström <jo...@stromnet.se> wrote:
>
> On 22/09/14 00:21, Robin Gilks wrote:
> >> 1. Trying to resolve a serial port TTY name (i.e. /dev/cuaU1 on FreeBSD)
> >> to a potential USB device is probably doable, but not without a lot of
> >> effort and OS specific code.
> >> I don't think it's worth trying to go down that road.
> >>
> > How about using udev on Linux (is there an equivalent on other OSes?)
> that
> > creates a symlink to a device node with a unique name from the type
> (FTDI)
> > and bus number and OWFS looks for that specific device name.
> >
> > Just an idea (had to do that years ago with serial devices to sort out a
> > connection to a weather station and an IR blaster, never sure what device
> > names each would come up with!).
> >
> >
>
> I have a similar setup myself, using FreeBSD's devd. It uses my known,
> hard-coded USB serials to set up a symlink from /dev/cua-linkusb to
> /dev/cuaXXX when device is detected, to easier find which tty device I
> should be using for what (I think I have ~4 serial ports on my box)
>
> However, this doesn't solve the auto-deteciton problem, the user still
> needs to manually tell which USB device to be used, by serial-no or
> otherwise. And if that has to be done, it could just as well be done
> directly in owfs.
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
