From: "Roland Caßebohm" <roland.cassebohm@visionsystems.de>
To: "Ravi Kumar B S" <ravikbs@mindtree.com>,
"Vinayak P Risbud" <vinayak@multitech.co.in>,
"Ecos-Discuss" <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] serial port ARM e7t problem
Date: Wed, 17 Jul 2002 01:11:00 -0000 [thread overview]
Message-ID: <200207170811.g6H8B6d04877@hhlx01.visionsystems.de> (raw)
In-Reply-To: <E125980C421DFD4DA0B80D55DB1EDA58980461@mtv01ex01.mindtree.com>
On Wednesday, 17. July 2002 06:26, Ravi Kumar B S wrote:
> The Samsung microcontroller has a DMA controller with it. the UART can be
> configured to work along with the UART chip. This is called DMA mode of the
> UART chip. With this you can configure to get the interrupt after certian
> number of bytes are received instead of single byte interrupt.
Has anybody tried to do this?
I thinked about it, but I haven't found a way to get an interrupt after a
timeout like a FIFO does. A UART with FIFO generates an interrupt after
reaching the triggerlevel or if it received less characters after an timeout.
Without something like this I will never notify if there are characters but
the DMA buffer isn't full.
Although there is nothing like a triggerlevel. If the UART gets the last
character fitting in the DMA-Buffer the interrupt happens and I have to copy
the buffer and restart the DMA before the next character is coming.
So I have the same chance to loose a character.
Roland
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2002-07-17 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 21:29 Ravi Kumar B S
2002-07-17 1:11 ` Roland Caßebohm [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-16 6:39 Vinayak P Risbud
2002-07-17 2:54 ` Robert Cragie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200207170811.g6H8B6d04877@hhlx01.visionsystems.de \
--to=roland.cassebohm@visionsystems.de \
--cc=ecos-discuss@sources.redhat.com \
--cc=ravikbs@mindtree.com \
--cc=vinayak@multitech.co.in \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).