From: Chuck McManis <ecos@mcmanis.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] N00blet question on networking
Date: Fri, 23 Feb 2007 02:43:00 -0000 [thread overview]
Message-ID: <7.0.1.0.0.20070222153844.01a56ca0@mcmanis.com> (raw)
In-Reply-To: <45DD86C9.5050503@mlbassoc.com>
At 04:04 AM 2/22/2007, Gary Thomas wrote:
The most likely cause is not getting interrupts from your
>ethernet card. RedBoot doesn't use them but eCos requires
>that they work.
>
>Try putting some 'diag_printf()' calls in the ethernet driver to
>see what's happening.
Aye, that I've been doing and sure enough no Rx interrupts. I see the
transmit interrupts but not the receive ones ... hmmm.
--Chuck
>Note: at this point, it's best to access RedBoot via the serial port
>and leave network based debugging for later.
Sigh :-) I so wish this weren't the case but I understand why it is.
--
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:[~2007-02-23 2:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 3:20 Chuck McManis
2007-02-22 12:04 ` Gary Thomas
2007-02-23 2:43 ` Chuck McManis [this message]
2007-02-23 2:49 ` Chuck McManis
2007-02-22 3:47 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=7.0.1.0.0.20070222153844.01a56ca0@mcmanis.com \
--to=ecos@mcmanis.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).