Hi Alex, On 26 August 2018 at 18:58, Alexander Graf <ag...@suse.de> wrote: > > > On 08.08.18 11:54, Simon Glass wrote: >> This jumps to test code which can call directly into the EFI support. It >> does not need a separate image so it is easy to write tests with it. >> >> This test can be executed without causing problems to the run-time >> environment (e.g. U-Boot does not need to reboot afterwards). >> >> For now the test just outputs a message. To try it: >> >> ./sandbox/u-boot -c "bootefi test" >> U-Boot 2017.09-00204-g696c9855fe (Sep 17 2017 - 16:43:53 -0600) >> >> DRAM: 128 MiB >> MMC: >> Using default environment >> >> In: serial >> Out: serial >> Err: serial >> SCSI: Net: No ethernet found. >> IDE: Bus 0: not available >> Found 0 disks >> WARNING: booting without device tree >> Hello, world! >> Test passed >> >> Signed-off-by: Simon Glass <s...@chromium.org> > > I think I'm missing the point of this exercise. What's the problem with > running the selftest suite? Its set of tests that it runs can be > configured using an environment variable just fine?
I'm not saying you can't run the selftest suite, but that is for a different purpose. This is just a sanity check. I'll change the name to 'ping instead'. Regards, Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
