[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <trinity-b1f48e51-af73-466d-9ecf-d560a7d7c1ee-1566488653737@3c-app-gmx-bap07>
Date: Thu, 22 Aug 2019 17:44:13 +0200
From: "Frank Wunderlich" <frank-w@...lic-files.de>
To: "René van Dorst" <opensource@...rst.com>
Cc: "Sean Wang" <sean.wang@...iatek.com>,
"Andrew Lunn" <andrew@...n.ch>,
"Vivien Didelot" <vivien.didelot@...il.com>,
"Florian Fainelli" <f.fainelli@...il.com>,
"David S . Miller" <davem@...emloft.net>,
"Matthias Brugger" <matthias.bgg@...il.com>,
netdev@...r.kernel.org, linux-mips@...r.kernel.org,
"René van Dorst" <opensource@...rst.com>,
linux-mediatek@...ts.infradead.org,
"John Crispin" <john@...ozen.org>,
linux-arm-kernel@...ts.infradead.org
Subject: Aw: [PATCH net-next v2 0/3] net: dsa: mt7530: Convert to PHYLINK
and add support for port 5
Hi,
tested on BPI-R2 (mt7623) with 2 Problems (already reported to Rene, just to inform everyone)...maybe anybody has an idea
- linux-next (i know it's not part of the series, but a pitfall on testing other devices) seems to break power-regulator somewhere here:
priv->core_pwr = devm_regulator_get(&mdiodev->dev, "core"); returns 517
#define EPROBE_DEFER517/* Driver requests probe retry */
https://elixir.bootlin.com/linux/latest/source/drivers/regulator/core.c#L1726
without linux-next switch came up including dsa-ports
- RX-traffic (run iperf3 -c x.x.x.x -R) is only 780 Mbits/sec (TX=940 Mbits/sec), same measure with 5.3-rc4 gives 940 MBit/s with same devices,
maybe caused by changes for mt76x8?
regards Frank
Powered by blists - more mailing lists