commit 64d86024083f5e53c610d9bba1018f59a2078b9e parent 8250d592ba664e07479e0b46170f35e8718dc932 Author: Daniel Barlow <dan@telent.net> Date: Sun, 19 Mar 2023 20:27:43 +0000 some kexecboot notes Diffstat:
| M | THOUGHTS.txt | | | 25 | +++++++++++++++++++++++++ |
1 file changed, 25 insertions(+), 0 deletions(-)
diff --git a/THOUGHTS.txt b/THOUGHTS.txt @@ -1208,3 +1208,28 @@ Wed Mar 15 19:11:09 GMT 2023 defined location "tftpboot" implies "revertable", because it will use the same ramdisk + + +Fri Mar 17 11:44:40 GMT 2023 + +- patch the kernel kexec code to pass DTB to new kernel unconditionally +- unpatch pernel to pass command line to kexec (breaks DTB passing) +- decide how we specify rootfs. doing it by number is awkward + - may be phram + - may be real mtd root + - may be real mtd root but renumbered becuase phram exists + +Wild idea: we could probably get rid of the need for declaring a phram +device in the first kernel, if we can use kexec to copy the squashfs into +physical ram. As far as I can see this is a simple(sic) matter of +specifying it as a segment, but we would have to extend kexec-tools +to do this and it's quite a niche option if we make it do all the +mtd setup. + +kexec --dtb=foo.dtb --map-file=squashfs@0x120000 + + +Sat Mar 18 18:02:26 GMT 2023 +What if: we added derivations for "apply openwrt changes" as packages, +which could then be called from the kernel derivation's extraPatchPhase? +There could be one for generic and one for each openwrt targetop