<samueldr>
the `dt_size` variants are throwing a wrench
disasm has quit [Ping timeout: 240 seconds]
disasm has joined #nixos-aarch64
<DigitalKiwi>
did anyone buy a helios64?
<DigitalKiwi>
anyone here*
<DigitalKiwi>
obviously people did as they're sold o ut
orivej has joined #nixos-aarch64
cole-h has quit [Ping timeout: 260 seconds]
<sphalerite>
DigitalKiwi: I ordered one, it's not shipped yet.
<sphalerite>
DigitalKiwi: angerman's has arrived though.
cornu has quit [Ping timeout: 244 seconds]
cornu has joined #nixos-aarch64
<DigitalKiwi>
do they have nixos on it :D
alp has joined #nixos-aarch64
<angerman>
No idea. I’ve only managed to mostly assemble it. And have been thrown off as it’s not level on the floor.
orivej has quit [Ping timeout: 258 seconds]
alp has quit [Ping timeout: 244 seconds]
<DigitalKiwi>
does it seem good
<angerman>
It’s not level.
elvishjerricco has quit [Ping timeout: 272 seconds]
elvishjerricco has joined #nixos-aarch64
bqy has quit [Quit: Idle for 30+ days]
alp has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-aarch64
nschoe has joined #nixos-aarch64
<grw1>
hi, i made this pr https://github.com/NixOS/nixpkgs/pull/99255 and someone request "ofborg doesn't evaluate kodi on arm64 but since that's what you are specifically targeting with this PR, is there any chance you could massage that into happening?"
<{^_^}>
#99255 (by georgewhewell, 1 day ago, open): kodi: remove jre override, use jre_headless
<grw1>
im not really sure whats being requested of me, can anyone help? :)
ib07 has joined #nixos-aarch64
orivej has quit [Ping timeout: 265 seconds]
nschoe has quit [Remote host closed the connection]
nschoe has joined #nixos-aarch64
<betaboon>
grw1: I'm not sure either. maybe you could ask grahamc in #nixos ?
orivej has joined #nixos-aarch64
alp has joined #nixos-aarch64
<betaboon>
gitMinimal doesnt cross-compile yet ?
jj__ has joined #nixos-aarch64
jasom has quit [Ping timeout: 260 seconds]
njha has quit [Ping timeout: 244 seconds]
alp has quit [Ping timeout: 272 seconds]
jjsullivan1 has quit [Ping timeout: 260 seconds]
jasom has joined #nixos-aarch64
njha has joined #nixos-aarch64
Darkmatter66 has joined #nixos-aarch64
Darkmatter66_ has quit [Ping timeout: 240 seconds]
<srk>
betaboon: yeah, I know about that. linuxPackages_rpi4?
<betaboon>
srk: yes linuxPackages_rpi4, buit build against 5.4.51 from raspberrypi/linux.
<betaboon>
srk:i tired applying your fixes from PR 99378, but either i did it wrong or it doesnt fix this
<betaboon>
*trie
<betaboon>
*tried (argh sausage-fingers)
<srk>
no, that just fixes cross compilation for _rpi kernels but there are still issues with binary overlays from device-tree_rpi.overlays
<srk>
5.4.51 from samueld|rs pi4 PR?
<betaboon>
srk: didnt take it from the pr, but i guess it is quite similar to what i do. building against tag "1.20200902", disabling PCIE_ALTERA (because of upstream fuckup)
<srk>
betaboon: can you try grabbing dts from the kernel source instead? you switch dtboFile to dtsFile with "${pkgs.linux_rpi4.src}/arch/arm/boot/dts/overlays/vc4-kms-v3d-overlay.dts" I thin
<srk>
k
<betaboon>
srk: will try
<srk>
oh no, that contains #include <dt-bindings/clock/bcm2835.h>
<betaboon>
srk: fails with syntax-error "FATAL ERROR: Unable to parse input tree"
<srk>
yeah, because of that #include ^
<srk>
I'm trying to figure out how compatible these binary rpi overlays are and it's pretty weird
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<betaboon>
srk: what is the problem with those #include statements ?
cole-h has joined #nixos-aarch64
<srk>
betaboon: needs to run through preprocessor, it's done as part of the rpi kernel build so maybe we could grab .dtbo from its out instead
<sphalerite>
betaboon: hmm, cross-building sway fails on dconf, not pyyaml, for me
<betaboon>
sphalerite: yeah later on i ran into that aswell
<betaboon>
sphalerite: i think i was able to get dconf compiled by adding mesonFlags `-Dvapi=false` and `-Dgtk_doc=false` and removing the "devdoc" output. but then it failed on a package called `enca`
<betaboon>
srk:i just tried with `dtboFile = "${config.hardware.deviceTree.kernelPackage}/dtbs/overlays/vc4-fkms-v3d.dtbo"` running into FDT_ERR_NOTFOUND agains
<srk>
betaboon: ok, will look closely at that one. I've tried similar today (hifiberry dac) and it has similar issues, even though it comes from the same kernel package
rajivr has quit [Quit: Connection closed for inactivity]
<colemickens>
I've pushed up my latest changes for blueline. I can't get the android or mainline kernels to boot, seems like DTB overlay issues.
<colemickens>
I tried making it match the razer device that sam/ueldr is working on, but my kernel options are slightly different and I don't see anything obviously wrong, especially in the Android config.aarch64.
<samueldr>
colemickens: did you see the other day my suggestion
<samueldr>
CONFIG_BUILD_ARM64_DT_OVERLAY
<colemickens>
`CONFIG_BUILD_ARM64_DT_OVERLAY=y`
<samueldr>
hm
<samueldr>
which kernel source tree are you using? I forgot, was it android-linux-stable?
<colemickens>
I added these too: enableRemoveWerror=true, isImageGzDtb=true.
<colemickens>
Yes. Android-linux-stable.
<samueldr>
great to see a rebase on the new builder
<colemickens>
is there another I should try?
<samueldr>
I don't think so, other than the one from google outright
<colemickens>
hm ok
<samueldr>
though ALS should be close enough that it doesn't matter
<colemickens>
I do have this too, though:
<colemickens>
`# CONFIG_BUILD_ARM64_APPLY_DTBO is not set`
<colemickens>
It kind of feels like the boot process is still trying to "apply dtb overlay", which I'm not sure if it should be.
<colemickens>
(I pushed the change, and the updated boot log)
<colemickens>
"DeviceTreeOverlay failed: Invalid Parameter Failed to apply dtb overlay"
<colemickens>
I'm going to look at your razer device and the makefiles for more hints.
zupo has joined #nixos-aarch64
<colemickens>
hm interesting, fastboot boot takes a --dtb option
<samueldr>
note that on razer-cheryl2 `fastboot boot` does not exist, I always flashed
<samueldr>
I guess it could change how things work
<colemickens>
I decided to `fastboot flash boot ...` and then `fastboot set_active a` and tried to boot, similar results so far.
<colemickens>
Except this time where it didn't reboot into fastboot -_-
cole-h has quit [Ping timeout: 240 seconds]
<colemickens>
ooh, different errors after erasing dtbo_a
<samueldr>
it could be that for the pixel 3 things are different enough compared to cheryl2
<samueldr>
though I never had to erase dtbo
<samueldr>
it's still the stock dtbo from whatever version of the OS was installed
<colemickens>
I got a EFI error, so I enabled CONFIG_EFI and I'm going to try again.
<colemickens>
I figured maybe if it couldn't load the DTB from the partition, it would try to load from my kernel instead (and I think it might've...?).
<samueldr>
and what you're going through is what I often go through when porting :)
<samueldr>
trying to figure out what is going one from a mostly blackened box
<samueldr>
though yours at least has serial out
<colemickens>
I'm in the "blindly stumbling, looking for guidance, saying everything I'm trying outloud mode" so that's good to hear.
<colemickens>
does yours not? that would be a humbling experience.
<samueldr>
cheryl2 doesn't
<samueldr>
well, doesn't have a documented one
<samueldr>
and for those that are documented, I have only used those that didn't require a hardware modification
<samueldr>
so limited to Pixel devices on android-based devices :)
<samueldr>
though I still have to try and make the MTK debug cable