linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Samuel Osorio Calvo" <samuel.osorio@nl.thalesgroup.com>
To: <ajz@cambridgebroadband.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: multicast disabled on 8260_io/fcc_enet.c
Date: Wed, 15 Jun 2005 15:14:34 +0200	[thread overview]
Message-ID: <s2b045ef.027@scms1.sc.signaal.nl> (raw)

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....

Samuel.


Unclassified.
>>> Alex Zeffertt <ajz@cambridgebroadband.com> 06/14/05 10:31AM >>>

On Mon, 13 Jun 2005 18:14:06 +0200
"Samuel Osorio Calvo" <samuel.osorio@nl.thalesgroup.com> wrote:

> Hi all!
>=20
> I was playing with a mpc8260 board and the latest ELDK version, 3.1.1
> (linux 2.4.25) and face a strange behaviour:
>=20
> I was trying to make multicast work and everything seemed to be ok
> (/proc/net/igmp, /proc/net/dev_mcast), making a local ping to
> 224.0.0.1 returns localhost as part of the group, etc....BUT it was
> not possible to contact the board to the group it had joined from the
> network. I was digging into the kernel drivers and found a strange
> return statement just in teh start of the funciton set_multicast_list
> (arround line 1471 of the file mentioned in the subject of the mail).
> I moved the return to the end of the function and everything worked
> perfectly.
>=20
> My question is wether the return statement was moved at the starting
> of the function due to some bug of the set_multicast_list code or it
> was just a typo???
>=20


According to

	http://ozlabs.org/pipermail/linuxppc-embedded/2005-May/018529.html=
=20

it would seem that multicast is not correctly implemented and has been
effectively commented out.  This also stops promisc mode working.  I
have removed the return in my source tree and promisc mode now works
fine. I can't say whether multicast works.  Maybe you could just give it
a try and see what happens....

Alex

             reply	other threads:[~2005-06-15 13:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 13:14 Samuel Osorio Calvo [this message]
2005-06-16  1:03 ` multicast disabled on 8260_io/fcc_enet.c Dan Malek
  -- 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=s2b045ef.027@scms1.sc.signaal.nl \
    --to=samuel.osorio@nl.thalesgroup.com \
    --cc=ajz@cambridgebroadband.com \
    --cc=linuxppc-embedded@ozlabs.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 NNTP newsgroup(s).