From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: dts: cubox-i: add support for Broadcom Wifi/Bluetooth devices
Date: Mon, 18 May 2015 14:38:48 +0100 [thread overview]
Message-ID: <20150518133848.GX2067@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CALHpu35HB4NgtSwc8zJBffrfsD0Kk9++_5kw4K_j2FuUf9sCzQ@mail.gmail.com>
On Mon, May 18, 2015 at 02:47:32PM +0200, Jon Nettleton wrote:
> okay tested. Looks good on both the 4330 and 4329.
>
> Signed-off-by: Jon Nettleton <jon@solid-run.com>
Seems to work on the 4329 on the Cubox-i4, although I see an additional
error which didn't appear first time with my original patches:
brcmfmac: brcmf_setup_wiphybands: rxchain error (-52)
It seems to be repeatable, and I'm guessing from a brief look at the code
that "rxchain" is something that's requested from the firmware (my 4329
firmware is v4.220.48). Why it didn't appear first time around I've no
idea.
Apart from that, iw dev wlan0 scan appears to find my local hostap, and
as usual none of the BTHub stuff that have flooded the area.
I'll drop my patches in favour of this one. Shawn, please go ahead and
merge it.
Tested-by: Russell King <rmk+kernel@arm.linux.org.uk>
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-05-18 13:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 15:38 [PATCH v3] ARM: dts: cubox-i: add support for Broadcom Wifi/Bluetooth devices Fabio Estevam
2015-05-18 11:34 ` Shawn Guo
2015-05-18 11:55 ` Russell King - ARM Linux
2015-05-18 12:10 ` Shawn Guo
[not found] ` <CALHpu36rJuRWum+TGrM4cchKLxSVVup0cB58dFxANF=mAzLA0Q@mail.gmail.com>
2015-05-18 12:47 ` Jon Nettleton
2015-05-18 12:56 ` Fabio Estevam
2015-05-18 12:57 ` Jon Nettleton
2015-05-18 13:38 ` Russell King - ARM Linux [this message]
2015-05-19 1:46 ` Shawn Guo
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=20150518133848.GX2067@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.