From: Alessandro Suardi <alessandro.suardi@gmail.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com
Subject: Re: ipw2200 in 2.6.15-rc2-git4 warns about improper NETDEV_TX_BUSY retcode
Date: Fri, 25 Nov 2005 11:59:20 +0100 [thread overview]
Message-ID: <5a4c581d0511250259i3e412c92i57a0bfe82144c81a@mail.gmail.com> (raw)
In-Reply-To: <1132889013.24413.5.camel@debian.sh.intel.com>
On 11/25/05, Zhu Yi <yi.zhu@intel.com> wrote:
> On Fri, 2005-11-25 at 00:38 +0100, Alessandro Suardi wrote:
> > Dell Latitude D610, FC4 base distro, kernel is:
> >
> > [asuardi@sandman ~]$ cat /proc/version
> > Linux version 2.6.15-rc2-git4 (asuardi@sandman) (gcc version 4.0.1
> > 20050727 (Red Hat 4.0.1-5)) #2 Fri Nov 25 00:15:46 CET 2005
> >
> > Onboard wireless card as detected by kernel is:
> > ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.0.8
> >
> > and I placed the 2.4 firmware from sourceforge.net in /lib/firmware.
> >
> > ifup eth1 yields this message:
> >
> > eth1: NETDEV_TX_BUSY returned; driver should report queue full via
> > ieee_device->is_queue_full.
>
> Please use the patch here. It will be push to upstream very soon.
> http://bughost.org/bugzilla/show_bug.cgi?id=808
The offsets of the patch are off by several hundred lines,
however the patch itself works fine. Thanks !
--alessandro
"So much can happen by accident
No rhyme, no reason - no one's innocent"
(Steve Wynn - "Under The Weather")
next prev parent reply other threads:[~2005-11-25 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 23:38 Alessandro Suardi
2005-11-25 3:23 ` Zhu Yi
2005-11-25 10:59 ` Alessandro Suardi [this message]
2005-11-25 13:17 ` Kasper Sandberg
2005-11-25 16:33 ` Alejandro Bonilla Beeche
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=5a4c581d0511250259i3e412c92i57a0bfe82144c81a@mail.gmail.com \
--to=alessandro.suardi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=yi.zhu@intel.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
all inboxes | Powered by JetHome®