From: "Laurie Gellatly" <laurie.gellatly@netic.com>
To: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Re: Half Duplex RS485
Date: Sat, 26 Jan 2008 20:41:00 -0000 [thread overview]
Message-ID: <OBEELMDOHGDFDEMJCJCJEENIMIAA.laurie.gellatly@netic.com> (raw)
In-Reply-To: <BAY110-W387C5E7D79E8E5B7E58B02A5390@phx.gbl>
Hi Wang,
I've been looking through the patch you sent.
I don't see any change to the FIFO handling unless you mean where
it figures out the deviceType?
...Laurie:{)
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2008-01-26 20:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 4:16 wangcui
2008-01-26 20:41 ` Laurie Gellatly [this message]
2008-01-28 10:34 ` wangcui
2008-01-27 4:52 ` [ECOS] Uart missing chars when in Release Laurie Gellatly
2008-01-27 5:14 ` [ECOS] " Grant Edwards
2008-01-27 6:46 ` Laurie Gellatly
2008-01-27 9:54 ` Grant Edwards
2008-01-27 11:20 ` Laurie Gellatly
2008-01-27 15:55 ` Grant Edwards
2008-01-28 0:11 ` Laurie Gellatly
2008-01-28 2:37 ` Grant Edwards
2008-01-28 5:53 ` Laurie Gellatly
2008-01-28 15:58 ` Grant Edwards
2008-01-28 20:40 ` Grant Edwards
2008-01-29 23:35 ` Byron Jacquot
2008-02-06 9:35 ` Laurie Gellatly
2008-02-06 15:25 ` Grant Edwards
-- strict thread matches above, loose matches on Subject: below --
2008-01-21 22:04 [ECOS] routing sockets / far end address resolution Daniel Paape
2008-01-22 9:19 ` [ECOS] Half Duplex RS485 Laurie Gellatly
2008-01-23 16:34 ` [ECOS] " Grant Edwards
2008-01-23 21:12 ` Laurie Gellatly
2008-01-23 22:03 ` Grant Edwards
2008-01-23 23:06 ` Laurie Gellatly
2008-01-23 23:44 ` Grant Edwards
2008-01-24 9:02 ` Daniel Néri
2008-01-25 1:33 ` wangcui
2008-01-25 2:00 ` Laurie Gellatly
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=OBEELMDOHGDFDEMJCJCJEENIMIAA.laurie.gellatly@netic.com \
--to=laurie.gellatly@netic.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).