Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split kernels into separate repo? #118

Open
henrytill opened this issue Jul 5, 2020 · 4 comments
Open

Split kernels into separate repo? #118

henrytill opened this issue Jul 5, 2020 · 4 comments
Assignees

Comments

@henrytill
Copy link
Member

Initial discussion with @betaboon here:
#116 (comment)

@henrytill's thoughts:

The kernels are the thing that are updated the most frequently (everything else has been mostly static for some time now), so a basic split where the kernels were a submodule, subtree, or Nix fetch would require updating hashes (or subtrees) every time the kernels are updated, which is a tad suboptimal (though likely not a deal-breaker).

I wonder if there is some way to structure things so that the audio stuff can be layered on top without needing to "include" the kernels in the repo (as a submodule/subtree/fetch etc.).

@henrytill henrytill self-assigned this Jul 5, 2020
@magnetophon
Copy link
Member

Has anyone looked at NixOS/nixpkgs#96702 ?

If those are good, do we need the kernels in here at all?

@tex
Copy link
Contributor

tex commented Nov 29, 2020

Booted into linux-rt_latest from nixpkgs and it works as far as I can tell. Is there any point to have musnix if running this nixpkgs rt kernel? Obvious advantage od nixpkgs rt kernel is that Hydra builds it and I never has to build it myself.

@magnetophon
Copy link
Member

@tex I'm running those as well.
There still is a lot of other stuff musnix does, so it's still useful if you want to run rt audio.

@betaboon
Copy link
Contributor

betaboon commented Dec 1, 2020

i switched to using the rt-kernels in nixpkgs aswell as soon as they got available :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants