Re: [OpenWrt-Devel] [PATCH] ramips: Fix WiFi after 5f7396ebef09b224edf08b0bda113613a42f0928

2018-05-31 Thread Rosen Penev
On Thu, May 31, 2018 at 10:02 PM, Felix Fietkau wrote: > On 2018-05-29 20:03, Rosen Penev wrote: >> That commit exposed a bug in the DTS files used by mt7621 where the wrong >> reg value for pcie1 (and potentially pcie2) was being used. This was >> causing WiFi failures for interfaces in pcie1.

Re: [OpenWrt-Devel] [PATCH] ramips: Fix WiFi after 5f7396ebef09b224edf08b0bda113613a42f0928

2018-05-31 Thread Felix Fietkau
On 2018-05-29 20:03, Rosen Penev wrote: > That commit exposed a bug in the DTS files used by mt7621 where the wrong > reg value for pcie1 (and potentially pcie2) was being used. This was > causing WiFi failures for interfaces in pcie1. > > eg. 2.4GHz working but not 5GHz. > > As all of these dts

Re: [OpenWrt-Devel] [PATCH] ramips: Fix WiFi after 5f7396ebef09b224edf08b0bda113613a42f0928

2018-05-29 Thread Karl Palsson
Rosen Penev wrote: > That commit exposed a bug in the DTS files used by mt7621 where > the wrong reg value for pcie1 (and potentially pcie2) was being > used. This was causing WiFi failures for interfaces in pcie1. > > eg. 2.4GHz working but not 5GHz. > > As all of these dts entries are

[OpenWrt-Devel] [PATCH] ramips: Fix WiFi after 5f7396ebef09b224edf08b0bda113613a42f0928

2018-05-29 Thread Rosen Penev
That commit exposed a bug in the DTS files used by mt7621 where the wrong reg value for pcie1 (and potentially pcie2) was being used. This was causing WiFi failures for interfaces in pcie1. eg. 2.4GHz working but not 5GHz. As all of these dts entries are already specified in mt7621.dtsi, remove