serial driver with 2 dispatch threads?

bridged with qdn.public.ddk
Post Reply
mik

serial driver with 2 dispatch threads?

Post by mik » Wed Oct 22, 2003 6:53 pm

Hello,

I have taken the standard devc-ser8250 and added a thread to handler the
resource managing,
while the main thread does all the interrupt processing. This works fine.
The problem comes
when I added a third thread that implements the "Sample code for handling
_IO_READ messages".
This sample code conflicts with the io-char library. It should be possible
to have another resource.
Do I have to re-write the io-char library and use the "Multi-threaded device
resource manager example"
as the basis for a new io-char library?

Thanks

mik

Re: serial driver with 2 dispatch threads?

Post by mik » Fri Oct 24, 2003 2:48 pm

I have found the conflict. When defining your io_*() functions make sure
you alter the name function.
For example instead of
io_funcs.read = io_read;
use
io_funcs.read = my_io_read;



"mik" <mkonstantinides@connecttech.com> wrote in message
news:bn6inl$m1i$1@inn.qnx.com...
Hello,

I have taken the standard devc-ser8250 and added a thread to handler the
resource managing,
while the main thread does all the interrupt processing. This works fine.
The problem comes
when I added a third thread that implements the "Sample code for handling
_IO_READ messages".
This sample code conflicts with the io-char library. It should be
possible
to have another resource.
Do I have to re-write the io-char library and use the "Multi-threaded
device
resource manager example"
as the basis for a new io-char library?

Thanks

Post Reply

Return to “qdn.public.ddk”