From: Larry Finger <Larry.Finger@lwfinger.net>
To: John Linville <linville@tuxdriver.com>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Your netbook
Date: Tue, 30 Mar 2010 10:23:51 -0500 [thread overview]
Message-ID: <4BB21787.4040501@lwfinger.net> (raw)
John,
If possible, I would like you to do one more test on that troublesome netbook.
Please build a kernel with CONFIG_MMIOTRACE=y and build the Broadcom wl driver
for it. Starting with wl unloaded, issue the following commands (as root):
echo 10000 > /sys/kernel/debug/tracing/buffer_size_kb
echo mmiotrace > /sys/kernel/debug/tracing/current_tracer
cat /sys/kernel/debug/tracing/trace_pipe > wl_dump.txt &
modprobe -v wl
After the wireless network device gets created, etc., then
echo nop > /sys/kernel/debug/tracing/current_tracer
sleep 1
killproc cat
and send me the file wl_dump.txt. With it, I will be able to see if the Broadcom
driver is actually finding an SPROM that b43 is missing.
Thanks,
Larry
next reply other threads:[~2010-03-30 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 15:23 Larry Finger [this message]
2010-03-30 20:28 ` Your netbook John W. Linville
2010-03-30 20:50 ` Larry Finger
2010-03-30 21:30 ` Larry Finger
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=4BB21787.4040501@lwfinger.net \
--to=larry.finger@lwfinger.net \
--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 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).