All of lore.kernel.org
 help / color / mirror / Atom feed
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: BCM5301X: Add support for TP-LINK Archer C5 V2
Date: Sat, 11 Mar 2017 13:05:11 -0800	[thread overview]
Message-ID: <855bc957-8a04-47d6-3355-b641c8f393ad@gmail.com> (raw)
In-Reply-To: <CACna6rzxaqnLShMQRovv4Cr5s6XKSG0NQ2RRrQ+TeePt59bG7A@mail.gmail.com>



On 03/11/2017 09:27 AM, Rafa? Mi?ecki wrote:
> Hi Andrew,
> 
> On 11 March 2017 at 18:23, Andrew Lunn <andrew@lunn.ch> wrote:
>> On Sat, Mar 11, 2017 at 01:14:53PM +0100, Rafa?? Mi??ecki wrote:
>>> From: Rafa?? Mi??ecki <rafal@milecki.pl>
>>>
>>> This is BCM47081A0 based home router with BCM43217 and BCM4352 wireless
>>> chipsets.
>>
>> Have you made any progress with the Ethernet switch? Does anybody know
>> if it is compatible with the SF2/B53 DSA driver?
>>
>> I have a DIR 860l v1 router, using the same chipset. I'm interested in
>> the switch, given my DSA maintainer role.
> 
> I mostly work with LEDE. Just few days ago I managed get kernel 4.9
> running stable (there was a memory corruption caused by iproc PCIe
> controller driver). With kernel 4.9 I can finally start testing b53. I
> should have some news withing new weeks.

FYI, the initial b53 work was done by testing on:
- BCM53010 (SR400AC) and BCM53012 (BCM953012ER)
- BCM58265 (Northstar Plus)
- externally attached BCM53125 to a BCM7445

So let me know if you need guidance/help with getting the 4708/5301X
devices to work.
-- 
Florian

WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>, "Andrew Lunn" <andrew@lunn.ch>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	Russell King <linux@armlinux.org.uk>,
	Rob Herring <robh+dt@kernel.org>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	John Crispin <john@phrozen.org>,
	Rafa?? Mi??ecki <rafal@milecki.pl>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: BCM5301X: Add support for TP-LINK Archer C5 V2
Date: Sat, 11 Mar 2017 13:05:11 -0800	[thread overview]
Message-ID: <855bc957-8a04-47d6-3355-b641c8f393ad@gmail.com> (raw)
In-Reply-To: <CACna6rzxaqnLShMQRovv4Cr5s6XKSG0NQ2RRrQ+TeePt59bG7A@mail.gmail.com>



On 03/11/2017 09:27 AM, Rafał Miłecki wrote:
> Hi Andrew,
> 
> On 11 March 2017 at 18:23, Andrew Lunn <andrew@lunn.ch> wrote:
>> On Sat, Mar 11, 2017 at 01:14:53PM +0100, Rafa?? Mi??ecki wrote:
>>> From: Rafa?? Mi??ecki <rafal@milecki.pl>
>>>
>>> This is BCM47081A0 based home router with BCM43217 and BCM4352 wireless
>>> chipsets.
>>
>> Have you made any progress with the Ethernet switch? Does anybody know
>> if it is compatible with the SF2/B53 DSA driver?
>>
>> I have a DIR 860l v1 router, using the same chipset. I'm interested in
>> the switch, given my DSA maintainer role.
> 
> I mostly work with LEDE. Just few days ago I managed get kernel 4.9
> running stable (there was a memory corruption caused by iproc PCIe
> controller driver). With kernel 4.9 I can finally start testing b53. I
> should have some news withing new weeks.

FYI, the initial b53 work was done by testing on:
- BCM53010 (SR400AC) and BCM53012 (BCM953012ER)
- BCM58265 (Northstar Plus)
- externally attached BCM53125 to a BCM7445

So let me know if you need guidance/help with getting the 4708/5301X
devices to work.
-- 
Florian

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2017-03-11 21:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-11 12:14 [PATCH] ARM: dts: BCM5301X: Add support for TP-LINK Archer C5 V2 Rafał Miłecki
2017-03-11 12:14 ` Rafał Miłecki
2017-03-11 17:23 ` Andrew Lunn
2017-03-11 17:23   ` Andrew Lunn
2017-03-11 17:27   ` Rafał Miłecki
2017-03-11 17:27     ` Rafał Miłecki
2017-03-11 21:05     ` Florian Fainelli [this message]
2017-03-11 21:05       ` Florian Fainelli
2017-03-13 14:31       ` Jon Mason
2017-03-13 14:31         ` Jon Mason
2017-03-12 17:10 ` Andrew Lunn
2017-03-12 17:10   ` Andrew Lunn
2017-03-13 18:48   ` Rafał Miłecki
2017-03-13 18:48     ` Rafał Miłecki
2017-03-13 19:14     ` Andrew Lunn
2017-03-13 19:14       ` Andrew Lunn
2017-03-13 19:15       ` Rafał Miłecki
2017-03-13 19:15         ` Rafał Miłecki
2017-03-13 19:27         ` Jon Mason
2017-03-13 19:27           ` Jon Mason
2017-03-13 21:37           ` Rafał Miłecki
2017-03-13 21:37             ` Rafał Miłecki
2017-03-13 22:33             ` Andrew Lunn
2017-03-13 22:33               ` Andrew Lunn
2017-03-13 19:35         ` Andrew Lunn
2017-03-13 19:35           ` Andrew Lunn
2017-03-13 21:46           ` Rafał Miłecki
2017-03-13 21:46             ` Rafał Miłecki
2017-03-14 10:39 ` [PATCH V2] " Rafał Miłecki
2017-03-14 10:39   ` Rafał Miłecki

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=855bc957-8a04-47d6-3355-b641c8f393ad@gmail.com \
    --to=f.fainelli@gmail.com \
    --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.