<exarkun22>
What does "linux_rpi" correspond to in the Python universe?
<exarkun22>
I found python-gpiozero which has an open PR with aarch64 support, I'm currently trying that to see if it works
<exarkun22>
doesn't seem to :(
<exarkun22>
"linux_rpi" is a Raspberry Pi-enabled kernel configuration?
<exarkun22>
noooo....
<samueldr>
linux_rpi is the raspberry pi foundation's fork of the kernel, built for NixOS
<exarkun22>
I don't really know what that means. I have some kind of Linux running on AArch64 already. Maybe ... this?
<samueldr>
NixOS's aarch64 images default to mainline kernel, the upstream Linux kernel
<exarkun22>
Huh, I see
<exarkun22>
probably the wrong time of day/night to start screwing with kernels for me
<exarkun22>
guess I'll take a look in that direction tomorrow though
<exarkun22>
How might it help me? I saw some commentary suggesting there was no interest in "fixing" the /proc/cpuinfo incompatibility.
<samueldr>
not sure what comment you're referring to
<samueldr>
but what might happen is that gpio things (is that what you're doing?) are expecting the special sauce that the raspbery pi foundation could have added to the kernel
<samueldr>
while the mainline kernel either doesn't have it, or has a different sauce
<samueldr>
(I don't have actual experience with that, only going from things I read)
<{^_^}>
raspberrypi/linux#2110 (by thomasklingbeil, 1 year ago, closed): /proc/cpuinfo missing Hardware/Revision/Serial on arm64
<samueldr>
hm, that may not be "fixed" by that, only way to know would be to test :/
<exarkun22>
that seems to be raspberrypi linux maintainers saying they won't put "Hardware" and "Revision" into /proc/cpuinfo on AArch64
<exarkun22>
yea, okay
<exarkun22>
it seems like the way forward is maybe device-tree (first I ever heard of it)
<samueldr>
AFAIUI, the raspberry pi foundation are kinda disregarding aarch64 :/
<exarkun22>
nixos basic linux kernel does not have a fully populated device tree but maybe raspberrypi linux does
<samueldr>
that may help yeah
<exarkun22>
that's a little bit crap of them, considering they sell aarch64 capable hardware? isn't it?
<samueldr>
probably because everything is written considering the armv7 raspberry pi (talking out of my ass, no real knowledge of the situation)
<samueldr>
raspberry pi 2*
<samueldr>
AFAIK raspbian still is armv7 even for raspberry pi 3 :(
<exarkun22>
this guy seems to think he has a solution using device-tree - https://github.com/RPi-Distro/python-gpiozero/issues/688 - his code didn't work on my pi. so I guess I'll try it on raspberry pi linux tomorrow and see if that helps.
<{^_^}>
RPi-Distro/python-gpiozero#688 (by Martchus, 1 week ago, open): Support device detection under aarch64
<exarkun22>
(his code assumes there is a /proc/device-tree/system/linux,revision but I don't even have a /proc/device-tree/system)
samrose_ has joined #nixos-aarch64
samrose has quit [Ping timeout: 245 seconds]
orivej has quit [Ping timeout: 244 seconds]
orivej has joined #nixos-aarch64
<exarkun22>
So is that linux_rpi thing at `pkgs.linuxPackages_rpi` or are those two different things?
<exarkun22>
it sounds like there are some issues with proprietary hardware for which there are only 32 bit blobs available. maybe aarch64 on rpi is just premature at this point.
samrose_ is now known as samrose
<tilpner>
samueldr - Your 4.14.72 keeps the display on, I can login without serial!
<samueldr>
other people's 4.14 :)
<samueldr>
I merely did a `git merge`
<tilpner>
So what can you tell me about what you merged?
<tilpner>
I'd like to figure out why this works but 4.20-rc1 doesn't