From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: linux-wireless@vger.kernel.org
Cc: flamingice@sourmilk.net, Hans de Goede <j.w.r.degoede@hhs.nl>
Subject: Recent linux-wireless git changes have broken my prism54pci card
Date: Mon, 13 Aug 2007 07:50:03 +0200 [thread overview]
Message-ID: <46BFF10B.1090307@hhs.nl> (raw)
Hi All,
I first reported this in Fedora bugzilla, as I'm using Fedora with a Fedora
kernel (which includes recent linux-wireless git snapshots), see here for the
Fedora bugreport:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249823
Updating from the Fedora 7 test kernel to the final results in very poor
performance, and going to even newer versions of the Fedora kernel totally
breaks connectivity. Linville thought it would be best to further discuss this
here, so here I am.
I've looked at recent git commits to the prism54 / p54pci driver and have been
trying it revision by revision, eventually I've managed to pin the cause down
to 2 patches, below is a verbatim cut and paste from the bugzilla entry,
containing my analysis:
---
I've been busy researching this and I have come to the
following conclusions.
1) with the 2.6.20-2something F7-test kernel everything works fine build date
3 march, I can give you the exact revision if you want.
2) with the fc release kerkel (3194) things work, but the connection is often lost.
3) with the 2.6.23-0.49.rc1.git3.fc8, the card asociates and thats it.
Using wireless git and out of tree driver building I've found that the following
2 patches are the culprits:
Patch causing loose off connection within seconds when fully loading the link
with a local file transfer:
http://bu3sch.de/gitweb?p=wireless-dev.git;a=commitdiff;h=62ee473d67b7ae353d210b186abaadc37a642237
Only associating and nothing else:
http://bu3sch.de/gitweb?p=wireless-dev.git;a=commitdiff;h=7d59453a9dbe50dc9bab846c410e39f8d5b10c83
And then specifically the changes to prism54common.c
This is with an isl3886 cardbus card, using the p54pci driver.
----
I would be more then happy to test any changes.
Thanks & Regards,
Hans
p.s.
Please keep my CC-ed I'm not on the list.
next reply other threads:[~2007-08-13 5:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 5:50 Hans de Goede [this message]
2007-08-13 6:18 ` Recent linux-wireless git changes have broken my prism54pci card Michael Wu
2007-08-13 6:33 ` Hans de Goede
2007-08-13 6:46 ` Andy Green
2007-08-13 7:49 ` Hans de Goede
2007-08-13 7:58 ` Michael Wu
2007-08-13 8:05 ` Andy Green
2007-08-13 11:58 ` Hans de Goede
2007-08-13 20:14 ` Michael Wu
2007-08-13 22:25 ` Chr
2007-08-14 8:10 ` Hans de Goede
2007-08-14 18:29 ` Chr
2007-08-20 0:44 ` Chr
2007-08-20 2:32 ` Larry Finger
2007-08-20 7:52 ` Hans de Goede
2007-08-20 11:51 ` Chr
2007-08-20 12:17 ` Johannes Berg
2007-08-20 22:14 ` Chr
2007-08-23 11:24 ` Hans de Goede
2007-08-23 14:43 ` Chr
2007-08-23 14:36 ` Hans de Goede
2007-08-23 21:52 ` Hans de Goede
2007-08-23 23:00 ` Chr
2007-08-24 9:45 ` Hans de Goede
2007-08-28 19:32 ` Chr
2007-08-30 5:52 ` Michael Wu
2007-08-30 11:16 ` Chr
2007-08-31 21:27 ` [PATCH 1/2] p54: various fixes Chr
2007-08-31 21:27 ` [PATCH 2/2] p54: disable QoS on older firmwares Chr
2007-09-01 4:58 ` Michael Wu
2007-09-01 16:54 ` [PATCH 2/2 v2] " Chr
2007-08-13 13:14 ` Recent linux-wireless git changes have broken my prism54pci card Johannes Berg
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=46BFF10B.1090307@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=flamingice@sourmilk.net \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).