On Sun, Oct 8, 2017 at 11:33 PM, Jonathan Gray <j...@jsg.id.au> wrote: > On Sun, Oct 08, 2017 at 11:33:08AM -0400, Rob Clark wrote: >> This fixes an issue with OpenBSD's bootloader, and I think should also >> fix a similar issue with grub2 on legacy devices. In the legacy case >> we were creating disk objects for the partitions, but not also the >> parent device. >> >> Reported-by: Jonathan Gray <j...@jsg.id.au> >> Signed-off-by: Rob Clark <robdcl...@gmail.com> > > Thanks for looking into this. While this lets armv7/bootarm.efi > boot again on cubox-i and bbb it doesn't help rpi3. > > What is the easiest way to get U-Boot to display these paths > to be able to compare the current behaviour to 2017.09? >
in grub, there is the lsefi command, not sure if the OpenBSD bootloader has something similar? u-boot implements that device-path to text protocol, so it should be pretty easy to implement something like this if not. BR, -R _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
