Re: SG2042 SATA (DMA?) issues

Chen Wang <[email protected]> Mon, 1 Jun 2026 16:00:04 +0800
Newsgroups dev.linux.lists.sophgo
Message-ID <MA5PR01MB1250071E879EDEC8ED3A29813FE152@MA5PR01MB12500.INDPRD01.PROD.OUTLOOK.COM>
Hi,Mike,

On 6/1/2026 2:47 PM, Michael Orlitzky wrote:
> On 2026-06-01 14:06:29, Chen Wang wrote:
>>>     * SRA1-20.fd (20251209)
>>>     * fip.bin (20251209, from the bootloader-riscv repo)
>>>     * fw_dynamic.bin (20251106)
>>>     * zsbl.bin (20251215)
>>>     * mango-milkv-pioneer.dtb (20251215)
>> Are these firmware components correspond to the https://github.com/sophgo/edk2-non-osi/commit/017a5aea26a066fd2bf501b7893937183165af36?
> The dates listed above are before any dma-coherent patches. This set
> of firmware files is OK, no filesystem corruption.
>
>
>> Just want to double-confirm if we use
>> https://github.com/sophgo/edk2-non-osi/commit/017a5aea26a066fd2bf501b7893937183165af36
>> plus the dts dma-coherenet patch, how the SATA works?
> The older firmware, without the patch, works. It is the newer firmware
> (plus the dma-coherent patch) that appears to cause the problem.

I'm a little confused about what you mean by "newer firmware." Do you 
mean >= 017a5aea or > 017a5aea?

Because in your last email you mentioned you discovered the problem 
starting with b379b067.

The firmware's tree log is as follows:

https://github.com/sophgo/edk2-non-osi/commits/devel-sg2042/

latest commit

.
b379b067
017a5aea <---- dma-coherenet patch was submitted together with this commit.
.... older commit