On 04-09-17 16:42, Antony Antony wrote:
Hi Arend,
On Fri, Sep 01, 2017 at 11:30:59PM +0200, Arend van Spriel wrote:
Hi Rob,
Actually the Broadcom wifi chips themselves are discoverable. So once the
driver has access to the register space of the device it can determine the
actual chip, its revi
Hi Arend,
On Fri, Sep 01, 2017 at 11:30:59PM +0200, Arend van Spriel wrote:
> > > Hi Rob,
> > >
> > > Actually the Broadcom wifi chips themselves are discoverable. So once the
> > > driver has access to the register space of the device it can determine the
> > > actual chip, its revision, and exa
On 01-09-17 23:38, Rob Herring wrote:
On Fri, Sep 1, 2017 at 2:10 PM, Arend van Spriel
wrote:
On 01-09-17 18:49, Rob Herring wrote:
On Wed, Aug 30, 2017 at 02:02:18PM +0200, Antony Antony wrote:
hi,
On Wed, Aug 30, 2017 at 10:28:20AM +0800, Chen-Yu Tsai wrote:
On Wed, Aug 30, 2017 at 5
On Fri, Sep 1, 2017 at 2:10 PM, Arend van Spriel
wrote:
> On 01-09-17 18:49, Rob Herring wrote:
>>
>> On Wed, Aug 30, 2017 at 02:02:18PM +0200, Antony Antony wrote:
>>>
>>> hi,
>>>
>>> On Wed, Aug 30, 2017 at 10:28:20AM +0800, Chen-Yu Tsai wrote:
On Wed, Aug 30, 2017 at 5:43 AM, Antony A
On 01-09-17 22:40, Antony Antony wrote:
On Fri, Sep 01, 2017 at 09:10:41PM +0200, Arend van Spriel wrote:
On 01-09-17 18:49, Rob Herring wrote:
On Wed, Aug 30, 2017 at 02:02:18PM +0200, Antony Antony wrote:
hi,
On Wed, Aug 30, 2017 at 10:28:20AM +0800, Chen-Yu Tsai wrote:
On Wed, Aug 30, 201
On Fri, Sep 01, 2017 at 09:10:41PM +0200, Arend van Spriel wrote:
> On 01-09-17 18:49, Rob Herring wrote:
> > On Wed, Aug 30, 2017 at 02:02:18PM +0200, Antony Antony wrote:
> > > hi,
> > >
> > > On Wed, Aug 30, 2017 at 10:28:20AM +0800, Chen-Yu Tsai wrote:
> > > > On Wed, Aug 30, 2017 at 5:43 AM,
On 01-09-17 18:49, Rob Herring wrote:
On Wed, Aug 30, 2017 at 02:02:18PM +0200, Antony Antony wrote:
hi,
On Wed, Aug 30, 2017 at 10:28:20AM +0800, Chen-Yu Tsai wrote:
On Wed, Aug 30, 2017 at 5:43 AM, Antony Antony wrote:
a/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.tx
On Wed, Aug 30, 2017 at 02:02:18PM +0200, Antony Antony wrote:
> hi,
>
> On Wed, Aug 30, 2017 at 10:28:20AM +0800, Chen-Yu Tsai wrote:
> > On Wed, Aug 30, 2017 at 5:43 AM, Antony Antony wrote:
>
> > > a/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt
> > > +++ b/Documentatio
hi,
On Wed, Aug 30, 2017 at 10:28:20AM +0800, Chen-Yu Tsai wrote:
> On Wed, Aug 30, 2017 at 5:43 AM, Antony Antony wrote:
> > a/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt
> > +++ b/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt
> > @@ -6,7 +6,9 @@
Hi,
On Wed, Aug 30, 2017 at 5:43 AM, Antony Antony wrote:
> Add device tree binding documentation for Broadcom BCM43430
> AMPAK AP6212A has this chip.
>
> e.g
> compatible = "brcm,bcm43430-fmac";
>
> NanoPi NEO Plus2 has an AMPAK AP6212A WiFi module
> with BCM43430 rev=1 inside.
> brcmf_chip_reco
Add device tree binding documentation for Broadcom BCM43430
AMPAK AP6212A has this chip.
e.g
compatible = "brcm,bcm43430-fmac";
NanoPi NEO Plus2 has an AMPAK AP6212A WiFi module
with BCM43430 rev=1 inside.
brcmf_chip_recognition found AXI chip: BCM43430, rev=1
brcmf_ops_sdio_probe sdio vendor ID:
11 matches
Mail list logo