From: Larry Finger <Larry.Finger@lwfinger.net>
To: Chr <chunkeey@web.de>
Cc: John W Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] p54: Fix for TX sequence number problem that resulted from commit 741b4fbc44
Date: Sat, 09 Aug 2008 13:11:54 -0500 [thread overview]
Message-ID: <489DDDEA.2030604@lwfinger.net> (raw)
In-Reply-To: <200808091843.41985.chunkeey@web.de>
Chr wrote:
> hmm? there are lots of new & old firmwares.
> what chip do you have? a ISL3886 + net2280 or a ISL3887?
> you can get the firmware version from dmesg, just load the
> driver and grep for "p54: FW rev"
>
> my devices:
> isl3880 minipci: 2.7.0.0 (best supported) & 2.13.1.0 (unstable)
> isl3887 usb: 2.5.8.0(bugs), 2.6.16.0(DELL bugs) and 2.13.2.0 (WIP)
>
From dmesg:
firmware: requesting isl3887usb_bare
p54: LM86 firmware
p54: FW rev 2.5.8.0 - Softmac protocol 3.0
I think this shows that I have an ISL3887. As further confirmation, it
uses routine p54u_tx_3887() to transmit. Are the bugs in 2.5.8.0 and
2.6.16.0 described on the Web? My device is a Dell DW1450.
The 2-3 hour disconnect is still present with the sequence number
patch reverted and the MTU at 1300. Still testing.
Larry
next prev parent reply other threads:[~2008-08-09 18:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 16:23 [PATCH] p54: Fix for TX sequence number problem that resulted from commit 741b4fbc44 Larry Finger
2008-08-08 8:26 ` Chr
2008-08-08 14:29 ` Larry Finger
2008-08-08 18:38 ` Chr
2008-08-09 16:02 ` Larry Finger
2008-08-09 16:43 ` Chr
2008-08-09 18:11 ` Larry Finger [this message]
2008-08-10 14:19 ` Larry Finger
2008-08-10 22:27 ` Chr
2008-08-10 23:04 ` Larry Finger
2008-08-13 22:15 ` Chr
2008-08-15 18:34 ` Chr
2008-08-15 19:26 ` Johannes Berg
2008-08-15 20:15 ` Chr
2008-08-15 20:17 ` Johannes Berg
2008-08-15 21:06 ` Chr
2008-08-15 21:13 ` Johannes Berg
2008-08-16 0:34 ` Larry Finger
2008-08-16 2:21 ` Chr
2008-08-16 14:00 ` Larry Finger
2008-08-16 14:38 ` Chr
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=489DDDEA.2030604@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chunkeey@web.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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.