<k0ral>
samueldr: I am not using linuxPackages_rpi as the wiki says it is only for RPi 1, and following our recent discussion I am not using linuxPackages_latest either as it made it impossible to boot correctly IIRC, so I am using whatever is the default
<samueldr>
the wiki note is partially misleading; it initially was built only for the pi 1, but since a few years back, when it was written, it now also builds the foundation's kernel with the right configuration
<samueldr>
the default would be the latest lts at the time of the release, so presumably 4.19, since that's what on 19.03 and 19.09
<samueldr>
which board is it, that is impossible to boot correctly witht linuxPackages_latest?
* samueldr
re-reads backlog
<samueldr>
I quickly looked, I think you never specified whether it was a 3B or 3B+ (or maybe another one?)
<samueldr>
there is a reported issue on the 3B+ combined with linuxPackages_latest, which may be fixed by using a more recent u-boot than what shipped with 19.03
<k0ral>
3B+ (sorry for the response delay)
<k0ral>
are you suggesting I use the _rpi kernel then ?
<k0ral>
I should*
zupo has joined #nixos-aarch64
<k0ral>
I've just tried and the dtbo fails to apply with _rpi the same way
zupo has quit [Ping timeout: 240 seconds]
zupo has joined #nixos-aarch64
jtojnar has quit [Quit: jtojnar]
zupo has quit [Ping timeout: 240 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has joined #nixos-aarch64
vika_nezrimaya has joined #nixos-aarch64
orivej has quit [Ping timeout: 276 seconds]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
zupo has quit [Ping timeout: 245 seconds]
zupo has joined #nixos-aarch64
_ris has joined #nixos-aarch64
orivej has quit [Read error: Connection timed out]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 276 seconds]
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
pi2 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
WilliButz has quit [Remote host closed the connection]
WilliButz has joined #nixos-aarch64
vika_nezrimaya has quit [Read error: Connection reset by peer]
vika_nezrimaya has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
<samueldr>
:/ I would have initially assumed it might have worked better, that's because it's known that the device tree files are different between mainline and the foundation's fork
<samueldr>
though I don't have the right experience to help
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 268 seconds]
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<MichaelEden[m]>
What would it take to have Hydra keep track of cross compilation regressions and progress? I'd be interested to see the percent of nixpkgs that can be cross compiled
<samueldr>
that it'd be configured build a part, if not all, of nixpkgs with cross-compilation
<samueldr>
and maybe some more infra to run that
<samueldr>
though it should be doable at a reduced rate too
<samueldr>
though, having it built is not the same as keeping track of compilations, regressions and progress, if no one keeps tabs :)
<samueldr>
(though, again, it'd at least list numbers)
<MichaelEden[m]>
Is it something that I can write a PR for or does it need extra decision power because it might cost more money?
<MichaelEden[m]>
I guess I've never contributed to Hydra so I don't know the process