[Top] [All Lists]

Re: Broadcom 4400 driver bm44

To: James Hubbard <jameshubbard@xxxxxxxxx>
Subject: Re: Broadcom 4400 driver bm44
From: Pekka Pietikainen <pp@xxxxxxxxxx>
Date: Thu, 8 Jul 2004 23:43:46 +0300
Cc: netdev@xxxxxxxxxxx
In-reply-to: <f3ddc6d304070807002a19d340@xxxxxxxxxxxxxx>
References: <f3ddc6d3040707112141b20720@xxxxxxxxxxxxxx> <20040708133853.GA20254@xxxxxxxxxx> <f3ddc6d304070807002a19d340@xxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.2i
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
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.

<Prev in Thread] Current Thread [Next in Thread>