From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Ismael Luceno <ismael@iodev.co.uk>
Cc: linux-wireless@vger.kernel.org, brcm80211-dev-list@broadcom.com
Subject: Re: [PATCH] brcmfmac: Add USB ID for Cisco Linksys AE1200
Date: Wed, 22 Jun 2016 21:07:08 +0200 [thread overview]
Message-ID: <576AE1DC.7050203@broadcom.com> (raw)
In-Reply-To: <20160622183622.uo5avhsjzmnn6jgf@pirotess>
On 22-06-16 20:36, Ismael Luceno wrote:
> On 21/Jun/2016 21:02, Arend van Spriel wrote:
>> On 21-06-16 02:18, Ismael Luceno wrote:
>>> Signed-off-by: Ismael Luceno <ismael@iodev.co.uk>
>>
>> A bit more description would be nice. I am actually wondering why you
>> would be adding this. If I am not mistaken the AE1200 can not be handled
>> by brcmfmac. Otherwise I am interested in a kernel log showing the
>> device probe sequence with brcmfmac loaded with parameter debug=0x1416.
>
> Log attached.
>
> I was surprised it works without any tweaking.
Nice. What kernel version are you running on. Can you also dump a
debugfs file, ie. /sys/kernel/debug/brcmfmac/*/revinfo. I want to know
what chip id and revision is reported. I have tried an AE1200 in the
past, but it had a chip revision that had insufficient memory to run
fullmac firmware. Is there FCC registration number on it?
Regards,
Arend
> There's quite a lot of unhelpful noise about those adapters, but not
> much actual information, I couldn't find anything about those that
> supposedly don't work, so I have no idea if it's just a different
> firmware version or what did change (if anything).
>
next prev parent reply other threads:[~2016-06-22 19:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 0:18 [PATCH] brcmfmac: Add USB ID for Cisco Linksys AE1200 Ismael Luceno
2016-06-21 5:45 ` Rafał Miłecki
2016-06-21 16:58 ` Ismael Luceno
2016-06-21 17:27 ` Rafał Miłecki
2016-06-21 19:02 ` Arend van Spriel
2016-06-22 18:36 ` Ismael Luceno
2016-06-22 19:07 ` Arend van Spriel [this message]
2016-06-22 20:54 ` Ismael Luceno
2016-08-20 15:17 ` Ismael Luceno
2016-08-20 17:10 ` Rafał Miłecki
2016-08-20 19:22 ` 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=576AE1DC.7050203@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=ismael@iodev.co.uk \
--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 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.