From: "Rune Torgersen" <runet@innovsys.com>
To: <alebas@televes.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Bridge, promiscous mode andCPM2
Date: Fri, 8 Oct 2004 09:02:08 -0500 [thread overview]
Message-ID: <DCEAAC0833DD314AB0B58112AD99B93B06DB7B@ismail.innsys.innovsys.com> (raw)
Hi
Assuming CPM2 =3D> 82xx or 85xx CPU.
In the old 8260_io/fcc_enet.c the set_multicast_list=20
function is present, bu has an early return nine lines=20
in. If you delete that return, promiscous mode works great.
I have no idea who or why that early return was put in,=20
but it does disable multicast and promiscous mode=20
on the FCC ethernets.
> -----Original Message-----
> From: linuxppc-embedded-bounces@ozlabs.org=20
> [mailto:linuxppc-embedded-bounces@ozlabs.org] On Behalf Of=20
> alebas@televes.com
> Sent: Friday, October 08, 2004 04:29
> To: linuxppc-embedded@ozlabs.org
> Subject: Bridge, promiscous mode andCPM2
>=20
>=20
>=20
> Hi,
>=20
> I would need confirmation on this.
>=20
> As long as I have seen, bridge's stuff in kernel sets=20
> promiscous mode by using dev_set_promiscuity, which arrives=20
> in the execution of fcc_enet's set_multicast_list.
>=20
> But this function is not developed, so the promiscous mode is=20
> never set in the FCC Ethernet Mode Register.
>=20
> Am I right? By now, I only needs the promiscous mode, so,=20
> could it be a solution to implement only this functionality=20
> in the set_multicast_list function? Do I need to consider=20
> anything else?
>=20
> Best regards
>=20
> Alexandre Bastos _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org=20
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20
>=20
next reply other threads:[~2004-10-08 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 14:02 Rune Torgersen [this message]
2004-10-08 15:39 ` Bridge, promiscous mode andCPM2 Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2004-10-13 7:54 Bastos Fernandez Alexandre
2004-10-13 7:46 bridge, promiscous mode andcpm2 Bastos Fernandez Alexandre
2004-10-08 9:28 Bridge, promiscous mode andCPM2 alebas
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=DCEAAC0833DD314AB0B58112AD99B93B06DB7B@ismail.innsys.innovsys.com \
--to=runet@innovsys.com \
--cc=alebas@televes.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