From: Christian Lamparter <chunkeey@web.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org,
John W Linville <linville@tuxdriver.com>,
Pavel Roskin <proski@gnu.org>, Tomas Winkler <tomasw@gmail.com>
Subject: Re: [PATCH v2] p54usb: support LM87 firmwares
Date: Sun, 7 Sep 2008 02:56:41 +0200 [thread overview]
Message-ID: <200809070256.42582.chunkeey@web.de> (raw)
In-Reply-To: <48C32138.4000700@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]
On Sunday 07 September 2008 02:32:56 Larry Finger wrote:
> Chr wrote:
> > On Sunday 07 September 2008 01:33:29 Larry Finger wrote:
> >> Chr wrote:
> >>> But, for newer firmwares you'll need "p54: better firmware support"
> >>> (cc4b0cbf4ab) as well. This changes were merged about 25-26 hours ago
> >>> into wireless-testing, the only thing that isn't in yet is 802.11a
> >>> support....
> >>>
> >>> the LM87 firmware is this one:
> >>> http://daemonizer.de/prism54/prism54-fw/fw-usb/2.13.1.0.arm.1
> >>>
> >>> This link can be found on the driver's site too:
> >>> http://linuxwireless.org/en/users/Drivers/p54
> >>
> >> Thanks. That one fixed the ping problem. I had the latest
> >> wireless-testing, and have added the patches you posted earlier today.
> >
> > Well, since you already do some testing here. Want more? ;-)
> >
> > I will be off for about 4-5 weeks and it would be very nice if someone
> > with lots of broadcom hardware can test if the p54 works ADHOC & AP mode
> > with them.
> >
> > i've already (successfully) tested Intel's 2915 & 4965, several atheros
> > chipsets and another prism54 on different operating systems.
> >
> > But there could be problems with some broadcom chips.
>
> I'll see what I can do.
>
> After loading the new firmware, p54usb crapped out after the following
> message was logged:
>
> phy9: not handling 0x02 type control frame
>
> After this, I had to unload and reload the driver. I have not yet had
> time to check on it.
>
Do you have a big-endian machine by accident?
Anyway control flags with 0x02 is some sort of scanning trap...
These packages can be produces easily by setting chan->flags = 2 (or 4,6?)
and setting the dwell timers as well in p54_set_freq.
Since we don't do this, is there any chance you can hexdump
the unknown/corrupted frames?
and as a last shot: try another firmware, maybe this one works better for you.
Regards,
Chr
[-- Attachment #2: 2.13.3.lm87.arm --]
[-- Type: application/octet-stream, Size: 29092 bytes --]
prev parent reply other threads:[~2008-09-07 0:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 19:39 [PATCH] p54usb: support LM87 firmwares Christian Lamparter
2008-09-02 23:14 ` Tomas Winkler
2008-09-03 0:00 ` Christian Lamparter
2008-09-04 1:44 ` Pavel Roskin
2008-09-04 10:29 ` [PATCH v2] " Christian Lamparter
2008-09-06 22:57 ` Larry Finger
2008-09-06 23:19 ` Chr
2008-09-06 23:33 ` Larry Finger
2008-09-07 0:25 ` Chr
2008-09-07 0:32 ` Larry Finger
2008-09-07 0:56 ` Christian Lamparter [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=200809070256.42582.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=proski@gnu.org \
--cc=tomasw@gmail.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.