2011/8/16 Jan Kandziora
> Am Dienstag, 16. August 2011, 14:11:49 schrieb Paul Alfille:
> > Did you know that --usb=ALL and --i2c=ALL:ALL will do the scanning for
> you?
> >
> Yes, but only in the back of my mind. That function isn't exactly what I
> need.
> I do this scanning once on application
On 8/16/2011 17:42, Jan Kandziora wrote:
If there was another possiblity to find out which host adapters are in use, I
would find that useful, too. Something like
"bus.2/interface/settings/serial/device" returning "ttyS0" or major/minor
Maybe this will help:
cat /mnt/1-wire/bus.0/bus.0/interfac
Am Dienstag, 16. August 2011, 14:11:49 schrieb Paul Alfille:
> Did you know that --usb=ALL and --i2c=ALL:ALL will do the scanning for you?
>
Yes, but only in the back of my mind. That function isn't exactly what I need.
I do this scanning once on application start. Then I have a list of host
adap
humm this could be nice :)
2011/8/16 Paul Alfille :
> Did you know that --usb=ALL and --i2c=ALL:ALL will do the scanning for you?
> I think the serial hasn't actually hung, it's just a very long sequence
> (minutes). The code certainly wasn't tuned for efficiently finding bad port,
> but rather fi
Did you know that --usb=ALL and --i2c=ALL:ALL will do the scanning for you?
I think the serial hasn't actually hung, it's just a very long sequence
(minutes). The code certainly wasn't tuned for efficiently finding bad port,
but rather finding the right settings for configuration problems. So ther
Hello,
in my application, I have an auto-detection scheme to find out which host
adapter(s) the machine has. Basically I probe each /dev/i2c-*, /dev/ttyS*,
/dev/ttyUSB* and usb one after another to find out if there is a onewire host
on that port.
That works fine with USB and I²C, but with ser
