Hi Bin, On 1 June 2017 at 17:04, Bin Meng <bmeng...@gmail.com> wrote: > Hi Simon, > > On Thu, Jun 1, 2017 at 9:14 PM, Simon Glass <s...@chromium.org> wrote: >> Hi Bin, >> >> On 1 June 2017 at 01:27, Bin Meng <bmeng...@gmail.com> wrote: >>> >>> Hi Simon, >>> >>> On Wed, May 17, 2017 at 8:42 AM, Bin Meng <bmeng...@gmail.com> wrote: >>> > Hi Simon, >>> > >>> > On Sat, May 13, 2017 at 9:11 AM, Simon Glass <s...@chromium.org> wrote: >>> >> Hi Bin, >>> >> >>> >> On 8 May 2017 at 01:05, Bin Meng <bmeng...@gmail.com> wrote: >>> >>> Hi Simon, >>> >>> >>> >>> On Mon, Apr 10, 2017 at 8:38 AM, Simon Glass <s...@chromium.org> wrote: >>> >>>> This is not to be applied. It is needed to test using CONFIG_DM_MMC on >>> >>>> x86 >>> >>>> since SCSI is broken with this setup. >>> >>>> >>> >>>> Signed-off-by: Simon Glass <s...@chromium.org> >>> >>>> --- >>> >>> >>> >>> When you said "SCSI is broken with this setup", did you mean GP# >>> >>> exception when boot up with a hard disk like below? >>> >> >>> >> Yes that's right. >>> >> >>> > >>> > Do you plan to work on a patch soon? >>> > >>> >>> I tracked down the exception happens at part_test_efi()->block_dread() >>> function: >>> >>> if (!ops->read) >>> return -ENOSYS; >>> >>> Where ops points to nowhere, because underlying SATA device does not >>> have a DM driver associated. >>> >>> Could you please fix this? >> >> I've been hoping that someone else will take on this side of things, >> but perhaps I am optimistic. I'll see if I can take a look. > > Thanks. I wanted to fix this myself however I have been busy on some > other stuff.
I've sent a series which I think puts SCSI and SATA in a better position with respect to driver model. However even with that there is more work to do. Regards, Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
