From: "Ling Su" <lingsu@palmmicro.com>
To: "Jonathan Larmour" <jlarmour@redhat.com>,
"Charles Feng" <charles@zh.t2-design.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Re: Fw: [ECOS] diag serial port and debug serial port conflict?
Date: Thu, 31 Aug 2000 10:55:00 -0000 [thread overview]
Message-ID: <003501c01371$d80fa4f0$0201a8c0@raccoon> (raw)
In-Reply-To: <39ADDD7D.8F2ECA73@redhat.com>
> Charles Feng wrote:
> > Jifl, do you have the plan to add ethernet debug support for vr4373
board?
>
> It's not yet part of our plans.
>
According to my understanding and examination on the new CVS, I think the
TCP/IP is not working on vrc4373 because of no low level EtherNet device
driver available. Is that correct? Therefore if I can build a working
version DEC ethernet chip driver, the TCP/IP and RedBoot will work on the
vrc4373, right?
Regards,
-Ling
prev parent reply other threads:[~2000-08-31 10:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-30 10:05 [ECOS] " Ling Su
2000-08-30 10:23 ` [ECOS] " Nick Garnett
2000-08-30 10:33 ` Ling Su
2000-08-30 19:26 ` Charles Feng
2000-08-30 21:22 ` Jonathan Larmour
2000-08-31 10:55 ` Ling Su [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='003501c01371$d80fa4f0$0201a8c0@raccoon' \
--to=lingsu@palmmicro.com \
--cc=charles@zh.t2-design.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@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).