From: Bastos Fernandez Alexandre <ALEBAS@televes.com>
To: 'Dan Malek' <dan@embeddededge.com>
Cc: "'linuxppc-embedded@ozlabs.org'" <linuxppc-embedded@ozlabs.org>
Subject: RE: Bridge, promiscous mode andCPM2
Date: Wed, 13 Oct 2004 09:54:52 +0200 [thread overview]
Message-ID: <51DB8827D393D411BB69003048003F46FDCF2B@tvesntr.televes.com> (raw)
So,
Is this patch available? Will it be available soon or applied to any ppc
kernel tree?
This is in my to-do list for the near future, so it would be very helpful if
this were already done.
Best regards,
Alex
> -----Original Message-----
> From: Dan Malek [SMTP:dan@embeddededge.com]
> Sent: Friday, October 08, 2004 5:40 PM
> To: Rune Torgersen
> Cc: alebas@televes.com; linuxppc-embedded@ozlabs.org
> Subject: Re: Bridge, promiscous mode andCPM2
>
>
> On Oct 8, 2004, at 10:02 AM, Rune Torgersen wrote:
>
> > Assuming CPM2 => 82xx or 85xx CPU.
>
> Yes.
>
> > I have no idea who or why that early return was put in,
> > but it does disable multicast and promiscous mode
> > on the FCC ethernets.
>
> Because I never wrote (or lifted from somewhere else)
> the function to run the CRC generator for creating the
> multicast filters (the CPM1 on 8xx has hardware support
> for this). I left the function there as a place holder to get
> promiscuous mode, and someone did finish that function.
> It should be in one of the several kernel source trees......
> If not, I'll try to find the patch and do it again.
>
>
> -- Dan
next reply other threads:[~2004-10-13 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 7:54 Bastos Fernandez Alexandre [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-13 7:46 bridge, promiscous mode andcpm2 Bastos Fernandez Alexandre
2004-10-08 14:02 Bridge, promiscous mode andCPM2 Rune Torgersen
2004-10-08 15:39 ` Dan Malek
2004-10-08 9:28 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=51DB8827D393D411BB69003048003F46FDCF2B@tvesntr.televes.com \
--to=alebas@televes.com \
--cc=dan@embeddededge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.