| 30 Jun 2022 |
Linux Hackerman | it's been discussed previously as well | 08:46:13 |
Linux Hackerman | I agree that we should have more formal documentation on the subject | 08:46:24 |
Linux Hackerman | I disagree that we should make things worse just because there isn't formal documentation on the subject. | 08:46:41 |
matthewcroughan - nix.how | I don't think it's too bad though. | 08:47:05 |
matthewcroughan - nix.how | "worse" in this case is just suboptimal, since we already do it for the pi. | 08:47:14 |
matthewcroughan - nix.how | less than perfect :D | 08:47:28 |
matthewcroughan - nix.how | putting it in nixos-hardware would be perfect, I guess. | 08:47:52 |
matthewcroughan - nix.how | But nixos-hardware is definitely not something that is very active. We'd need to invest in that. | 08:48:38 |
dramforever | I guess I should clarify that the thing I worry about most is not just linux_visionfive but all the other things in the PR | 08:48:47 |
dramforever | there's a lot of vendor specific stuff going on | 08:48:56 |
matthewcroughan - nix.how | Is nixos-hardware itself, very maintainable? | 08:49:33 |
matthewcroughan - nix.how | even if it's the right concept, and right place to put things, is it very good itself? I don't know if it is. | 08:49:45 |
Alyssa Ross | it could probably use some love | 08:49:59 |
matthewcroughan - nix.how | Those layered imports seem wrong to me, is there a better way to do it? | 08:50:14 |
matthewcroughan - nix.how | the chain of imports = [ ../../foo ] and then ../../foo does imports = [ ./foo/foo ] and then ./foo/foo imports ../foo | 08:50:47 |
matthewcroughan - nix.how | * the chain of imports = [ ../../foo ] and then ../../foo does imports = [ ./foo/foo ] and then ./foo/foo imports = ../foo | 08:50:58 |
matthewcroughan - nix.how | * the chain of imports = [ ../../foo ] and then ../../foo does imports = [ ./foo/foo ] and then ./foo/foo imports = [ ../foo ] | 08:51:03 |
matthewcroughan - nix.how | I mean, I do that in my own configs. But my own configs are not as complex as what is in nixos-hardware | 08:51:31 |
Alyssa Ross | https://github.com/NixOS/nixpkgs/pull/179686 | 08:51:46 |
matthewcroughan - nix.how | In reply to @qyliss:fairydust.space https://github.com/NixOS/nixpkgs/pull/179686 Awesome that there's already an example in nixos-hardware which you've linked to. | 08:52:33 |
Alyssa Ross | :) | 08:53:04 |
matthewcroughan - nix.how | nixos-hardware is comparable to a "bsp" in Yocto terminology. A "board support package" if anyone has ever used or dabbled with it. | 08:53:56 |
matthewcroughan - nix.how | Basically they give you a bunch of "bitbake" code, like nix code, which you import. Then it gets rid of all the quirks, and patches software, etc. Much like an overlay in nix. | 08:54:27 |
matthewcroughan - nix.how | An example of what a bsp would do, is patch ffmpeg to have support for the Pi's OMX gpu. | 08:54:58 |
matthewcroughan - nix.how | what we do with configureFlags = [ --enable-omx ] | 08:55:09 |
matthewcroughan - nix.how | * what we do with configureFlags = [ "--enable-omx" ] | 08:55:20 |
dramforever | In reply to @dramforever:matrix.org I guess I should clarify that the thing I worry about most is not just linux_visionfive but all the other things in the PR IMHO We're not even sure how long the VisionFive will last, and what other things StarFive will do, and what the other Linux-capable RISC-V computers in the future will be like. We already know StarFive is working on a JH7110, an even better 8-core thing (I think these two are not the same?). Will we be updating linux_visionfive or will we need linux_visionfive_v2? Are we prepared to deal with upstream issues in github:starfive-tech/*? Will StarFive keep upstreaming their drivers or not? | 08:55:39 |
matthewcroughan - nix.how | https://github.com/agherzan/meta-raspberrypi | 08:55:49 |
matthewcroughan - nix.how | here's what their "BSP" looks like | 08:55:54 |
matthewcroughan - nix.how | So in order to patch mesa, they cannot just mesa.override since their language is simply terrifying and doesn't work like that, they do this https://github.com/agherzan/meta-raspberrypi/tree/master/recipes-graphics/mesa | 08:56:45 |