On 12/5/24 5:27 AM, Abbarapu, Venkatesh wrote:
[...]
So there is still something broken in that specific commit that I
missed when removing the defects ? Sigh ... can you try to narrow it down ?
Hi Marek, I tried to narrow the changes in commit
5d40b3d384dc536ec26ce9b76b20b0b84749d2d1 a bit by first applying all
of the changes in the .h files, and then for spi-nor-core.c, only
applying changes per function. The only function change that causes
errors was spi_nor_read(). With the changes in spi_nor_read() in
commit
5d40b3d384dc536ec26ce9b76b20b0b84749d2d1 applied to the prior commit
fbe16bc2801, did I get:
=> sf probe && sf update ${loadaddr} 0x400000 0x10
SF: Detected s28hs512t with page size 256 Bytes, erase size 256 KiB,
total 64 MiB device 0 offset 0x400000, size 0x10 SPI flash failed in
read step
Hi all. What is the status of addressing the failures introduced by this
patchset? I
tried building from u-boot next and still see the failure.
Marek, was the isolation of changes I performed above helpful in understanding
the
failure?
Can you try by applying this change
https://lore.kernel.org/u-boot/[email protected]/
Can you please CC me on SPI NOR patches related to this stacked/parallel
breakage ?
