From: Nick Garnett <nickg@ecoscentric.com>
To: droethig@cipher.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] problem with generic serial driver?
Date: Thu, 19 May 2005 23:15:00 -0000 [thread overview]
Message-ID: <m31x83e10s.fsf@xl5.calivar.com> (raw)
In-Reply-To: <428CA063.8040005@cipher.com>
David Roethig <droethig@cipher.com> writes:
> > Out of interest, what is the target you are working on?
>
> We are working on a Philips LPC2292 custom board.
> We started our design before the LPC2xxx port was released. Recently,
> the generic serial port driver package was added because we thought
> it would be more robust than the code we cobbled together.
That makes sense, I think it was in the context of the LPC2xxx serial
devices that I came across the same problem.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2005-05-19 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 8:43 David Roethig
2005-05-19 12:16 ` Nick Garnett
2005-05-19 20:01 ` David Roethig
2005-05-19 23:15 ` Nick Garnett [this message]
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=m31x83e10s.fsf@xl5.calivar.com \
--to=nickg@ecoscentric.com \
--cc=droethig@cipher.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).