> Am 08.02.2018 um 06:49 schrieb Jonathan Gray <j...@jsg.id.au>: > > On Mon, Feb 05, 2018 at 11:31:42AM +0100, Mark Kettenis wrote: >>> Date: Mon, 5 Feb 2018 21:06:59 +1100 >>> From: Jonathan Gray <j...@jsg.id.au> >>> >>>>> booting sd0a:/bsd: open sd0a:/bsd: Device not configured >>>>> failed(6). will try /bsd >>>> >>>> How do you find out that it's sd0a instead of sd1a? >>> >>> The loaded image protocol I believe. >> >> Actually the OpenBSD bootloader currently only supports loading the >> bsd kernel from the same device as the bootloader. It will always >> call that device sd0. It invokes the device path protocol on the >> loaded image handle and then matches that path to a device that >> supports the block io protocol. > > Perhaps the problem is elsewhere as U-Boot master also broke > vexpress_ca15_tc2 and mx6cuboxi targets:
Perfect, so can you quickly bisect it now that the bisect doesnât end at the pinctrl driver? Alex _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot