public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ludovic Drolez <ldrolez@linbox.com>
To: linux-kernel@vger.kernel.org
Subject: transmit timeouts with b44 and 2.6.2
Date: Fri, 05 Mar 2004 17:13:51 +0100	[thread overview]
Message-ID: <4048A73F.7030005@linbox.com> (raw)

Hi !

We have a bcm 4400 based NIC which has transmit timeouts with the b44 module. It 
works fine with broadcom's bcm4400 module and a 2.4.x module.

These bug entries,

http://bugzilla.kernel.org/show_bug.cgi?id=664
http://bugzilla.kernel.org/show_bug.cgi?id=257

seem to say that they are no problems left, but this card is still not working 
with my 2.6 kernel.

So is someone still working on the bugs ?
Why not integrating the bcm4400 module (GPLed) and droping this buggy b44 module ?

Regards,

-- 
Ludovic DROLEZ                                       Free&ALter Soft
152, rue de Grigy - Technopole Metz 2000                  57070 METZ
tel : 03 87 75 55 21                            fax : 03 87 75 19 26



             reply	other threads:[~2004-03-05 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05 16:13 Ludovic Drolez [this message]
     [not found] <4048B632.25551.483318ED@localhost>
2004-03-09 13:27 ` transmit timeouts with b44 and 2.6.2 Ludovic Drolez

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=4048A73F.7030005@linbox.com \
    --to=ldrolez@linbox.com \
    --cc=linux-kernel@vger.kernel.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