linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: "Samuel Osorio Calvo" <samuel.osorio@nl.thalesgroup.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: multicast disabled on 8260_io/fcc_enet.c
Date: Wed, 15 Jun 2005 21:03:25 -0400	[thread overview]
Message-ID: <5359e8b72ccab672f101490b84a1f1c0@embeddededge.com> (raw)
In-Reply-To: <s2b045ef.027@scms1.sc.signaal.nl>


On Jun 15, 2005, at 9:14 AM, Samuel Osorio Calvo wrote:

> Currently I have multicast working just be moving the return 
> statement. It seems to work but I guess I did not face yet the 
> problems that caused the code to be commented.
> Let's say it works in an unreliable way....

When I wrote the original code I copied the old SCC driver and didn't 
have
a function for computing CRCs, so I just placed the return early in the 
function.
I believe there is a patch floating around that wrote a CRC function 
(or used some
existing one), to compute the filter mask.  If the code has a CRC 
function call,
then it will likely work.  If it doesn't have one, then you are running 
on luck.  Either
the proper filter bit is set by some random reset bits, or you somehow 
get the
right one set.  By default, the multicast filter may just catch 
everything, forcing
the Linux IP stack to do the filtering at a higher level, not exactly 
what you want. :-)

This has been discussed many times in the past.

Thanks.

	-- Dan

  reply	other threads:[~2005-06-16  1:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 13:14 multicast disabled on 8260_io/fcc_enet.c Samuel Osorio Calvo
2005-06-16  1:03 ` Dan Malek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-17 15:29 Samuel Osorio Calvo
2005-06-13 16:14 Samuel Osorio Calvo
2005-06-14  8:31 ` Alex Zeffertt

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=5359e8b72ccab672f101490b84a1f1c0@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=samuel.osorio@nl.thalesgroup.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 NNTP newsgroup(s).