hi Peter, On Fri, 27 Jun 2025 at 17:36, Peter Robinson <pbrobin...@gmail.com> wrote: > > Hey Sughosh, > > > Add support for adding URI based boot option through the eficonfig > > command. Also add a basic test case for checking validity of the URI's > > being passed to the wget function. > > I suspect more an extension to this feature, have we looked at getting > the URI boot options via dhcp? > > I'm not sure what options the LWIP dhcp stack support but it would be > a useful automatic deployment option
That is an interesting use-case scenario. The one thing to think about is whether it would be better to do this through a dedicated command instead -- that command can then support other aspects that Heinrich had suggested earlier. Things like which network interface to use, the http server ip, the address to load the payload to from the server etc. Also, eficonfig is a boot menu driven maintenance of the Bootxxxx variables. So it might be a bit cumbersome from the point of scripting this. -sughosh > > > Changes since V2: > > * Added comments for eficonfig_create_uri_device_path() - patch 1 > > * Added comments for fill_dp_uri() - patch 1 > > * Remove some superfluous newlines added - patch 1 > > > > > > Sughosh Ganu (2): > > cmd: eficonfig: add support for URI device path based boot options > > test: wget: add a test case for validating URI > > > > cmd/eficonfig.c | 131 ++++++++++++++++++++++++++++++++++++++++--- > > include/efi_config.h | 4 ++ > > test/cmd/wget.c | 20 +++++++ > > 3 files changed, 147 insertions(+), 8 deletions(-) > > > > -- > > 2.34.1 > > > >
