aboutsummaryrefslogtreecommitdiffstats
path: root/package/qos-scripts/files/usr/bin/qos-stat
diff options
context:
space:
mode:
authorRobert Marko <robimarko@gmail.com>2024-02-17 17:39:22 +0100
committerRobert Marko <robimarko@gmail.com>2024-02-17 17:39:22 +0100
commit70498cb3865e3ada4f1b47c55ead266c40fd4c3e (patch)
tree71078dcc12c1d7ab132690ddd59e2c5d358f4ec9 /package/qos-scripts/files/usr/bin/qos-stat
parentb38a1d6c65ddb469981284d5215cb2ec05cbb86f (diff)
downloadupstream-70498cb3865e3ada4f1b47c55ead266c40fd4c3e.tar.gz
upstream-70498cb3865e3ada4f1b47c55ead266c40fd4c3e.tar.bz2
upstream-70498cb3865e3ada4f1b47c55ead266c40fd4c3e.zip
qualcommax: ipq807x: correct PHY mode for AQR
Interfaces that have AQR-s attached to them are using USXGMII and not just the default SGMII. This was fine until SSDK added some sanity checking and now on Qnap 301W it would fail with: [ 24.740197] nss-dp 3a001800.dp5 10g-1 (uninitialized): failed to connect to phy device [ 24.740264] nss-dp: probe of 3a001800.dp5 failed with error -14 Since this is not Qnap 301W specific lets fix it subtarget wide by declaring the correct PHY mode for 10G AQR-s. Signed-off-by: Robert Marko <robimarko@gmail.com>
Diffstat (limited to 'package/qos-scripts/files/usr/bin/qos-stat')
0 files changed, 0 insertions, 0 deletions