Re: [ECOS] interrupt and scheduling (serial driver)

[Jonathan Larmour <jifl at eCosCentric dot com>]

Roland Caßebohm wrote:
> I think the main issue which could keep other DSRs from running to long
> is, that the scheduler is locked the whole time data is copied, when
> beeing in read or write. If I work with larger buffers this could cause
> large delay.
>
> In http://sources.redhat.com/ml/ecos-discuss/2003-02/msg00209.html
> I have send a patch. I now the patch is not useable, because there
> are some things in which are for functionality which only I needed.
> It should only show what I have made.

Yes what you're doing seems reasonable in principle. Obviously the diag led 
bits shouldn't be there, and the overrun stuff is specific to you, but, as 
a separate patch, having something to retrieve the flow control method is 
a fair change.

> If you are interested I would make a usable patch. The patch just
> make a copy of the relevant pointers with scheluler locked at the
> beginning of read or write, writes them back at the end.

I can't see any real problems with it in principle. If you wanted to tidy 
it up for CVS that would be good.

Jifl
--
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
>>>>> Visit us in booth 2527 at the Embedded Systems Conference 2004 <<<<<
March 30 - April 1, San Francisco http://www.esconline.com/electronicaUSA/
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss