m1n1/proxyclient
Kyle Evans 0ba2027e5e proxyclient: tools: add a FreeBSD loader
The differences are documented in the script itself, but the main odd
bit is that we pass the provided kernel as an initramfs.  Our modified
loader will probe for the initramfs start/end props in FDT and put up
a memdisk that we load the kernel from.  This choice was made for two
reasons:

1.) Avoid ad-hoc interpretations of a memory region in m1n1, it doesn't
    care if we actually passed it an initramfs or not anyways.

2.) We already had some code on hand to do this in our loader, so I
    suspect we've done similar shenanigans elsewhere anyways.

This also requires a U-Boot change to allow bootefi of an arbitrary
location, as long the size is provided.

The alignment constraints for loader/kernel were kept arbitrarily.  The
kernel will be bounced anyways by loader. I don't recall what
alignment requirements UEFI payloads have, but 2M seems reasonable.

Signed-off-by: Kyle Evans <kevans@FreeBSD.org>
2022-04-16 19:22:55 +09:00
..
experiments Make scripts executable 2022-04-16 19:17:33 +09:00
hv m1n1.hv: Add trace script keyboard/trackpad 2022-03-11 12:06:01 +09:00
m1n1 m1n1.utils.Reloadable: Add force argument to _reloadcls() 2022-04-16 19:06:22 +09:00
tools proxyclient: tools: add a FreeBSD loader 2022-04-16 19:22:55 +09:00