m1n1 user guide: document build/kmutil target#266
Conversation
|
Please sign off your commit |
1101d60 to
af4851f
Compare
Introduced in AsahiLinux/m1n1#573, simplifying the amount of manual steps a lot. Signed-off-by: Florian Klink <flokli@flokli.de>
af4851f to
6dfac23
Compare
|
I'm planning to extend this to |
Are you ok with landing this as-is, and updating the docs later? Or you want to keep this open until that's landed? |
|
AsahiLinux/m1n1#601 has the kmutil script server |
|
Ok, can you cherry pick my commit into there and update it? Probably makes more sense. |
jannau
left a comment
There was a problem hiding this comment.
I don't follow the comment about cherry-picking. docs and m1n1 are separate repositories. Please update this PR once AsahiLinux/m1n1#601 is merged
| To build that, and expose it via a webserver, run: | ||
|
|
||
| ```shell | ||
| ip -br a s |
There was a problem hiding this comment.
while somewhat helpful the ip command looks a little odd here. I would expect anyone using this to be familiar with their local network. kmutil.py itself could print network info at startup. I'm not going to implement that but would accept PRs.
|
|
||
| m1n1 stage 1 release builds packaged with the Asahi Linux Installer have both of those options set. m1n1 stage 2 release builds packaged by distros should just have `RELEASE=1` (since they do not need to chainload further) and thus do not need Rust to build. | ||
|
|
||
| ### kmutil target |
There was a problem hiding this comment.
please update for the kmutil.py script
| This assumes you manually fetched the m1n1-stage1.bin from somewhere. | ||
| If you used the `build/kmutil` target above, you can also: | ||
|
|
||
| ``` |
| If you used the `build/kmutil` target above, you can also: | ||
|
|
||
| ``` | ||
| sh <(curl HOST:8000/kmutil) |
There was a problem hiding this comment.
with kmutil.py the URL could be simplified to HOST:8000.
Introduced in AsahiLinux/m1n1#573, simplifying the amount of manual steps a lot.