* serial port buffer commit
@ 2002-11-26 15:56 David Chow
0 siblings, 0 replies; 2+ messages in thread
From: David Chow @ 2002-11-26 15:56 UTC (permalink / raw)
To: linux-kernel
Hi all,
I am writing a kernel thread for serial port communication. If the
serial character device file is opened by a filp_open() or manipulating
using a struct file in the kernel, how can I know whether the previous
written buffer has commit or not? Similarly, how do I know is there any
data ready for read for non blocking access? Thanks.
regards,
David Chow
^ permalink raw reply [flat|nested] 2+ messages in thread
* serial port buffer commit
@ 2002-11-27 2:24 David Chow
0 siblings, 0 replies; 2+ messages in thread
From: David Chow @ 2002-11-27 2:24 UTC (permalink / raw)
To: linux-kernel
Hi all,
I am writing a kernel thread for serial port communication. If the
serial character device file is opened by a filp_open() or manipulating
using a struct file in the kernel, how can I know whether the previous
written buffer has commit or not? Similarly, how do I know is there any
data ready for read for non blocking access? Thanks.
regards,
David Chow
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-11-27 2:17 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-11-27 2:24 serial port buffer commit David Chow
-- strict thread matches above, loose matches on Subject: below --
2002-11-26 15:56 David Chow
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.