<Tusker>
Is there a way in DTS to set a register on the phy gmac ? It seems that there is a register difference between when I ping in uboot vs not pinging in uboot, so wanted to try to set that register value in DT
<Tusker>
https://pastebin.com/3WSpWY3x shows the difference, where 3800 != 7800 ... no clue what the register signifies
<Tusker>
#define AR8035_GBCR 0x09
<Tusker>
whatever GBCR is
<Tusker>
ah, 1000base-t control register ... wonder what 7800 means that 3800 doesn't
<digitalcircuit>
I thought I'd be clever by trying an older SSD (Samsung 850 Pro) connected via a USB SATA case to my NBG6817 router - contrary to expectations, the SSD is actually more power hungry (in bursts) than the HDD, and within an hour of trying to backup, I've corrupted the ext4 filesystem on the SSD :D
* digitalcircuit
shall continue experimenting to get to the root of the L2 1.4 GHz ipq806x cache changes!
<digitalcircuit>
So.. I might try getting a powered USB hub after all with the USB 3.0 HDD, alongside looking at how to tinker with the DTS voltage levels. (The USB HDD is having trouble staying connected to my desktop/laptop directly, possibly from a fiddly microUSB 3.0 connector, so I feel like I either need to move it or replace it eventually anyways...)
<slh>
good luck! (I'm just having fun with an ASRock G10, which also has a number of issues (just arrived a few hours ago, so I don't even have an idea about its stability yet), with the DSA PR and maybe also kernel 5.10 and its NAND, well, need to test v5.4 before claiming that, but there's something fishy, or the second hand device is on the brink of dying)
<wulfy23>
digitalcircuit: have you ran these tests with wifi off?
<wulfy23>
the fact that OEM makes such a prominent 'disable-usb3' tunable is ominous
<digitalcircuit>
wulfy23: Not yet, good point. My desktop is situated somewhere I can't easily run a cable to it, but I can move my laptop around.
<digitalcircuit>
My laptop has generally connected to a second access point (ASUS RT-AC68U) that's connected to the NBG6817 via Ethernet, so it at least doesn't seem to be direct. But I'll still keep in mind trying the SFTP-to-USB drive test with disabling the WiFi radios (presumably freeing up power and/or stopping other devices connecting).
<digitalcircuit>
Trying using the USB 2.0 port instead is another option, too.
Rentong has quit [Ping timeout: 480 seconds]
Tusker has quit [Ping timeout: 480 seconds]
Tusker has joined #openwrt-devel
valku has joined #openwrt-devel
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
nitroshift has joined #openwrt-devel
rmilecki has joined #openwrt-devel
jlsalvador has quit [Read error: Connection reset by peer]
wulfy23 has quit [Remote host closed the connection]
<Tusker>
I'm a bit stuck... how do I figure out what the factory firmware does to activate the gmac0 on the ipq8068 ? The gpio all look good now between working state and non-working state, and the registers only look slightly different in the 1gbs link status (3800 vs 7800). Am a bit lost :) any ideas ?
<Tusker>
there is a bit of oddness around mii-tool output vs ethtool output. mii-tool eth0 shows 10baseT-FD no link, when I turn autoneg off with ethtool... but shows 1000baseT-FD flow-control, link ok if I turn autoneg on
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #openwrt-devel
zx2c4 has joined #openwrt-devel
rejoicetreat has quit [Ping timeout: 480 seconds]
Tapper has quit [Ping timeout: 480 seconds]
Tapper has joined #openwrt-devel
danitool has joined #openwrt-devel
<Tusker>
looking at the factory firmware, the only thing it does weird is set the PLL RATE manually in the /etc/rc.d/network script --- echo 733000000 > /proc/sys/dev/nss/clock/current_freq --- which seems to relate to NSS_PLL_RATE(733000000, 58, 16, 25, 0x014b5625), but that might only be related to NSS, not without NSS...
<Tusker>
anyway, time to shutdown the PC for the weekend :) any ideas would be appreciated, and I'll check the irc logs :) have a good weekend everyone
Tusker has quit [Quit: Time wasted on IRC: 12 hours 44 minutes 58 seconds]
goliath has quit [Quit: SIGSEGV]
Rentong has joined #openwrt-devel
nitroshift has quit [Quit: Gone that way --->]
Tapper has quit [Ping timeout: 480 seconds]
Acinonyx_ has joined #openwrt-devel
jlsalvador has quit [Read error: No route to host]
Acinonyx has quit [Ping timeout: 480 seconds]
jlsalvador has joined #openwrt-devel
goliath has joined #openwrt-devel
jlsalvador2 has joined #openwrt-devel
jlsalvador has quit [Read error: Connection reset by peer]
jlsalvador2 is now known as jlsalvador
Rentong has quit [Ping timeout: 480 seconds]
jlsalvador has quit [Quit: jlsalvador]
Acinonyx_ is now known as Acinonyx
aleksander has quit [Quit: Leaving]
jlsalvador has joined #openwrt-devel
ttocsr has joined #openwrt-devel
minimal has joined #openwrt-devel
<ttocsr>
blocktrron I'm having issues with your recent commit to ethtool
ttocsr has quit [Remote host closed the connection]
<stintel>
sooo ... ARM-based QorIQ devices are already supported in the Layerscape target, the mpc85xx is not really appropriate for the ppc64-based QorIQ devices, so what about a new target named qoriq
<stintel>
I think I will go with that, and send out a first RFC this weekend
Luke-Jr has joined #openwrt-devel
Luke-Jr has quit [Ping timeout: 480 seconds]
Luke-Jr has joined #openwrt-devel
silver has quit [Ping timeout: 480 seconds]
Luke-Jr has quit [Ping timeout: 480 seconds]
Borromini has quit [Quit: Lost terminal]
Luke-Jr has joined #openwrt-devel
Luke-Jr has quit [Ping timeout: 480 seconds]
<agb[m]>
+1 for a qoriq target
<stintel>
agb[m]: alright :) shall I CC you when sending my series ?
minimal has quit []
Tapper has quit [Ping timeout: 480 seconds]
rmilecki has quit [Ping timeout: 480 seconds]
Luke-Jr has joined #openwrt-devel
Tapper has joined #openwrt-devel
Luke-Jr has quit [Ping timeout: 480 seconds]
<blocktrron_>
fda: context?
Acinonyx_ has joined #openwrt-devel
Acinonyx has quit [Ping timeout: 480 seconds]
goliath has quit [Quit: SIGSEGV]
Luke-Jr has joined #openwrt-devel
Luke-Jr has quit [Ping timeout: 480 seconds]
Luke-Jr has joined #openwrt-devel
<fda>
blocktrron_: its serial console output 2 seconds after kernel start