<mDuff>
What does it take to get g_ether working on a Pi 4b on NixOS? I see CONFIG_USB_DWC2_DUAL_ROLE=y, but loading g_ether, it warns "udc-core: couldn't find an available UDC"
<samueldr>
I guess the question is "what does it take on other distros"
<samueldr>
it should be the same afterward
<mDuff>
It looks like Raspian ships a device tree overlay that does some necessary initialization-time setup.
<mDuff>
...I *suspect* that getting the appropriate bits into `config.hardware.deviceTree` might be appropriate, but ofc, need to figure out what aforementioned "appropriate bits" are first.
<samueldr>
gchristensen (not time sensitive) as the qemu settings have not been fiddled with, and it works on my pinebook pro, and on the community builder, I guess it's likely to work on that c2.large, since the same qemu settings worked for thefl*weringash earlier
<gchristensen>
great. I'm just getting to another active part of making dinner, let's create a c2.large.arm in a couple hours?
<samueldr>
we could yeah
<gchristensen>
coor
<gchristensen>
cool. I took a nap from like 4:??-6, and am probably up for it then :)
<mDuff>
...hmm, looks like the existing raspberrypi-firmware-1.20190925 (pkgs.raspberrypifw) contains a dwc2.dtbo that might be what's missing...
<mDuff>
...yup, that did the trick.
<clever>
mDuff: by default, the rpi4 usb-c is in device mode
<clever>
there are dtbo flags to force it into host mode, but you probably dont want that
<mDuff>
*nod* -- I'm trying to convince my Pi to play ethernet-dongle. After telling the bootloader to install the dwc2 overlay (and loading g_ether), it's doing that properly.
<mDuff>
...so the next step is to make the sd_image build set it up that way out-of-the-box. :)
Irenes[m] has quit [Ping timeout: 252 seconds]
lovesegfault has joined #nixos-aarch64
h0m1 has quit [Quit: WeeChat 2.7]
h0m1 has joined #nixos-aarch64
<samueldr>
pushed a change to use s2idle for suspend in the pinebook pro config, that's opinionated, but a much better thing to do rather than accidentally activating suspend and needing to force shutdown
<clever>
samueldr: that reminds me, ive got crazy ideas to make suspend to ram work on an rpi, lol
<gchristensen>
hi samueldr
<samueldr>
hi gchristensen
<samueldr>
once suspend is fixed on the kernel (or u-boot, or trustzone?) that'll go away from that generic config
lovesegfault has quit [Ping timeout: 272 seconds]
<thefloweringash>
hi everyone
<samueldr>
'morning!
<samueldr>
(assuming)
mDuff has quit [Ping timeout: 268 seconds]
<gchristensen>
mksquashfs :(
<samueldr>
ah, taking a while to make your system image to deploy&
<samueldr>
?*
<gchristensen>
yea
ryantrinkle has joined #nixos-aarch64
<gchristensen>
"but it parallelizes well" evidently not b/c it still takes ages to finish a 500mb squash with 96 cores
<gchristensen>
put a `mksquashfs` over the faceand it is right on the money
* t184256
just understood that he can run QEMU VMs inside Nix-on-Droid
<samueldr>
can you?
<samueldr>
is /dev/kvm there?
<samueldr>
and accessible
<t184256>
No, but tcg works
<thefloweringash>
(reading scrollback) cross compiling that vm was on my todo list. I bootstrapped with an old sdimage and never got around to switching. The module I use does technically support cross buliding with nixpkgs.crossSystem
<samueldr>
thefloweringash: you saw the gist?
<samueldr>
oh, and a complication, I initially tried (part for fun) to cross-compile the qemu "harness" from x86_64-linux to aarch64-linux, and the system from x86_64-linux to armv7-llinux
<samueldr>
qemu won't cross-compile due to python3 deps not cross-compiling right now
<samueldr>
when I reduced the jenga^W complexity stack, it went easier :)
<thefloweringash>
the build-vm-script is ok for testing, but the overlayfs of 9p + tmpfs is probably too slow, and overlayfs breaks the go tests for large files. for productionising I think I'd recommend some simple filesystem like ext4
<samueldr>
I see
<thefloweringash>
oh, no, didn't see the gist
<samueldr>
ah, basically what was needed for it to cross-compile, got rid of `system` and used my usual cross-compilation fixes
<thefloweringash>
it passes a /nix/store as a squash, and on boot copies it to /
<samueldr>
<3 thefloweringash
<{^_^}>
thefloweringash's karma got increased to 6
<samueldr>
I do wonder if it is worth it to keep the aarch64 cross-compilation of the armv7l system part of the "critical" chain with the armv7l builders
<samueldr>
maybe with an hydra build
<samueldr>
I don't know how else they can be managed by the aarch64 system without relying on *another* armv7l builder
<samueldr>
maybe I'm missing something obvious?
h0m1 has quit [Ping timeout: 260 seconds]
<gchristensen>
seems like a good idea
h0m1 has joined #nixos-aarch64
lovesegfault has joined #nixos-aarch64
<lovesegfault>
gchristensen: Any idea why ghc doesn't build in parallel on the aarch64 box?
<clever>
/home/clever/apps/nixpkgs-hasura/nixos/modules/installer/cd-dvd/sd-image.nix: Volume ID for the /boot/firmware partition on the SD card. This value
<clever>
/home/clever/apps/nixpkgs-hasura/nixos/modules/installer/cd-dvd/sd-image.nix: Size of the /boot/firmware partition, in megabytes.
<clever>
basically, uboot and the rpi firmware goes into the fat32, at /boot/firmware
<clever>
extlinux.conf and the linux kernels, go into /boot, a directory on the ext3/4
<lovesegfault>
Aha!
<lovesegfault>
:)
<samueldr>
clever++
<{^_^}>
clever's karma got increased to 306
<lovesegfault>
clever++
<{^_^}>
clever's karma got increased to 307
<lovesegfault>
Thanks all :D
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]