netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Pietikainen <pp@ee.oulu.fi>
To: James Hubbard <jameshubbard@gmail.com>
Cc: netdev@oss.sgi.com
Subject: Re: Broadcom 4400 driver bm44
Date: Thu, 8 Jul 2004 23:43:46 +0300	[thread overview]
Message-ID: <20040708204346.GA28693@ee.oulu.fi> (raw)
In-Reply-To: <f3ddc6d304070807002a19d340@mail.gmail.com>

On Thu, Jul 08, 2004 at 10:00:26AM -0400, James Hubbard wrote:
> If I can make some time I'll look into writing a test case here also. 
> I just don't know when it will be though.  I've got the source for the
> net comms layer for the apps.  Perhaps I can pull out some code that
> may demonstrate the error.
> 
> Thanks for the help.
Ok, after some digging around ALLMULTI breaking is not a bug, the
vendor-provided driver seems to break in similar ways, at least on 2.6,
so that's a feature unless they fix it in theirs so I can copy the fix :-) 

I put a lots'o'debugging + some bit-flipping reordering to look
more like bcm4400 version at http://www.ee.oulu.fi/~pp/b44-test.tgz.
Probably won't fix the problem, but it's worth a shot I suppose.

Should compile with 

make -C /lib/modules/<version>/build modules SUBDIRS=$PWD

As a workaround I suppose ifconfig eth1 promisc might do the trick too.

  parent reply	other threads:[~2004-07-08 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f3ddc6d3040707112141b20720@mail.gmail.com>
2004-07-08 13:38 ` Broadcom 4400 driver bm44 Pekka Pietikainen
     [not found]   ` <f3ddc6d304070807002a19d340@mail.gmail.com>
2004-07-08 20:43     ` Pekka Pietikainen [this message]
2004-07-26 13:49       ` James Hubbard

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=20040708204346.GA28693@ee.oulu.fi \
    --to=pp@ee.oulu.fi \
    --cc=jameshubbard@gmail.com \
    --cc=netdev@oss.sgi.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).