[U-Boot] [PATCH 1/1][nvme] Fix PRP Offset Invalid

Hopefully this addresses your concerns. Note that nprbs can't be used directly for the size since one must be removed from each page to point to the next page. -Aaron ___ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] [PATCH 1/1] nvme: Fix PRP Offset Invalid

Hi Aaron, On Wed, Aug 21, 2019 at 8:34 AM Aaron Williams wrote: > > When large writes take place I saw a Samsung > EVO 970+ return a status value of 0x13, PRP > Offset Invalid. I tracked this down to the > improper handling of PRP entries. The blocks > the PRP entries are placed in cannot cross

[U-Boot] [PATCH 1/1] nvme: Fix PRP Offset Invalid

When large writes take place I saw a Samsung EVO 970+ return a status value of 0x13, PRP Offset Invalid. I tracked this down to the improper handling of PRP entries. The blocks the PRP entries are placed in cannot cross a page boundary and thus should be allocated on page boundaries. This is how

[U-Boot] [PATCH 1/1] nvme: Fix PRP Offset Invalid

When large writes take place I saw a Samsung EVO 970+ return a status value of 0x13, PRP Offset Invalid. I tracked this down to the improper handling of PRP entries. The blocks the PRP entries are placed in cannot cross a page boundary and thus should be allocated on page boundaries. This is how

[U-Boot] [PATCH 1/1] nvme: Fix PRP Offset Invalid

When large writes take place I saw a Samsung EVO 970+ return a status value of 0x13, PRP Offset Invalid. I tracked this down to the improper handling of PRP entries. The blocks the PRP entries are placed in cannot cross a page boundary and thus should be allocated on page boundaries. This is how