WIP: I am rearranging the kernel significantly. The plan is split...GitHub
Linux version 5.4.64 (email@example.com) (gcc version 9.3.0 (GCC)) <a href="https://terse.telent.net/tags/1" class="mention hashtag" rel="tag">#<span>1</span></a> Tue Sep 15 13:33:49 UTC 2020
Pausing here for a brief "woohoo!"
It doesn't mount the root fs yet, maybe (it suddenly occurs to me literally as I write this toot) because I forgot to build the phram target. And then the next big task is to build wireless modules from linux-backports. And maybe, y'know, actually commit some stuff to git?
Yay, ethernet cable to the shed!
Now I just have to find an appropriate device to plug in at the end of it (preferably one that #nixwrt supports)
It would be nice if I could make the linux-backports script thing work properly
It has been ~ 6 months since I last tried to build #nixwrt (I got distracted, my tux didn't come back from the cleaner, there was a global pandemic). Whyever did I think that it was sensible to start the build while sshed in from a laptop and without a tmux session?
TFW when you set out to benchmark something you've previously observed is inexplicably slow, and ... it's no slower than the other thing you're comparing it against
#nixwrt wireless performance on this gl-mt300a (MediaTek MT7620A SoC) is about ~ 14Mb/s according to iperf3, which is probably slower than I should expect but is on par with the 2.4GHz network on the gl-ar750 downstairs running the vendor's OpenWRT
As of today, #nixwrt no longer needs a forked nixpkgs repo! https://github.com/telent/nixwrt/commit/c3e0bc3dec168ab895c67973a8d40ed9904c2b83
(In all honesty a small achievement, but a noteworthy one nonetheless)
This means: no more need for a forked nixpkgs! At last, we now build with...GitHub
The LZMA decompression code in u-boot doesn't understand the LZMA compression performed by xz, so to get #nixwrt to generate images that work I have to build the "legacy" lzma (from 2008). Upgrading nixpkgs caused its buiild to fail with "RPATH ... contains a forbidden reference to /build"
so I worked around that by
configureFlags = [ "--enable-static" "--disable-shared"]
now it is building gcc again. Guess I must have changed something else fundamental ...
Kicked off a #nixwrt build (using nixpkgs master) for the first time in forever. Not sure quite what it's doing: seems to be building gcc, so let's hope this is one stage in a bootstrap that will eventually get me something that produces mipsel linux musl executables
There are definitely other things I could say about ath9k and ath10k and wireless regulatory domains in embedded Linux, but this blog post is too long already and it would probably require having more than the handwaviest idea of what I'm talking about. Plus I'm sick of it. Happy Christmas, if that's your bag.
I'm not saying it works, because it doesn't, but my ath10k wireless at least appears now to exist in #nixwrt. This is progress and it makes me happy
carrier phy80211 phys_switch_id carrier_up_count uevent name_assign_type queues gro_flush_timeout address carrier_changes dev_port device ifindex tx_queue_len duplex statistics wireless type power flags dev_id addr_assign_type phys_port_id addr_len carrier_down_count speed link_mode netdev_group phys_port_name broadcast subsystem iflink operstate dormant ifalias proto_down mtu ```
Oh, hey, this is good news. Linux (in OpenWRT) now has device tree support for my home router. Really need to snag another one so that I can port #nixwrt to it without losing the internet.
This repository is a mirror of https://git.openwrt.org/openwrt/openwrt.git...GitHub