This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: How to make a Interrupt driven serial port driver?

To: Ling Su <lingsu at palmmicro dot com>
Subject: Re: [ECOS] How to make a Interrupt driven serial port driver?
From: Jonathan Larmour <jlarmour at redhat dot com>
Date: Mon, 30 Oct 2000 03:02:13 +0000
CC: ecos-discuss at sources dot redhat dot com
Organization: Red Hat UK Ltd.
References: <003d01c0407a$0f66d880$1201a8c0@crusoe> <39FC9A15.8DBAA00C@redhat.com> <007701c04219$5ab4d530$0301a8c0@leopard>

Ling Su wrote:
> 
> > Or instead are you asking for some sort of automatic notification to your
> > application when data arrives?
> >
> 
> Yeah, exactly, what I am asking is how to make a kind of automatic
> notification to my application, so that my own serial port handler can
> continue process that data when data arrives. Any clue? Thanks!

Well, in that case as per another thread on ecos-discuss, you can either:

- use select(), but this has a number of overheads
- use a separate thread to read data, and then signal other threads in your
application
- or just go ahead and modify the source in the driver itself! e.g. by
waking up a thread in the serial DSR. This is one of the advantages of open
source after all.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

References:
- How to make a Interrupt driven serial port driver?
  - From: Ling Su
- Re: How to make a Interrupt driven serial port driver?
  - From: Jonathan Larmour
- Re: How to make a Interrupt driven serial port driver?
  - From: Ling Su

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]