From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: linux-wireless@vger.kernel.org
Subject: b43: Debugging PHY TX errors
Date: Thu, 24 Jul 2008 13:30:15 +0200 [thread overview]
Message-ID: <200807241330.15439.mb@bu3sch.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
I hacked up some scripts for debugging of the PHY transmission
errors. It consists of two parts. One patch that has to be applied
to the kernel driver (latest wireless-testing!) and one firmware
binary patcher script (for latest supported firmware only!)
Both are included in the attached tarball. Extract the tarball.
So you first have to apply the included "b43-kernel-patch.patch" to
the kernel driver and recompile your kernel.
Then you have to patch your firmware by doing:
cd phyerr-patcher-001
bash ./patch-phyerr-logger.sh /lib/firmware/b43/ucode5.fw
You might have to adjust the path to your firmware.
On successful patching, the script will exit with a nice smilie: :)
So when running the modified driver with the patched firmware, it should
dump the shared memory every time a PHY error occurs.
More state dumps can be added to the kernel driver. The firmware is halted
while the phyerr logger function is running, so state should be consistent.
WARNING: This patch might kill your cat, or at least disturb your wireless
connectivity. Only use it for debugging the PHY transmission errors.
Note that these scripts require a complete compiler toolchain, including
flex and bison, on your machine, as it will compile the assembler and
disassembler tools.
--
Greetings Michael.
[-- Attachment #2: phyerr-patcher-001.tar.bz2 --]
[-- Type: application/x-tbz, Size: 58586 bytes --]
next reply other threads:[~2008-07-24 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 11:30 Michael Buesch [this message]
2008-07-24 15:06 ` b43: Debugging PHY TX errors Stefanik Gábor
2008-07-24 21:13 ` Michael Buesch
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=200807241330.15439.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--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).