From: Larry Finger <Larry.Finger@lwfinger.net>
To: Markus Feldmann <feldmann_markus@gmx.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: BCM4303 on HP zv5265ea
Date: Wed, 04 Mar 2009 15:41:34 -0600 [thread overview]
Message-ID: <49AEF58E.30302@lwfinger.net> (raw)
In-Reply-To: <gomq5f$n64$1@ger.gmane.org>
Markus Feldmann wrote:
> Larry Finger schrieb:
>> I looked at that mail again. Have you figured out how to get your
>> radio switch on?
> I have takled to Matthew Garret. And he told me to check whether i have
> an empty directory </sys/bus/pci/slots/> or not.
> Generally it should be not empty if the <acpiphp> modul works fine.
>
> But thats all i know.
My system has an empty /sys/bus/pci/slots.
> Further on here is what Matthgew Garret said:
> "Some of these systems seem to use PCI express hotplug to handle the
> rfkill. Can you try with the latest git tree, and make sure that you
> have the acpiphp driver built in?"
> AND
> "Go to bus options/Support for PCI Hotplug/ACPI PCI Hotplug driver and
> enable it. You'll probably want it built-in to the kernel."
Did you do that?
> I have some printk statements activated.
> But i don't get more Debug messages than these in my
> old threads, or do you know some special debug kernel
> Options for wireless or general debug options ?
>
> CONFIG_MAC80211_DEBUGFS
> CONFIG_MAC80211_VERBOSE_DEBUG
> CONFIG_MAC80211_VERBOSE_PS_DEBUG
I meant new printk statements that are used to see if hitting your switch causes
any action with RFKILL. I don't know where to put them, nor do I want to take
much time. I have an old BCM4306 and a BCM4301 - both work with b43legacy.
Larry
next prev parent reply other threads:[~2009-03-04 21:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 23:47 BCM4303 on HP zv5265ea Markus Feldmann
2009-03-03 0:05 ` Larry Finger
2009-03-04 14:52 ` Markus Feldmann
2009-03-04 15:18 ` Larry Finger
2009-03-04 21:00 ` Markus Feldmann
2009-03-04 21:41 ` Larry Finger [this message]
2009-03-05 1:18 ` Markus Feldmann
2009-03-05 16:51 ` Larry Finger
2009-03-05 20:32 ` Markus Feldmann
2009-03-05 20:46 ` Larry Finger
2009-03-07 11:41 ` feldmaus
2009-03-04 15:05 ` Markus Feldmann
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=49AEF58E.30302@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=feldmann_markus@gmx.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).