Re: Support for Google Onhub devices
On 12/01/22 18:52, Brian Norris wrote: For the OnHub, you could leverage the same partition formatting (OnHub is also running a similar Chrome OS bootloader), but you'd have to bring up a different SoC (OnHub uses ipq8064, while Google WiFi is ipq4019). OnHub also doesn't have as easy of serial-console access for hacking. And I don't see documentation for Developer Mode on OnHub, although I know it's possible. There is some OnHub "developer mode" and rooting documentation/tools here, at least for the TP-Link OnHub model https://www.exploitee.rs/index.php/Rooting_The_Google_OnHub -Alberto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Custom thread names not working in htop anymore
On 11.01.22 12:55, Hannu Nyman wrote: Koen Vandeputte wrote at Tue Jan 11 02:03:33 PST 2022: > I noticed that custom thread names don't seem to work anymore these days. > Htop got bumped recently but the issue still isn't fixed. > > This feature was very useful to check which thread consumes a lot of cpu > during debugging applications. > > I think this got broken with the bump to a newer musl version as this is > the only delta I haven't tested yet. > > Someone any idea? Might be related to this upstream issue? https://github.com/htop-dev/htop/issues/915 got it. https://github.com/htop-dev/htop/issues/877 The workaround works too. Koen ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
