Alan Stern wrote:
Yes, of course we always write device drivers so that they will fail in
unexpected ways unless the user does something unintuitive and
undocumented. :-)
Ya, we all knew that. Just so long as you understand that we users all
read the hardware docs from cover to cover,
Robert Hancock wrote:
It's because you haven't done anything to handle the error which is
still persisting. Likely the only thing sane you can do in this case is
close the fd and try to reopen it later.
This seems to be true, but not for what you might think.
It appears that if u plug the
Alan Stern wrote:
Another way of thinking about it: Suppose an existing device entry was
not removed (or least made inaccessible) when you unplugged the device
-- the idea being that the existing entry could be reused if you
plugged the device back in. Then if you never did plug it back
Alan Stern wrote:
On Sun, 3 Jun 2007, Uncle George wrote:
Alan Stern wrote:
Another way of thinking about it: Suppose an existing device entry was
not removed (or least made inaccessible) when you unplugged the device
-- the idea being that the existing entry could be reused if you
Pete Zaitcev wrote:
BTW, here's the recipy I use for my GPS (I use it as timing source,
so ntpd has to be able to find it in fixed place):
[EMAIL PROTECTED] ~]$ cat /etc/udev/rules.d/70-gps.rules
KERNEL==ttyACM*, SYSFS{idVendor}==0b20 SYSFS{idProduct}==0406,
SYMLINK+=gps0
[EMAIL
