dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Client Quit]
wavirc22 has quit [Ping timeout: 265 seconds]
dongcarl has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
lovesegfault has joined #nixos-aarch64
dongcarl has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Client Quit]
lovesegfault has quit [Quit: WeeChat 2.7]
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
dongcarl has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
zupo has joined #nixos-aarch64
dongcarl has joined #nixos-aarch64
dongcarl has quit [Client Quit]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Client Quit]
orivej has quit [Ping timeout: 272 seconds]
misuzu has quit [Remote host closed the connection]
misuzu has joined #nixos-aarch64
chiefgoat has quit [Read error: Connection reset by peer]
chiefgoat has joined #nixos-aarch64
chiefgoat has quit [Client Quit]
chiefgoat has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 240 seconds]
Acou_Bass has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 258 seconds]
Acou_Bass has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
zupo has joined #nixos-aarch64
pbb has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
pbb has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Client Quit]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
dongcarl has joined #nixos-aarch64
zupo has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Client Quit]
dongcarl has joined #nixos-aarch64
t184256 has left #nixos-aarch64 [#nixos-aarch64]
t184256 has joined #nixos-aarch64
dongcarl has quit [Quit: The Lounge - https://thelounge.chat]
dongcarl has joined #nixos-aarch64
dongcarl has quit [Client Quit]
dongcarl has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Remote host closed the connection]
ryantrinkle has joined #nixos-aarch64
<bennofs> how do I change something in a device tree? Do I need to rebuild the kernel for that?
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
<bennofs> just editing the device tree file and running dtc should do it right?
<flokli> bennofs: the dtc is basically loaded in memory before the kernel is loaded
<flokli> you can also inline the dtc into the kernel image, but most people don't do that
<bennofs> yeah, so if I replace the compiled device tree in /boot/whatever it should just take the new one
<flokli> if you're using uboot, it's the "fdt" option
<bennofs> still need to figure out how to run the compiler to compile a modified device tree though
<samueldr> though if it's booting through the "extlinux" menu, it'll be overwritten even if you change it via u-boot commands
<samueldr> (I don't have an answer to the actual question though)
<bennofs> where does extlinux take the devtree from?
<samueldr> it's u-boot that uses the extlinux file format, thus the quotes and general confusion :)
<samueldr> it's using uh... let's call them "heuristics" to know
<samueldr> in allwinner land, it's hardcoded in the u-boot bin
<samueldr> raspberry pis detect the hardware
<samueldr> those names are used to find the right .dtb file in the relevant folder
<samueldr> >> FDTDIR ../nixos/wvd3ps6vnqba69k8apbi4kkij3dbllfx-linux-5.5.0-rc6-aarch64-unknown-linux-gnu-dtbs
<samueldr> by default, this uses the output of what mainline builds as a collection of dtbs
<samueldr> ah, makefu, not sure if you still care for the AIO-3399C, but since they're likely similar, mainline stuff on https://github.com/samueldr/wip-roc-rk3399-pc
<bennofs> samueldr: i'm running upstream uboot on rock64
<samueldr> I'm running upstream u-boot on pinebook pro, and that ROC-RK3399-PC, is it a contest? :)
<samueldr> because that's only the RK3399 hardware :D
<bennofs> samueldr: ah no, I mentioned this because of the device tree stuff
<samueldr> ah
<bennofs> but I guess that uboot should then load the dtb from the dtbs folder?
<samueldr> I figure it would be like for Allwinner, that rockchip u-boot builds have the name hardcoded at build time
<samueldr> it should
<samueldr> ooh, right, you're the one that just asked the question, silly me :)
<gchristensen> samueldr: btw, if I launched a new aarch64 machine, do you have the time to try?
<gchristensen> (I don't)
<samueldr> gchristensen: sure, I can at least attest that it runs
<gchristensen> ok
<samueldr> not sure I'll have to time to make it production worthy, but that would at least answer the question and making it production worthy can be done in other ways
<gchristensen> cool
<gchristensen> aarch64> instance is in provisioning, 50% done
ToxicFrog` is now known as ToxicFrog
<gchristensen> 20 minutes ... not terrible
<makefu> samueldr: i saw your wiki entry and almost wanted to add the note that the aio-3399c is very similar to that board. i am definitly still interested, board is laying in a box just waiting to be set up
<samueldr> I'm glad to be finally able to get it up and running
<samueldr> even with the caveat that type-c is "broken" (for now)
<bennofs> does anyone here have experience with eMMC on rock64? I have to check, but it seems that is unstable on 200 MHz? At least that's one of the differences between upstream and ayufan, and it runs unstable on ayufan for me. Did anyone else have that issue?
<samueldr> multiple unrelated platforms are having eMMC problems with mainline linux in what sleuthing I could do
<samueldr> (and some related)
<samueldr> and I don't know of an actual thread or bug report upstream
<bennofs> this is actually reverse: it works on mainline
<samueldr> at hs400 speeds?
<bennofs> but is broken on ayufan's downstream. but on mainline usb3 doesn't work
<bennofs> don't think it is hs400 speeds, feels quite slow
<samueldr> on asus-dumo, a chrome-based tablet, I had to force hs200, as hs400 is never coming up, and at hs200 it sometimes doesn't come up either
<samueldr> "unrelated" platforms bug report @ubuntu here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407
<bennofs> thanks for the references. for the logs, the errors that I see look like this: https://forum.pine64.org/showthread.php?tid=5258
<bennofs> samueldr: DTS for rock64 only has mmc-hs200-1_8v; and no mention hs400. So I assume it only runs on hs200 anyway?
<samueldr> with the knowledge I have, that's what I would assume
<bennofs> i don't really know a thing about emmc, guess I need to take a look at some spec sheet tomorrow
<bennofs[m]> Ah, my card only supports at most hs200 anyway
<samueldr> I *think* that there's also multiple compounding issues
<samueldr> but have no way to verify
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has quit [Ping timeout: 268 seconds]
pbb has quit [Ping timeout: 252 seconds]
<gchristensen> samueldr: how's it looking?
<gchristensen> (just curious, no rush/pressure)
pbb has joined #nixos-aarch64
<samueldr> still building!
<samueldr> the moment something happens I'll say
<samueldr> it *is* cross-compiling the whole system
<gchristensen> nice
pbb has quit [Ping timeout: 240 seconds]
<samueldr> it's still going!