From: Michael Buesch <mb@bu3sch.de>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: John Linville <linville@tuxdriver.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
Mark Huijgen <mark@huijgen.tk>,
Broadcom Wireless <bcm43xx-dev@lists.berlios.de>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] b43: LP-PHY: Remove BROKEN from B43_PHY_LP
Date: Sun, 16 Aug 2009 20:28:01 +0200 [thread overview]
Message-ID: <200908162028.01984.mb@bu3sch.de> (raw)
In-Reply-To: <4A884E71.6070202@gmail.com>
On Sunday 16 August 2009 20:22:41 Gábor Stefanik wrote:
> Larry has reported success getting scan data with an LP-PHY device,
> so it's probably time to release LP-PHY support for testing.
>
> Also disable 802.11a support for now, as 802.11a currently causes
> the driver to panic on startup (NULL pointer dereference).
>
> Signed-off-by: Gábor Stefanik <netrolller.3d@gmail.com>
ack
> ---
> V2:
> -Remove "VERY" from the warning in the symbol name.
> -Remove list of known devices.
> -Don't create a separate symbol for 5GHz, just disable it in the code.
>
> drivers/net/wireless/b43/Kconfig | 14 +++++++-------
> drivers/net/wireless/b43/main.c | 2 ++
> 2 files changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/net/wireless/b43/Kconfig b/drivers/net/wireless/b43/Kconfig
> index 67f564e..237b1aa 100644
> --- a/drivers/net/wireless/b43/Kconfig
> +++ b/drivers/net/wireless/b43/Kconfig
> @@ -80,16 +80,16 @@ config B43_NPHY
> SAY N.
>
> config B43_PHY_LP
> - bool "IEEE 802.11g LP-PHY support (BROKEN)"
> - depends on B43 && EXPERIMENTAL && BROKEN
> + bool "Support for low-power (LP-PHY) devices (EXPERIMENTAL)"
> + depends on B43 && EXPERIMENTAL
> ---help---
> Support for the LP-PHY.
> - The LP-PHY is an IEEE 802.11g based PHY built into some notebooks
> - and embedded devices.
> -
> - THIS IS BROKEN AND DOES NOT WORK YET.
> + The LP-PHY is a low-power PHY built into some notebooks
> + and embedded devices. It supports 802.11a/g
> + (802.11a support is optional, and currently disabled).
>
> - SAY N.
> + This is heavily experimental, and probably will not work for you.
> + Say N unless you want to help debug the driver.
>
> # This config option automatically enables b43 LEDS support,
> # if it's possible.
> diff --git a/drivers/net/wireless/b43/main.c b/drivers/net/wireless/b43/main.c
> index 99b41ce..c5bece0 100644
> --- a/drivers/net/wireless/b43/main.c
> +++ b/drivers/net/wireless/b43/main.c
> @@ -4514,7 +4514,9 @@ static int b43_wireless_core_attach(struct b43_wldev *dev)
> have_5ghz_phy = 1;
> break;
> case B43_PHYTYPE_LP: //FIXME not always!
> +#if 0 //FIXME enabling 5GHz causes a NULL pointer dereference
> have_5ghz_phy = 1;
> +#endif
> case B43_PHYTYPE_G:
> case B43_PHYTYPE_N:
> have_2ghz_phy = 1;
--
Greetings, Michael.
prev parent reply other threads:[~2009-08-16 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 18:22 [PATCH v2] b43: LP-PHY: Remove BROKEN from B43_PHY_LP Gábor Stefanik
2009-08-16 18:28 ` Michael Buesch [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=200908162028.01984.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mark@huijgen.tk \
--cc=netrolller.3d@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 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).