On Tuesday 16 September 2003 04:47 pm, Mike Durian wrote:
> I'm trying to implement a serial protocol that is timing sensitive.
> I'm noticing things like drains and reads and blocking until the
> next kernel tick. I believe this is due to the lbolt sleeps
> in the tty.c code.
Following up on my
On Wednesday 17 September 2003 12:55 am, Terry Lambert wrote:
>
> You need your process to become a process group leader, and then
> you need the serial port you are interested in to become the
> controlling tty for your process.
I thought daemon(3) and TIOCSCTTY would do the trick, however
after
Mike Durian wrote:
> I'm trying to implement a serial protocol that is timing sensitive.
> I'm noticing things like drains and reads and blocking until the
> next kernel tick. I believe this is due to the lbolt sleeps
> in the tty.c code.
>
> It looks like I can avoid these sleeps if isbackground
3 matches
Mail list logo