From: Michael Orlitzky <michael@orlitzky.com>
To: Chen Wang <unicorn_wang@outlook.com>
Cc: sophgo@lists.linux.dev, Han Gao <rabenda.cn@gmail.com>,
Inochi Amaoto <inochiama@outlook.com>,
Han Gao <gaohan@iscas.ac.cn>
Subject: Re: SG2042 SATA (DMA?) issues
Date: Mon, 1 Jun 2026 02:47:31 -0400 [thread overview]
Message-ID: <ah0rA-c34RLkHWYt@mertle> (raw)
In-Reply-To: <MA5PR01MB12500AE1ED1AD25C00C4BA706FE152@MA5PR01MB12500.INDPRD01.PROD.OUTLOOK.COM>
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.
next prev parent reply other threads:[~2026-06-01 6:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 4:32 SG2042 SATA (DMA?) issues Michael Orlitzky
2026-05-31 15:05 ` Michael Orlitzky
2026-06-01 0:31 ` Chen Wang
2026-06-01 2:22 ` Michael Orlitzky
2026-06-01 6:06 ` Chen Wang
2026-06-01 6:47 ` Michael Orlitzky [this message]
2026-06-01 8:00 ` Chen Wang
2026-06-01 8:12 ` Michael Orlitzky
2026-06-02 12:19 ` Han Gao
2026-06-02 19:20 ` Michael Orlitzky
2026-06-03 9:14 ` Niklas Cassel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ah0rA-c34RLkHWYt@mertle \
--to=michael@orlitzky.com \
--cc=gaohan@iscas.ac.cn \
--cc=inochiama@outlook.com \
--cc=rabenda.cn@gmail.com \
--cc=sophgo@lists.linux.dev \
--cc=unicorn_wang@outlook.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox