Greg KH wrote: > But I don't think the log shows this happening, right? Right--I do not understand what is happening in the logs. I am interested in investigating more.
I was trying to clarify what was happening with opost processing and why the write has to succeed. > Actually, if write() doesn't ever fail, then we don't need a put_char() Right. Having put_char does give device writers another implementation option--write can fail but put_char has to succeed in writing one char. That might be nice, or it might just be (historical) clutter, but what is important is getting the drivers working correctly, whatever the interface. Mostly I though it funny that we talked about this years ago and the issue is still around. > I agree, and we should try to make sure the drivers support all of these > features, if we can figure out what they are :) It is an overwhelming list of "features"--there used to be a termio man page that described the ioctls; now its been supplanted by termios with the tc* functions which does not have as much info on the ioctls. -- Al ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
