ryantrinkle has quit [Ping timeout: 245 seconds]
wildtrees has quit [Quit: Leaving]
ryantrinkle has joined #nixos-aarch64
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 245 seconds]
ryantrinkle has quit [Ping timeout: 248 seconds]
zupo has joined #nixos-aarch64
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-aarch64
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has quit [Ping timeout: 272 seconds]
ryantrinkle has joined #nixos-aarch64
contrun[m] has joined #nixos-aarch64
t184256 has left #nixos-aarch64 [#nixos-aarch64]
t184256 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
chiefgoat has quit [Ping timeout: 258 seconds]
chiefgoat has joined #nixos-aarch64
chiefgoat has quit [Quit: ZNC 1.7.4 - https://znc.in]
chiefgoat has joined #nixos-aarch64
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 258 seconds]
ryantrinkle has quit [Ping timeout: 268 seconds]
ryantrinkle has joined #nixos-aarch64
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<sphalerite> samueldr: I might be able to provide some helpful input on #66960 — just not sure if I have the right pi model. Do you know if there's a way to find out which one it is from a booted linux on it?
<{^_^}> https://github.com/NixOS/nixpkgs/issues/66960 (by samueldr, 1 week ago, open): Tracking issue for Raspberry Pi 3B+ and the latest kernel
<sphalerite> well it's definitely a 3A of some sort. Not sure about the + part
<sphalerite> oh there is no non-plus 3A?
zupo has joined #nixos-aarch64
orivej has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<samueldr> I'm not sure
<clever> sphalerite: there is a way to visually identify your model
<samueldr> though yeah, looks like it, only 3A+
<samueldr> it will also say so on the board
<clever> sphalerite: the image i linked, shows that there are 3 different versions of the 3B
<clever> and a 3B+
<clever> samueldr: oh, and the codes like a02082, i think those show in /proc/cpuinfo
<sphalerite> clever: nope nothing like that in cpuinfo
<sphalerite> clever: I'm about 5km away from the device right now
<clever> sphalerite: can you pastebin your cpuinfo?
<clever> looks like you want the hardware: and revision:
<clever> ah, but that may be specific to the rpi foundation fork of linux
<clever> are you on a more generic upstream kernel?
<sphalerite> /sys/firmware/devicetree/base/model: Raspberry Pi 3 Model A+
<sphalerite> yeah I'm on linuxPackages_latest from unstable
<clever> ah
<sphalerite> Linux soundblaster 5.2.9 #1-NixOS SMP Fri Aug 16 08:11:12 UTC 2019 aarch64 GNU/Linux
<clever> the devicetree comes from a blob on the SD card, so i'm not sure how much i would trust it
<clever> it relies on the bootloader being configured right, and/or enforcing the right value
<clever> let me see...
<samueldr> clever: make sure you're following the u-boot way of doing it :)
<sphalerite> "The baud rate of the mini UART is linked to the core frequency of the VPU on the VC4 GPU." :|
<clever> sphalerite: do you have the vcgencmd binary?
<sphalerite> no
wildtrees has joined #nixos-aarch64
<samueldr> if it's been loaded through u-boot, and loaded the right device tree, then it looks fine
<samueldr> (oops, linked to 3B+, but scroll a bit)
<sphalerite> yeah
wildtrees has quit [Max SendQ exceeded]
<clever> in an ideal world, with the new rpi4, the DT blob can exist on the spi flash
<clever> and the bootloader will just use that as-is
<samueldr> hahaha
<samueldr> sorry, this was mean
<clever> and then you cant get the wrong one
<clever> and its flash, so it can be fixed
wildtrees has joined #nixos-aarch64
<sphalerite> what was mean?
<clever> samueldr: at least, thats my understanding of how DT was meant to be used
<samueldr> just laughing in the face of ARM implementors
<samueldr> it _is_ how DT was meant to be used :)
<samueldr> but most implementors don't care and ship broken DTs
<samueldr> and then there's linux... that wants to control their device trees and change schemes for their use cases :/
<samueldr> we already have the rpi foundation shipping device trees
<samueldr> it would be best if the mainline kernel would use them outright
<clever> for older models, you sort of rely on start.elf detecting the model for you, and picking the right DT file
<clever> and u-boot having matching detection logic, which you hope is right
wildtrees has quit [Max SendQ exceeded]
<clever> related, ive got an mpr121 touch sensor, it has 11 touch elements
<clever> and linux already has a driver for it, but doesnt map the buttons
<clever> you need to then write your own driver, that specifies the i2c address, and button mappings
<clever> the "platform specific" driver, from the pre-DT days
wildtrees has joined #nixos-aarch64
<clever> i wanted to use DT, but at the time, the kernel rpi shipped lacked DT support
<samueldr> sphalerite: I guess your image came from unstable and not stable, right?
<sphalerite> samueldr: yep
<samueldr> I just looked more in depth
<samueldr> u-boot 2018.09 doesn't have anything for the pluses
<samueldr> neither B+ nor A+
<sphalerite> ah, and that's what's in 19.03?
<samueldr> yes
<samueldr> so I guess that stable with the 4.19 kernel on 3B+ works by luck on 2018.09
<clever> but what will it do for unknown models?
<clever> report the wrong thing, or report nothing?
<samueldr> I'm thinking it doesn't load a new DT
<samueldr> but I'm unsure
<samueldr> it ends up using that
<clever> ah, so it probably wont lie
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
FRidh has quit [Quit: Konversation terminated!]
orivej has quit [Ping timeout: 268 seconds]
ris has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
samrose_ has joined #nixos-aarch64
samrose has quit [Ping timeout: 248 seconds]
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 272 seconds]
zupo has joined #nixos-aarch64
zupo_ has quit [Ping timeout: 244 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
wildtrees has quit [Remote host closed the connection]
wildtrees has joined #nixos-aarch64
t184256 has left #nixos-aarch64 [#nixos-aarch64]
t184256 has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 272 seconds]
ris has quit [Ping timeout: 246 seconds]
balsoft has quit [Ping timeout: 252 seconds]
codyopel has quit [Ping timeout: 252 seconds]
balsoft has joined #nixos-aarch64
atopuzov[m] has quit [Ping timeout: 252 seconds]
nocent has quit [Ping timeout: 252 seconds]
atopuzov[m] has joined #nixos-aarch64
nocent has joined #nixos-aarch64
codyopel has joined #nixos-aarch64
orivej has quit [Ping timeout: 248 seconds]