From: "Laurie Gellatly" <laurie.gellatly@netic.com>
To: "Chuck McManis" <ecos@mcmanis.com>,
"ECOS Discussion Group" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] and another thing ..
Date: Thu, 22 Feb 2007 06:50:00 -0000 [thread overview]
Message-ID: <OBEELMDOHGDFDEMJCJCJGEHMLKAA.laurie.gellatly@netic.com> (raw)
In-Reply-To: <6.1.2.0.2.20070221222531.03c90ec0@192.168.110.40>
Have you set the ethernet chip to receive boradcasts as well as unicasts or
any
other such filtering?
...Laurie:{)
-----Original Message-----
From: Chuck McManis [mailto:ecos@mcmanis.com]
Sent: Thursday, 22 February 2007 5:30 PM
To: ECOS Discussion Group
Cc: Laurie.Gellatly
Subject: Re: [ECOS] and another thing ..
At 08:21 PM 2/21/2007, you wrote:
>The MAC changes - interesting.
>So your NIC supports working with two MACs simultaneously?
>You might try by simplifying things and keeping just the one MAC and having
>it support two IPs which I know works.
>Why do you want both Redboot and your app to be DHCP?
>Again, I'd look to nail these to some static addresses to get you started
>and then make it fancier later.
Well as I expected hard coding the address didn't really change anything.
Basically I'm not seeing any of the response packets. So I went back to my
old notes from a year ago where I had a similar issue with Redboot and
there were issues with enabling the CRC checking / generation which I've
confirmed are not the issue here.
Sigh, time to match Ethereal traces with debugging output and try to narrow
down where things go wrong. I suppose the good news is that when I use DHCP
the DHCP server *is* seeing the transmitted packets so I can contentrate
primarily on the receiver. It does complain about not being able to set
multicast but I don't think that is a real problem. I'll know after I dig
into the traces more thoroughly. Hmm, I suppose I could dig up my old Intel
board as well and see if that board had similar issues. Another avenue to
try ...
--Chuck
--
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-22 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 4:21 Laurie.Gellatly
2007-02-22 6:28 ` Chuck McManis
2007-02-22 6:50 ` Laurie Gellatly [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-22 3:52 Laurie.Gellatly
2007-02-22 4:05 ` Chuck McManis
2007-02-22 3:46 Chuck McManis
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=OBEELMDOHGDFDEMJCJCJGEHMLKAA.laurie.gellatly@netic.com \
--to=laurie.gellatly@netic.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=ecos@mcmanis.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).