Re: [RFC PATCH 4/7] ath79: prepare for 1-port TP-Link EAP2x5 devices

2020-07-19 Thread David Bauer
Hello Sander, On 7/18/20 10:40 PM, Sander Vanheule wrote: > Hi David, > > On Sat, 2020-07-18 at 21:45 +0200, David Bauer wrote: >>> + gmac-config { >>> + device = <&gmac>; >>> + >>> + rgmii-ge0 = <1>; >>> + ge0-sgmii = <1>; >>> + rxdv-delay = <3>; >>> +

Re: [RFC PATCH 4/7] ath79: prepare for 1-port TP-Link EAP2x5 devices

2020-07-18 Thread Sander Vanheule
Hi David, On Sat, 2020-07-18 at 21:45 +0200, David Bauer wrote: > > + gmac-config { > > + device = <&gmac>; > > + > > + rgmii-ge0 = <1>; > > + ge0-sgmii = <1>; > > + rxdv-delay = <3>; > > + rxd-delay = <3>; > > This does not make a lot of sense

Re: [RFC PATCH 4/7] ath79: prepare for 1-port TP-Link EAP2x5 devices

2020-07-18 Thread David Bauer
Hi Sander, On 7/17/20 1:37 PM, Sander Vanheule wrote: > TP-Link has developed a number of access points based on the AP152 > reference board. In the EAP-series of 802.11ac access points, this > includes the following devices with one ethernet port: > * EAP225 v1/v2 > * EAP225 v3 > * EAP225-Outdoor

Re: [RFC PATCH 4/7] ath79: prepare for 1-port TP-Link EAP2x5 devices

2020-07-18 Thread Sander Vanheule
On Sat, 2020-07-18 at 13:03 +0200, m...@adrianschmutzler.de wrote: > > I tried 80MHz and 65MHz, but that didn't result in proper reads. > > 50MHz, > > 55MHz, and 60MHz do appear to work on my eap245-v1, so I really > > wouldn't > > risk going above 50MHz. > > If you've taken the 25 MHz somewhere r

RE: [RFC PATCH 4/7] ath79: prepare for 1-port TP-Link EAP2x5 devices

2020-07-18 Thread mail
> I tried 80MHz and 65MHz, but that didn't result in proper reads. 50MHz, > 55MHz, and 60MHz do appear to work on my eap245-v1, so I really wouldn't > risk going above 50MHz. If you've taken the 25 MHz somewhere reasonable, as you stated, I'd also be fine with that. My motivation is mainly to pr

Re: [RFC PATCH 4/7] ath79: prepare for 1-port TP-Link EAP2x5 devices

2020-07-18 Thread Sander Vanheule
On Fri, 2020-07-17 at 14:49 +0200, m...@adrianschmutzler.de wrote: > Hi, Hi Adrian, Thanks for the quick feedback. > > diff --git > > a/target/linux/ath79/dts/qca9563_tplink_eap2x5_1port.dtsi > > b/target/linux/ath79/dts/qca9563_tplink_eap2x5_1port.dtsi > > new file mode 100644 > > index 000

RE: [RFC PATCH 4/7] ath79: prepare for 1-port TP-Link EAP2x5 devices

2020-07-17 Thread mail
j...@phrozen.org; ra...@milecki.pl; yn...@true.cz; > m...@david-bauer.net > Subject: [RFC PATCH 4/7] ath79: prepare for 1-port TP-Link EAP2x5 devices > > TP-Link has developed a number of access points based on the AP152 > reference board. In the EAP-series of 802.11ac access p

[RFC PATCH 4/7] ath79: prepare for 1-port TP-Link EAP2x5 devices

2020-07-17 Thread Sander Vanheule
TP-Link has developed a number of access points based on the AP152 reference board. In the EAP-series of 802.11ac access points, this includes the following devices with one ethernet port: * EAP225 v1/v2 * EAP225 v3 * EAP225-Outdoor v1 * EAP245 v1 Since the only differences between these devices a