<samueldr>
I even have an amlogic board on hand to look at!
<samueldr>
but I kind of don't really care because it has an SPI flash
<samueldr>
and a **really** good u-boot distro from the vendor!
<samueldr>
they actually care to make their u-boot act like a generic pc bios
sorki is now known as srk
<gchristensen>
oh wow nice
<samueldr>
including a menu driven interface, rather than just a command-line ish console
<samueldr>
even one step further, they have a customized minimal linux distro that can be booted to RAM and used to automatically install other distros!
<zhaofeng_ircclou>
Wait, all from amlogic themselves?
<samueldr>
nope
<samueldr>
libre.computer did a lot of the work
<gchristensen>
nice
<samueldr>
(of making the firmware nice)
<zhaofeng_ircclou>
pretty cool
<samueldr>
they really are a cool small gang
<samueldr>
they really push to have everything done on mainline
<samueldr>
they had a big tarnishing failure recently with another board
<samueldr>
because the vendor failed to cooperate
* zhaofeng_ircclou
has a Phicomm N1 (amlogic s905x) with a faulty emmc :/
bennofs__ has joined #nixos-aarch64
bennofs_ has quit [Ping timeout: 276 seconds]
Thra11 has quit [Quit: WeeChat 3.1]
rajivr has joined #nixos-aarch64
<gchristensen>
well ... that's a bummer: "error: Package ‘cnijfilter2-6.00’ in /nix/store/mlqxab6h6f2w70c1yrh4z1ns3qvba948-nixexprs.tar.xz/pkgs/misc/cups/drivers/cnijfilter2/default.nix:117 is not supported on ‘aarch64-linux’, refusing to evaluate."
h0m1 has quit [Ping timeout: 272 seconds]
h0m1 has joined #nixos-aarch64
<samueldr>
oh, printers
<samueldr>
nothing good can come from wanting to print
<zhaofeng>
For printers, I've found those that support wireless mostly pain-free, as they often implement ipp everywhere
ajs124 has quit [Quit: Bridge terminating on SIGTERM]
ajs124 has joined #nixos-aarch64
justan0theruser has quit [Ping timeout: 272 seconds]
evils has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-aarch64
cole-h has quit [Ping timeout: 256 seconds]
<Ke>
zhaofeng, samueldr: I guess it was pointed out, but generally ext* are the only typical filesystems that have inode tables that can run out
<Ke>
at least not ZFS, btrfs, xfs to my knowledge
<ar>
Ke: iirc reiserfs also had this issue
<Ke>
possibly, not commonly in use anymore, I hope
<Ke>
I might guess that many more traditional unix filesystems I have never heard of people using have those
<Ke>
like gentoo installation manual had jfs and some others, but I don't even know anyone who admitted trying them out
<Ke>
I did use reiserfs and reiser4 myseld
<Ke>
reiser4 is the reason I don't touch out of tree filesystems anymore
<Ke>
not because reiser4 was bad, but it limited too much, what kernels I could use
patagonicus has quit [Ping timeout: 264 seconds]
<Ke>
actually it worked flawlessly for me
<ar>
zfs these days gets updated for new kernels relatively fast
<Ke>
maybe, though ZFS recently blocked my kernel on nixos even while I was not even using it
<Ke>
lazy evaluation is like magnets: magic
<Ke>
if I have to modify nixpkgs for it, it's already too much
<Ke>
there is an issue for similar problem where using newer kernel and unstable zfs still faces some issues
<Ke>
admittely this is either nix or nixos bug most likely
<{^_^}>
#109031 (by Atemu, 8 weeks ago, open): Packages are still built against zfsStable when boot.zfs.enableUnstable
<Ke>
sphalerite admitted seeing this issue, but I believe he also thought it aws magic, though did not expressly mention magnets
<Ke>
root cause was something like zfs kernel package name gets evaluated even though it's not used and that triggers an assertion
<Ke>
I have absolutely no idea how to debug lazy evaluation
patagonicus has joined #nixos-aarch64
<Ke>
samueldr: reading on the implementation it seems to me that the keyboard is integrated to the init framework and not something that could be used with traditional nixos
dev_mohe has quit [Remote host closed the connection]
dev_mohe has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
dev_mohe has quit [Quit: dev_mohe]
FRidh has quit [Ping timeout: 246 seconds]
FRidh has joined #nixos-aarch64
evils has joined #nixos-aarch64
monk has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
zupo has joined #nixos-aarch64
dev_mohe has joined #nixos-aarch64
<samueldr>
Ke: it's not strictly integrated, there is an interface between the init part and the splash
<samueldr>
but it is part of the splash app
<samueldr>
what I mean to say is that it was written in a way where making all of this work independently shouldn't be too hard
<samueldr>
(because anyway it's possible that the custom init will go away at some point)
<samueldr>
Ke: that memory thing is not used yet, it's an informational data point that represents the lowest amount of memory a specific device can have
<samueldr>
e.g. if you were to make a default.nix for a ROG phone 5, you wouldn't put 18GB, but 6GB (IIRC)
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
* samueldr
is looking at helios64
<samueldr>
=> sf probe
<samueldr>
Invalid bus 0 (err=-19)
<samueldr>
poo, more work than "it just works" looks like
<samueldr>
other than using Nix (lol) I wonder what tools could help managing a u-boot distro easier
<samueldr>
I'm strongly considering building an opinionated u-boot distro, with a common feature set among boards, aimed at acting like a standard firmware interface
<samueldr>
like, I wonder if e.g. debian and such have good tools to maintain patches on top of large projects
<samueldr>
or if it's just good ol' git wrangling
<ar>
samueldr: there's a tool called "quilt" I've heard some debian people use
<samueldr>
AFAIUI it's to manage patches as patch files like a git branch
<samueldr>
the main goal would be supporting devices with SPI flash or similarly isolated firmware storage
<samueldr>
and having other type of devices somewhat supported, but with tricks
<samueldr>
e.g. "holey" GPT for allwinner, maybe something else for rockchip
<samueldr>
with the idea that it gets managed like a BIOS, maybe with fwupd management