From: "Arend van Spriel" <arend@broadcom.com>
To: "David Herrmann" <dh.herrmann@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"Jonas Gorski" <jogo@openwrt.org>,
"Maximilian Engelhardt" <maxi@daemonizer.de>,
"David Costa" <david@zarel.net>
Subject: Re: [RFT 00/13] brcmsmac: bcm4313 iPA related patches
Date: Wed, 14 Aug 2013 20:16:30 +0200 [thread overview]
Message-ID: <520BC97E.9070505@broadcom.com> (raw)
In-Reply-To: <CANq1E4SOcT765CTFCR=xywBuMkOs5oru-NBqwHM=Jj_dfwtvkw@mail.gmail.com>
On 08/14/2013 12:33 PM, David Herrmann wrote:
> Hi
>
> On Tue, Aug 13, 2013 at 10:46 PM, Arend van Spriel <arend@broadcom.com> wrote:
>> On 08/13/2013 10:09 PM, David Herrmann wrote:
>>>
>>> Hi
>>>
>>> On Tue, Aug 13, 2013 at 10:03 PM, Arend van Spriel <arend@broadcom.com>
>>> wrote:
>>>>
>>>> This series replaces the patch "[PATCH 12/12] brcmsmac: support 4313iPA"
>>>> with Message-ID: <1376130450-29746-13-git-send-email-arend@broadcom.com>.
>>>>
>>>> It has been split up into individual patches. Please test this series
>>>> especially if you had issues with the original commit b6fc28a that was
>>>> reverted.
>>>>
>>>> Cc: Jonas Gorski <jogo@openwrt.org>
>>>> Cc: David Herrmann <dh.herrmann@gmail.com>
>>>> Cc: Maximilian Engelhardt <maxi@daemonizer.de>
>>>> Cc: David Costa <david@zarel.net>
>>>
>>>
>>> Is this available in a public branch that I can merge? And what should
>>> be used as base? 3.11-rc5? linux-next?
>>
>>
>> Indeed I should have mentioned. It applies on v3.11-rc5 for sure. Did not
>> try linux-next.
>
> All 13 patches applied cleanly on top of 3.11-rc5, everything works
> fine even after a dozen of reconnects to different networks. No
> additional delays.
>
> Consider this whole series:
> Tested-by: David Herrmann <dh.herrmann@gmail.com>
>
> card info: Broadcom Corporation BCM4313 802.11b/g/n (0a5c:219c)
> (builtin into my old Intel Atom N450 board)
> I tested with 802.11g networks. I have only a/g networks here. I don't
> know whether that matters.
As this series modifies the phy code, I would say no.
Thanks for verifying this works for you.
Regards,
Arend
next prev parent reply other threads:[~2013-08-14 18:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 20:03 [RFT 00/13] brcmsmac: bcm4313 iPA related patches Arend van Spriel
2013-08-13 20:03 ` [RFT V2 01/13] brcmsmac: cosmetic change in phy_lcn.c Arend van Spriel
2013-08-13 20:03 ` [RFT V2 02/13] brcmsmac: change pa_gain for bcm4313 iPA Arend van Spriel
2013-08-21 19:18 ` Hauke Mehrtens
2013-08-22 8:08 ` Arend van Spriel
2013-08-13 20:03 ` [RFT V2 03/13] brcmsmac: use ARRAY_SIZE in phytbl_lcn.c Arend van Spriel
2013-08-13 20:03 ` [RFT V2 04/13] brcmsmac: add switch control table for BCM4313 iPA BT-combo cards Arend van Spriel
2013-08-13 20:03 ` [RFT V2 05/13] brcmsmac: add debug info message providing phy and radio info Arend van Spriel
2013-08-13 20:03 ` [RFT V2 06/13] brcmsmac: update transmit gain table for lcn phy Arend van Spriel
2013-08-13 20:03 ` [RFT V2 07/13] brcmsmac: change lcnphy receive i/q calibration routine Arend van Spriel
2013-08-13 20:03 ` [RFT V2 08/13] brcmsmac: fix TSSI idle estimation Arend van Spriel
2013-08-13 20:03 ` [RFT V2 09/13] brcmsmac: avoid calling set_txpwr_by_index() twice Arend van Spriel
2013-08-13 20:03 ` [RFT V2 10/13] brcmsmac: rework switch control table init including iPA BT-combo Arend van Spriel
2013-08-13 20:03 ` [RFT V2 11/13] brcmsmac: correct phy registers for TSSI-based power control Arend van Spriel
2013-08-13 20:03 ` [RFT V2 12/13] brcmsmac: reinitialize TSSI power control upon channel switch Arend van Spriel
2013-08-13 20:03 ` [RFT V2 13/13] brcmsmac: add support for BCM4313 iPA variant Arend van Spriel
2013-08-13 20:09 ` [RFT 00/13] brcmsmac: bcm4313 iPA related patches David Herrmann
2013-08-13 20:46 ` Arend van Spriel
2013-08-14 10:33 ` David Herrmann
2013-08-14 18:16 ` Arend van Spriel [this message]
2013-08-21 16:17 ` Maximilian Engelhardt
2013-08-21 19:00 ` 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=520BC97E.9070505@broadcom.com \
--to=arend@broadcom.com \
--cc=david@zarel.net \
--cc=dh.herrmann@gmail.com \
--cc=jogo@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=maxi@daemonizer.de \
/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).