From: James Hubbard <jameshubbard@gmail.com>
To: Pekka Pietikainen <pp@ee.oulu.fi>
Cc: netdev@oss.sgi.com
Subject: Re: Broadcom 4400 driver bm44
Date: Mon, 26 Jul 2004 09:49:55 -0400 [thread overview]
Message-ID: <f3ddc6d304072606495bf35e6a@mail.gmail.com> (raw)
In-Reply-To: <20040708204346.GA28693@ee.oulu.fi>
On Thu, 8 Jul 2004 23:43:46 +0300, Pekka Pietikainen <pp@ee.oulu.fi> wrote:
> 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.
>
Hello,
Just to let you know, I've not forgotten about this problem. I've got
another Dell laptop that I can reproduce it on. I'm going to try to
get the stock 2.6.7 kernel on it and try it out. Hopefully I can get
you some more information by the end of the week.
James
--
James Hubbard
http://www.mcs.uvawise.edu/~jhubbard
prev parent reply other threads:[~2004-07-26 13:49 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
2004-07-26 13:49 ` James Hubbard [this message]
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=f3ddc6d304072606495bf35e6a@mail.gmail.com \
--to=jameshubbard@gmail.com \
--cc=netdev@oss.sgi.com \
--cc=pp@ee.oulu.fi \
/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.