From: "Ling Su" <lingsu@palmmicro.com>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] How to make a Interrupt driven serial port driver?
Date: Fri, 27 Oct 2000 17:53:00 -0000 [thread overview]
Message-ID: <003d01c0407a$0f66d880$1201a8c0@crusoe> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
Dear All,
Â
I am using a NEC VRC4373 board, as you may know, it has two serial ports. I
use serial port 1 for GDB, and leave serial port 2 for communication with PC.
Now I have tested all the io tests on serial port 2, so it works well. My
question is how I can make a Interrupt driven driver from serial port 2. The
current serial port driver in eCos supports general Read/Write/ioctl funtions. I
don't want to waste time on constantly query serial port for input. The ideal
method will be interrupt trigged when input byte coming. On this platform, only
one interrupt allocated to UART, serial port 1 for GDB purpose, I think it will
use Interrupt, too. Is there any general method to implement a interrupt driver
for serial port B? Or I have to write it from scratch? Is there kernal API
for me can register such kind of Interrupt for serial port B without producing
conflict for serial port A?
Â
I looked the kernel source and driver, didn't figure out a simple way, is
that possible, please help me. Thanks a bounch!
Â
Regards,
-Ling
next reply other threads:[~2000-10-27 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 17:53 Ling Su [this message]
2000-10-29 13:43 ` Jonathan Larmour
2000-10-29 18:28 ` Ling Su
2000-10-29 19:02 ` Jonathan Larmour
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='003d01c0407a$0f66d880$1201a8c0@crusoe' \
--to=lingsu@palmmicro.com \
--cc=ecos-discuss@sources.redhat.com \
/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).