<samueldr> if you ever think you need to read device tree values from the linux userland: xargs -n1 -0 < /sys/firmware/devicetree/base/compatible
<samueldr> (if you were curious what compatible meant exactly)
orivej has quit [Ping timeout: 250 seconds]
<gchristensen> nice
lopsided98 has quit [Quit: Disconnected]
lopsided98 has joined #nixos-aarch64
<clever> samueldr: oh, thats a nice way of dealing with \0 files!
<clever> never thought of that
<samueldr> :)
<sphalerite> if the rest of the file is text, strings will also do
orivej has joined #nixos-aarch64
<clever> sphalerite: strings has a 4 character minimum, so it can mis shorter things
<sphalerite> clever: huh does strings -n1 not work for that?
<samrose> samueldr: when you build specific version of kernel, did you do something like this?: https://github.com/deepfire/nixos-wiki/blob/master/How%20to%20tweak%20Linux%20kernel%20config%20options.page#L41
<samrose> when you were building 4.20rec4
<samrose> 4.20-rc4 rather
<samueldr> nope
<samueldr> I had a nixpkgs checkout
<samueldr> I updated linux_testing
<samueldr> it wasn't a clean thing, just getting the thing compiled
<samrose> samueldr: so just for testing purposes you were overwriting parts of a checkout of nixpkgs, understood
<samueldr> I was working in a git checkout :)
<samueldr> not modifying the nix store, that would be bad :)
<samueldr> (just saying in case)
<samrose> yes yes totally
<samrose> right on thanks :)
<samrose> samueldr: so then once you modified linux_testing, you were able to specify linux_testing at https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/installer/cd-dvd/sd-image-aarch64.nix#L29 ?
<samueldr> oh, it was a nixos-rebuild boot :)
<samueldr> it's trivial for me since the device works :/
<samueldr> but yeah, if you were to change it to linuxPackages_testing there, it should work
<samrose> so, if I have nixos running on the device (which I do, and am connected via serial console) I can test it easiest by just adding lines to configuration.nix, and nixos-rebuild switch
<samrose> and if that works, then I could get fancier and build the os
<samrose> and if that works, then I could figure out how to overlay this etc
<samrose> ok cool
<samrose> thanks as always
<samrose> so you basically also had to use your git checkout as the nixpkgs source for your configuration.nix on your running nixos instance, in order to change the linux_testing file at https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/kernel/linux-testing.nix
<samueldr> yeah
<samueldr> I always builds my systems using a git checkout, so it just went naturally for me
<samrose> in my x_86 builds I had been testing locally, pushing through hydra, and then have test machines set up to autoupgrade and then running tests on those to assure that changes propagate
<samrose> but your way sounds really good in this context
<samrose> (even if I were pushing changes through hydra)
<samrose> eventually, I will figure out how to create a hydra channel for this on our hydra server. And I will PR the u-boot build and whatever else should be contributed (documentation on nixos.wiki too)
<samrose> interesting I had never explored all the options in nixos-rebuild until now either
Thra11 has joined #nixos-aarch64
<clever> sphalerite: strings -n1 could work, but xargs -0 sounds nicer, since i can get each element of /proc/self/environ seperately
<sphalerite> yeah
<samueldr> and strings isn't available by default in a fresh nixos install :)
<samueldr> ,locate bin strings
<{^_^}> Found in packages: busybox, binutils-unwrapped
<samueldr> it's in binutils; and busybox well, you probably don't want to install that one :)
<clever> samueldr: https://gist.github.com/cleverca22/2208cce6570f58175c64256cd34c7755 now you dont get the entire binutils
<samueldr> still on the system, though not on PATH
<clever> yeah
<samueldr> I made similar helpers for other things recently
<samueldr> e.g. I want `irb` in my PATH, but not `ruby`
worldofpeace has joined #nixos-aarch64
<worldofpeace> Any recommendations for boards to port here? Not looking for a horror show :D
<samueldr> everyone: list what you don't have :)
<samueldr> worldofpeace: what do you want to do?
<samueldr> since porting can be bothersome sometimes
<worldofpeace> samueldr: really strange audio/video experiments
<samueldr> then first look into boards that are useful for that first :)
<samueldr> if you don't have experience with SBCs, maybe even one that's supported instead, so you can gather a bit of experience
<samueldr> then, the next step is mostly to figure out how well-supported it is with mainline projects (uboot, linux)
<samueldr> the more well-supported it is, the better the experience
<worldofpeace> lol, those were my exact thoughts. maybe I'm less confused than I thought, and was looking for confirmation.
<samueldr> though non-mainline != horror necessarily
<samueldr> you could be lucky and have a manufacturer that has a well supported fork with good docs
<samueldr> though chances are low to find such manufacturer
<worldofpeace> I think hardkernel has a fork but I'm thinking mainline would be nice. Mostly worried about the gpus here
<samueldr> though, my biggest pro-tip is: make sure it's aarch64 (armv8)
<samueldr> else you can't drink from the sweet hydra cache
<worldofpeace> totally, much more of a healthy tonic too
<samueldr> oh, another tip: if the only "on-board" storage it supports is SD, it's going to be more painful than most having some eMMC support
<worldofpeace> I'm now taking notes :)
<worldofpeace> Amlogic's stuff is getting mainlined right?
<samueldr> AFAIUI
<samueldr> I don't have a (n aarch64) amlogic board yet
<samueldr> though one is ordered from a crowdfunding campaign already, so eventually I'll know how good it is first-hand
<worldofpeace> ahh reading this was very helpful http://linux-meson.com/doku.php
Thra11 has quit [Ping timeout: 240 seconds]
bobvanderlinden has joined #nixos-aarch64
<bobvanderlinden> It seems my raspberry pi 3 is not able to download the kernel from 18.09 channel becuase it is attempting to build the kernel by itself. I've looked at hydra and it seems building the kernel there has timed out for quite a few attempts. Any idea what is up? https://hydra.nixos.org/job/nixos/release-18.09-aarch64/nixpkgs.linuxPackages.kernel.aarch64-linux
<samueldr> looks like it would take *just* over four hours, and its timeout is four hours :/
<samueldr> the machine has been a bit overloaded lately
<samueldr> not sure what was going on, but tasks on hydra were getting cancelled
<samueldr> it's been chewing on those since yesterday, about half of the 18.09 backlog has been built
<samueldr> well, not necessarily built, but at least tried
<bobvanderlinden> aw that's too bad. timeout cannot be increased?
<samueldr> it can, it probably will, but ideally if there's something else at play, the something else should be fixed :)
<bobvanderlinden> very true :P
<bobvanderlinden> anything I can do to help?
<samueldr> no idea
<samueldr> though yeah, lookin in the history, looks like it sometimes hits 4 hours, sometimes ends in 2
<samueldr> weird, two successful builds at more than four hours in the past
<samueldr> I wonder if a setting was changed, I'll look more into it this evening
<bobvanderlinden> thanks!
<bobvanderlinden> that said though, why doesn't 18.09 reside on that latest succesful build of the kernel?
<samueldr> the sneaky truth is that there's no aarch64 channel
<bobvanderlinden> oh that is pretty sneaky :P
<samueldr> and if the x86_64 channel waited for aarch64, it would be out of date too
<bobvanderlinden> aah right
<bobvanderlinden> so probably a aarch64 channel should be added to hydra somehow
<samueldr> yeah, something along the line
<bobvanderlinden> ok, but that explains quite a bit. thanks for the info
bobvanderlinden_ has joined #nixos-aarch64
bobvanderlinden has quit [Ping timeout: 256 seconds]
bobvanderlinden_ has quit [Ping timeout: 256 seconds]