Linux version 5.4.64 (nixbld@nixwrt.builder) (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?

#nixwrt #mips #nixpkgs #WhoSaysSentencesCantStartWithConjunctions

self reply
self reply

Hypothesis: something has changed between kernel 4.x and 5.x in the way that GPIOs are described, meaning that the uart driver doesn't know which wires to twiddle on

#issuecomment-594270661">https://github.com/openwrt/openwrt/pull/2798#issuecomment-594270661

Anyway. the DTS definitely looks different

Although, assuming OpenWrt works with 5.4 on this hardware (I have compiled but not actually tried running it yet) it's much more plausible that I can fix this easily by finding a patch somewhere I missed applying, than that I need to do major edits to device tree files

self reply

I may have hit on a really good (and much simpler) reason that I can't build a gl-mt300n image that runs on this hardware. This hardware is not a gl-mt300n, it's a gl-mt300a.

There's probably some kind of life lesson here about remote development. Or about validating assumptions, or maybe just about not being an idiot