From: "Michael Büsch" <m@bues.ch>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
b43-dev@lists.infradead.org, larry.finger@lwfinger.net,
florian@openwrt.org
Subject: Re: [RFT][PATCH] b43: fix logic in GPIO configuration
Date: Wed, 7 Mar 2012 00:32:21 +0100 [thread overview]
Message-ID: <20120307003221.7664eb4a@milhouse> (raw)
In-Reply-To: <4F5695CC.3010206@hauke-m.de>
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
On Tue, 06 Mar 2012 23:55:08 +0100
Hauke Mehrtens <hauke@hauke-m.de> wrote:
> This patch did not helped fixing my problem. The ucode still takes over
> the GPIOs of the buttons with firmware version 666.2. I am getting the
> following messages:
>
> [ 83.620000] b43-phy0: Loading firmware version 666.2 (2011-02-23
> 01:15:07)
> [ 83.624000] Init value of B43_GPIO_CONTROL: 0x0
I think this is caused by b43_gpio_cleanup. Can you try removing that function (or just returning early, for the time being.)
--
Greetings, Michael.
PGP encryption is encouraged / 908D8B0E
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-06 23:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 22:11 [RFT][PATCH] b43: fix logic in GPIO configuration Rafał Miłecki
2012-03-06 21:59 ` Michael Büsch
2012-03-06 22:55 ` Hauke Mehrtens
2012-03-06 23:32 ` Michael Büsch [this message]
2012-03-07 6:54 ` Rafał Miłecki
2012-03-07 6:52 ` Rafał Miłecki
2012-03-07 7:23 ` Rafał Miłecki
2012-03-09 23:17 ` Hauke Mehrtens
2012-03-10 4:50 ` Rafał Miłecki
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=20120307003221.7664eb4a@milhouse \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.org \
--cc=florian@openwrt.org \
--cc=hauke@hauke-m.de \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=zajec5@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).