The Aerohive HiveAP 121 has the wrong PLL value set for Gigabit speeds,
leading to packet-loss. 10M and 100M work fine.
This commit sets the Gigabit Ethernet PLL value to the correct value,
fixing packet loss.
Confirmed with iperf and floodping.
Signed-off-by: David Bauer
---
target/linux/ar71
Can we not have a way of including unstable stuff in a way the consumers
know it’s un stable ?
Like a 19.07 canary
On Tue, 30 Jul 2019 at 20:22, Andreas Ziegler wrote:
>
> Dmitry Tunin schrieb am 30.07.19 um 14:29:
> > Are you taking in account that many devices added during the last year
> > a
Dmitry Tunin schrieb am 30.07.19 um 14:29:
> Are you taking in account that many devices added during the last year
> as ath79 won't be supported by a stable release.
> Master is no good now for normal use. That will mean that for the next
> year or so many users will require custom 19.07 builds.
> Can you explain why not? I'm not aware about any critical issues on ath79. How
> are we going to prepare ath79 in possibly best shape for the next release, if
> we now provide ath79 images in 19.07? Users would simply stick to stable
> images and snapshots would get less testing.
There are some i
Dmitry Tunin [2019-07-30 15:29:27]:
> > e) if you want to use ath79, you should use snapshot images (and expect
> > support) or
> >build 19.07 for ath79 yourself (but don't expect much support)
>
> Are you taking in account that many devices added during the last year
> as ath79 won't be su
Hi,
On 29-07-19, David Hutchison wrote:
> https://forum.openwrt.org/t/support-for-mikrotik-rb3011uias-rm/4064/412
>
> I've been working on the hAP AC2 port, and haven't tested with SMP yet.
>
> I posted the DTS files I came up with on the RB3011 thread as we were all
> working on Mikrotik IPQ40X
> e) if you want to use ath79, you should use snapshot images (and expect
> support) or
>build 19.07 for ath79 yourself (but don't expect much support)
Are you taking in account that many devices added during the last year
as ath79 won't be supported by a stable release.
Master is no good now
Hi,
I had a look at u7628-01-128m-16m .
You are right that this case is similar to your example, but I also think that
it should be renamed, too.
There are other examples in mt7628an using only flash size for name
distinction, e.g.
mt7628an_widora_neo-16m
mt7628an_widora_neo-32m
Dmitry Tunin [2019-07-29 19:28:11]:
Hi,
> What is the point of excluding ath79?
a) we've simply forget to make ath79 source-only right after the 19.07 branch,
sorry for the confusion or false expectations it might have introduced
b) it was decided some time ago, that 19.07 is last release w