<thefloweringash>
eep, #57682 broke ubootRock64 because there's a hidden dtc-1.4.5 in all-packages.nix that only overrides src, so the required patch got lost.
<samueldr>
thefloweringash: librecomputer will soon release patches for another rk3399 board, which from my what I can tell, makes me think any LPDDR4 RK3399 boards might work with mainline u-boot after their inclusion
<samueldr>
they mostly finally got their firefly contacts to make rockchip do the work they were supposed to do to make it all fit, or something along the lines
<thefloweringash>
So that'll fix ubootRockPro64, but the rock64 is lpddr3 rk3328
* samueldr
can't read
<samueldr>
yeah, though still useful for the pro* :)
<lopsided98_>
I have a PR that fixes the build with dtc 1.5.0
<{^_^}>
#59804 (by lopsided98, 1 week ago, open): ubootRock64, ubootRockPro64: make compatible with latest dtc
<thefloweringash>
I'm sure I searched, but I didn't find that. Thanks.
<thefloweringash>
I'll test it on my rock64 and comment
<samueldr>
thefloweringash: if it works, and looks fine to you, I'll merge
<samueldr>
lopsided98_: was this derived from backporting upstream changes?
<lopsided98_>
No, there were large changes to the dtc headers between 2017.09 and when compatibility with the latest dtc was added
<lopsided98_>
so I couldn't really find a patch to backport
<samueldr>
btw, nothing wrong, just wondering how this could be done again if there is a need to
<lopsided98_>
I just bisected dtc and found that the include guards were changed, which was causing conflicting includes of the external dtc headers and the ones built into uboot
<lopsided98_>
I don't really understand why uboot seems to have its own copy of the libfdt headers
<clever>
i prefer #pragma once, and just not having duplicate copies of headers
lopsided98_ is now known as lopsided98
<lopsided98>
Thanks for testing it - I don't have physical access to my Rock64 and RockPro64 right now, so I didn't want to risk it
<samueldr>
AFAIUI u-boot seems to derive from libfdt for some things like efi boot, and the fdt command
<thefloweringash>
my rock64 still boots
<jackdk>
what is the current state of rock64? can you get a nixos going on it using mainline nixpkgs, or is it still using your repo?
<lopsided98>
I probably don't really need most of those patches though
<thefloweringash>
looks like it has a lot of multimedia fixes in there
<thefloweringash>
My rock64 is a headless hydra and dev environment for my laptop, so all I need is network, cpu, usb3. I'm not the best person to ask about the state of various kernel features.
<jackdk>
that is the objective for mine, well, once it's in the same state as I am. how's that worked out for you? I was tossing up whether to put nix on armbian or similar, vs nixos.
<lopsided98>
which fixes the ethernet checksumming issue
<thefloweringash>
It's worked pretty well. Used to take about 3-days to build chromium, but haven't really had any stability problems.
<lopsided98>
Building for my other aarch64 machines is pretty much the only thing my RockPro64 does
<jackdk>
that's encouraging. I won't be building anything that gnarly, though I'll be crossing fingers if it decides to build haskell packages
<thefloweringash>
I like that people have solved all the various little problems with these boards, but I'm a little disappointed how fragemented the knowledge seems to be. How well do changes from ayufan's kernels make it upstream?
<thefloweringash>
when I'm impatient I configure some amazon a1.4xlarge instances as remote builders
<lopsided98>
My biggest annoyance with the RockPro64 is that it tends not to come up after a reboot and won't boot if a serial adapter is connected
<lopsided98>
I spent the first three days after I got it thinking it was DOA because I had the serial port connected
<lopsided98>
and I have to use a remote controlled power strip to reboot it
<sphalerite>
lopsided98: hmm, I have a similar issue with my router.
<sphalerite>
I've been meaning to try with my other USB-UART adapter for a while now, still haven't got around to it though
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
jackdk has quit [Ping timeout: 245 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
FRidh has joined #nixos-aarch64
makefu has quit [Ping timeout: 252 seconds]
ryantrinkle has quit [Ping timeout: 245 seconds]
orivej has quit [Ping timeout: 276 seconds]
ryantrinkle has joined #nixos-aarch64
orivej has joined #nixos-aarch64
jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 258 seconds]
lemsip has quit [Quit: cya]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 245 seconds]
FRidh has quit [Quit: Konversation terminated!]
ryantrinkle has joined #nixos-aarch64
orivej has quit [Ping timeout: 245 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
makefu has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mthst has quit [Quit: the bouncer died]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]