<ryantrinkle>
samueldr: hahaha i have finally gotten through enough stuff to understand what you were saying about the device tree thing
<ryantrinkle>
i just had to find a patch to add my specific LCD panel to the dts for my board
<ryantrinkle>
which doesn't even seem semantically correct
<ryantrinkle>
given that the panel isn't part of the board
<samueldr>
ryantrinkle: summing up my feelings
<samueldr>
though, now that you have made it work
<samueldr>
I think you're a prime suspect^W user that could figure out if dtbocfg works
<samueldr>
well, I'm 99% sure it works
<samueldr>
maybe more figuring it out :)
<samueldr>
or confirming?
<samueldr>
I mean, it's documented well enough
<samueldr>
but, I think that it's not that device trees are wrong, but they've been twisted into end-users requiring to manipulate them to assemble stuff
<samueldr>
because a device tree for a final end-user product like a phone makes sense
<samueldr>
even a laptop does imo
<samueldr>
(assuming a small range of compatible LCD screns)
<samueldr>
screens*
<samueldr>
chromeos devices, even x86_64, use device trees somehow in their tooling, which I think (don't quote me) makes up the ACPI tables in the end
orivej has quit [Remote host closed the connection]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
pkral has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
vika_nezrimaya has joined #nixos-aarch64
bennofs has joined #nixos-aarch64
bennofs_ has joined #nixos-aarch64
bennofs has quit [Ping timeout: 260 seconds]
Thra11 has joined #nixos-aarch64
Thra11 has quit [Quit: WeeChat 2.6]
bennofs_ has quit [Remote host closed the connection]
bennofs has joined #nixos-aarch64
Thra11 has joined #nixos-aarch64
bennofs has quit [Ping timeout: 252 seconds]
bennofs has joined #nixos-aarch64
<DigitalKiwi>
what's a good cord/controller thing I can use to get serial output. need it to work for rasperry pi but if it works for arduinos as well even better
<clever>
the ftdi i linked is 3.3v, so its safe to use on a pi, and the jumpers deal with the pinout being different, and make it flexible enough to use on anything
<clever>
you may also want some M/M jumpers for other boards that have sockets rather then headers, or for just holding on pins of a chip
<DigitalKiwi>
i have dupont connectors and a crimping tool :D
<DigitalKiwi>
and jst xh and jst sm...
<clever>
DigitalKiwi: ah nice, so you could rig up a connector that perfect fits the ftdi&pi, with the right wires crossed
<DigitalKiwi>
yup!
<DigitalKiwi>
oh so caveat: there's a project i might be interested in that i think i might want a serial chip that uses an atmega16u2 (not an ftdi)
<DigitalKiwi>
clever: it has multimedia control too
<clever>
DigitalKiwi: main problems i can see with the wifi keyboard after using it, you have to disable the onscreen keybord to use it, and it lacks authentication
<clever>
DigitalKiwi: i have also messed with bluetooth a bit, and my laptop can emulate a bluetooth speaker, so the phone will play out of the laptop speakers
<DigitalKiwi>
heh got the remote keyboard to work from my desktop to my revolution irc on my phone
<DigitalKiwi>
oh cool I got my raspberry pi 3b+ to work finally
<samueldr>
it's "the one" they use in their tutorials and such
<samueldr>
how bad would it be to introduce an impurity in the default mobile nixos image where the stage-1 would put a file in stage-2 when rehydrating the image at first boot?
<samueldr>
this would be used to make universal stage-2 (system) images work better
<samueldr>
I need to investigate the feasability
<samueldr>
hmmm, or not that impure if a nixos-rebuild can happen entirely offline with that file
<clever>
you could also make a stage2 image, that contains the closure of 4 different nixos configs
<clever>
and just select which one you boot, based on which stage1 you use