From: Benjamin Adler <benadler@gmx.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: brcm80211 development <brcm80211-dev-list@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: BCM4330 linux support
Date: Sat, 07 Feb 2015 01:53:53 +0000 [thread overview]
Message-ID: <54D57031.9090903@gmx.net> (raw)
In-Reply-To: <54D4E509.3090308@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
On 06.02.2015 16:00, Arend van Spriel wrote:
> version 5.97.39.4 FWID 01-c7b9d775
>
> The FWID should tell me what specific build this was and what feature
> set it contains. Unfortunately I can not access our database.
>
>> Does AP also work for you?
>
> Yes, but not sure if your firmware supports it.
Who can I ask for this information?
> The errors are direct result of wpa_supplicant request, but it is not
> root cause. I suspend the sdhci-acpi controller driver to use
> runtime-pm. Could you try disabling that through sysfs? If I am not
> mistaken the bcm4330 is in mmc1.
>
> mmc1: SDHCI controller on ACPI [INT33BB:00] using ADMA
>
> So following should do the trick (as root):
>
> # echo on > /sys/bus/acpi/INT33BB:00/power/control
# cat /sys/bus/acpi/devices/INT33BB\:00/power_state
D3cold
# cat /sys/bus/acpi/devices/INT33BB\:00/status
15
# echo on > /sys/bus/acpi/devices/INT33BB\:00/power/control
# cat /sys/bus/acpi/devices/INT33BB\:00/power_state
D3cold
# cat /sys/bus/acpi/devices/INT33BB\:00/status
15
That doesn't seem to work?! I tried booting with "acpi=off", but it
didn't boot successfully. I know there are ACPI woes with this box, see
http://www.spinics.net/lists/linux-acpi/msg55693.html
You were right about not having the debug option compiled into the
module. So I built 3.18 (not 3.19 anymore) and my new dmesg is attached.
Cheers,
Ben
[-- Attachment #2: dmesg.tar.gz --]
[-- Type: application/gzip, Size: 28077 bytes --]
next prev parent reply other threads:[~2015-02-07 1:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54D3FF89.502@phoenix-aerial.com>
2015-02-06 9:10 ` BCM4330 linux support Arend van Spriel
2015-02-06 14:45 ` Ben Adler
2015-02-06 16:00 ` Arend van Spriel
2015-02-07 1:53 ` Benjamin Adler [this message]
2015-02-07 18:12 ` Arend van Spriel
2015-02-07 19:14 ` Benjamin Adler
2015-02-07 19:37 ` Arend van Spriel
2015-02-07 22:20 ` Benjamin Adler
2015-02-06 16:06 ` Arend van Spriel
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=54D57031.9090903@gmx.net \
--to=benadler@gmx.net \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--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).