Subject: Re: O_NONBLOCK in a character device driver
To: Andreas Gustafsson <firstname.lastname@example.org>
From: Michael Graff <email@example.com>
Date: 08/17/1997 17:20:01
Andreas Gustafsson <firstname.lastname@example.org> writes:
> You need to make the driver mask with IO_NDELAY instead of O_NONBLOCK.
> As to why two different bits are used, I don't know.
Yea, I found this out later... My guess is that there are quite a few
drivers out there that are broken in this way as well (Jason's satlink
driver, for one I think...)