From: rholmberg <randy.holmberg@liposonix.com>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Multi-cast mode warning
Date: Wed, 31 Jan 2007 15:40:00 -0000 [thread overview]
Message-ID: <8731428.post@talk.nabble.com> (raw)
In-Reply-To: <5098085.post@talk.nabble.com>
Tim,
Can you please tell me if you were able to get the DP83848 to function
properly with the AT91RM9200? I have an application that is planning to use
the same DP83848CW Ethernety PHY with the AT91RM9200 - it would be very
reassurring to know that someone has successfully implemented these items.
Best Regards,
Randy Holmberg
Tim Hatton wrote:
>
> Hello,
> I am currently in the process of try to get eCos (2.0.43) running on our
> own hardware which uses an ATMEL AT91RM9200 CPU (bulit in MAC) and a
> DP83848 PHY. I have used the eCos build from the AT91RM9200-EK and the
> exisiting DP83847 driver (changing it to support the similar DP83848) as a
> base and I have got to the stage where the ethernet link is established. I
> am however getting the following warning message when initialising the
> network:
>
> [eth_drv_ioctl] Warning: Driver can't set multi-cast mode
>
> Now, if everything worked I wouldn't be worried about this, but I don't
> seem to be getting any IP packets out of the hardware (eCos is trying to
> send DHCP discovery messages but they aren't coming out to the ethernet).
> I suspect this may be a hardware issue but, I would like some confirm that
> the warning above is or isn't anything I need to look into.
>
> My understanding of multi-cast mode is that I shouldn't need it or care
> but if anyone could confirm or deny this I'd be very grateful.
> Best regards,
> Tim Hatton
> Coherent Research Ltd
> UK
>
>
>
>
--
View this message in context: http://www.nabble.com/Multi-cast-mode-warning-tf1865903.html#a8731428
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.
--
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-01-31 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 7:09 Tim Hatton
2006-06-29 10:06 ` Gary Thomas
2006-06-29 11:40 ` Tim Hatton
2007-01-31 15:40 ` rholmberg [this message]
2007-02-01 2:10 ` wang cui
2006-06-30 7:26 FALL
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=8731428.post@talk.nabble.com \
--to=randy.holmberg@liposonix.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).