On Wed, Jan 10, 2024 at 04:26:11PM +0100, Ahmad Fatoum wrote: > Hello Sascha, > > On 10.01.24 16:18, Sascha Hauer wrote: > > On Wed, Jan 10, 2024 at 03:39:58PM +0100, Ahmad Fatoum wrote: > >> The barebox bootm command is often not called directly, but via > >> bootloader spec or FIT image boot handlers. For debugging, it can be > >> useful to reuse those boot handlers, but replace single artifacts, e.g. > >> using the barebox device tree instead of the bootloader-spec provided > >> device tree. > >> > >> To make this easier, have boot -v -d (verbose + dry run) write a boot > >> script that reproduces the cancelled boot to /env/boot/cancelled. > > > > I like the idea very much. I also had this problem more than once. > > > > I think an explicit option rather than "-v -d" would be better. With > > this there would be a natural way to document this behaviour in the > > boot help output. > > > > /env/boot/cancelled would be saved in the environment with a saveenv > > which is likely not desirable. Maybe better put it somewhere in /tmp/? > > Or have the new option take an argument, which would be the path to save > the file to? We could make that argument optional, then we could still fall back to a default when no path is given. Sascha -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
