> Ok, see the point for multiple readers. Do you know what happens if you
> have two readers on /dev/ttyS0 asking for 10 bytes each but the device is
> sending a 15 byte packet? My guess is one of them gets the first 10 bytes,
> the other one a shortened read of the remaining 5. Unless we are talking
Each of them gets some of it. I don't believe SuS says anything about who gets
which so alternate bytes or random but in order bytes is fine
> about a device which provides a lseek(2) operation, I don't see how to get
> around. Should we just drop these 5 bytes because they were triggered by
lseek on a streaming device is meaningless. If you cant 'rewind' you cant
lseek sanely
> Somebody please correct me if I'm wrong, but IIRC nothing which may block
> is acceptable to call from a signal handler - at least according to POSIX?
POSIX basically says 'all you can safely do is a set a variable'. syscalls
in signal handlers are safe but libc functions are dicing with death. You
can do blocking ones too
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
