<samueldr>
you're probably better served by scraping the html page :/
<Enzime>
samueldr: I'm curious if Dezgeg made a scraper or just manually went through and checked each :p
<samueldr>
yeah now I am too
<samueldr>
(but I'm not sure that in 2015 there was an API)
<samueldr>
(the currently built hydra manual on the nixos.org website doesn't list the API section_
<samueldr>
btw, if you intend to scrape: please don't hit hydra more than once (load the document and work with a local copy)
<samueldr>
and use the ?full=1 link once you have scraping figured out; by default it limits the number of still [failing|succeeding] jobs
<Enzime>
👍
<samueldr>
oh, and please share the results / script :)
<gchristensen>
and be gentle
<Enzime>
I feel like it'd probably be better just to make an endpoint on Hydra for viewing this info if possible
<gchristensen>
rate limit yourself
<gchristensen>
yes
nix-build has joined #nixos-aarch64
orivej has quit [Ping timeout: 272 seconds]
orivej_ has joined #nixos-aarch64
orivej_ has quit [Ping timeout: 244 seconds]
codyopel[m] has quit [Read error: Connection reset by peer]
thefloweringash[ has quit [Read error: Connection reset by peer]
sphalerit has quit [Read error: Connection reset by peer]
bkchr[m] has quit [Read error: Connection reset by peer]
timokau[m] has quit [Remote host closed the connection]
pdafriend[m] has quit [Read error: Connection reset by peer]
dtz[m] has quit [Read error: Connection reset by peer]
bkchr[m] has joined #nixos-aarch64
codyopel[m] has joined #nixos-aarch64
dtz[m] has joined #nixos-aarch64
timokau[m] has joined #nixos-aarch64
pdafriend[m] has joined #nixos-aarch64
sphalerit has joined #nixos-aarch64
thefloweringash[ has joined #nixos-aarch64
orivej has joined #nixos-aarch64
<Dezgeg>
Enzime, samueldr: yes it scrapes the html with... bash
jtojnar has quit [Quit: jtojnar]
jtojnar has joined #nixos-aarch64
nix-build has quit [Remote host closed the connection]
{^_^} has joined #nixos-aarch64
{^_^} has quit [Changing host]
{^_^} has joined #nixos-aarch64
<gchristensen>
anyone in here have interesting use cases for NixOS & Aarch64?
<andi->
a replacement for SGX with the ARM trusted foo? But no real use-case in mind and IMO the TEE (was it named like that?) is also broken :)
<samueldr>
gchristensen: running nixos on my cellphone :)
<samueldr>
(which is on the backburner right now)
<samueldr>
an uninteresting one is to use synergy and hdmi out of an SBC as an extended screen
{^_^} has quit [Remote host closed the connection]
{^_^} has joined #nixos-aarch64
<grw>
gchristensen: shairport server, gps ntp server
<grw>
depends on your definition of "interesting" :p
<gchristensen>
that is up to you!
<grw>
also tried to make a kodi box, didnt get that running yet tho
orivej has quit [Ping timeout: 272 seconds]
{^_^} has quit [Remote host closed the connection]
{^_^} has joined #nixos-aarch64
orivej has joined #nixos-aarch64
<sphalerite>
gchristensen: I want nixos on my phone as well. Also full-featured ARM laptop. Intel stuff won't work without nonfree software, with some ARM machines there's a chance :D
<Dezgeg>
are there modern ones where there's a chance?
<sphalerite>
gchristensen: also it's not strictly an ARM thing but the massively parallelism available on machines like the community box is really useful
<sphalerite>
Dezgeg: Asus C101PA and similar chromebooks
<Dezgeg>
so it has open DDR4 memory initialization code? I think that's the latest one bringing trouble on many SoCs?
<Dezgeg>
or maybe they were just brave enough to put it in ROM x)
<samueldr>
conjecture, but I believe it's handled by depthcharge/chromium os' depthcharge; it was for the pixel c, which was initially bound to be a chromeos device
<samueldr>
if it is still, it's well-enough removed from the end-user since it's not present on the boot disks, but still a blob :(
<samueldr>
ugh, I means coreboot/chromium os' depthcharge
<sphalerite>
samueldr: no it's handled by coreboot
<sphalerite>
depthcharge just loads the kernel and stuff
<samueldr>
yeah that was a "or" since I didn't know whether they somehow put it into depthcharge
<Dezgeg>
initializing DRAM is usually a quite early operation :P
<samueldr>
from memory, switch hacking scene, it'll run slower until initialized, right? anything actually stopping loading the training data way later?
<samueldr>
(just curious here)
<Dezgeg>
I guess it depends on the platform, maybe tegra does some initialization of it in the bootrom (because the previous generations did), but generally no, you do need to initialize it to acces it at all
<samueldr>
I love how in this community asking questions, even basic~ish often is answered with good links to follow up, which is also why I try whenever I can to do the same :)
<sphalerite>
yeah
<sphalerite>
yesterday someone asked about a translation bug, and I spent most of the day digging into it
* samueldr
wonders if nix is a nerd snipe tarpit
<samueldr>
:)
<sphalerite>
maybe
<samueldr>
(I know this can sound pejorative and negative, but it's not)
<samueldr>
idea I had the other day, don't know if there's value: on merge-eval-failure, eval both master-without-merge and PR commit without merge to help figuring out the issue?
<samueldr>
failing evals would take ×3 longer to eval though