Message ID | 20230525093637.31364-1-yanhong.wang@starfivetech.com |
---|---|
Headers | show |
Series | Add ethernet driver for StarFive JH7110 SoC | expand |
On Thu, 25 May 2023 17:36:26 +0800 Yanhong Wang <yanhong.wang@starfivetech.com> wrote: [...] > The main difference between StarFive VisionFive 2 1.2A and 1.3B is > gmac, but the difference in gmac is not defined in DT, but reads the > PCB version from EEPROM, and then dynamically configures the > difference of gmac according to different PCB versions, which is > compatible with 1.2A and 1.3B versions, which is more user-friendly. Big ACK from me so far, it is overdue to clean the duplication mess that is currently in master. > The PHY and MAC driver has been tested on the StarFive VisionFive 2 > 1.2A and 1.3B boards and works normally. But for a complete test I'd like to see the respectively correct DTB passed to the OS, and that requires the other issue (base / clock support and single DT) to be resolved first. Thanks! Torsten
On Thu, 25 May 2023 17:36:26 +0800 Yanhong Wang <yanhong.wang@starfivetech.com> wrote: [...] > > base-commit: 62df7a39442902a71259568c13a4d496d5a514f4 Have you tested this? I get | U-Boot SPL 2023.07-rc2-00170-g62df7a3944 (Jun 01 2023 - 18:58:50 +0200) | DDR version: dc2e84f0. | Trying to boot from MMC2 | | | U-Boot 2023.07-rc2-00170-g62df7a3944 (Jun 01 2023 - 18:58:50 +0200) | | CPU: rv64imafdc_zba_zbb | Model: StarFive VisionFive 2 v1.3B | DRAM: 8 GiB | initcall sequence 00000000fffe0260 failed at call 00000000402160ec (err=-19) | ### ERROR ### Please RESET the board ### on that base rev already! My compiler is gcc (SUSE Linux) 13.0.1 20230421 (prerelease) [revision f980561c60b0446cc427595198d7f3f4f90e0924], FWIW. OpenSBI is 1.2 A simple switch back to an older branch (based on 6a11fdf0536e02ac) produces a working U-Boot again. Am I missing something? Torsten
On 2023/6/2 1:44, Torsten Duwe wrote: > On Thu, 25 May 2023 17:36:26 +0800 > Yanhong Wang <yanhong.wang@starfivetech.com> wrote: > [...] >> >> base-commit: 62df7a39442902a71259568c13a4d496d5a514f4 > > Have you tested this? > I also got the following error, which was caused by the recent submission [commit ID: 55171aedda88d12666e2a1bbc661dea1bec65337]. The modifications in this submission '! (gd->flags & GD_FLG_RELOC)' [in drivers/core/root.c] causes this issue, I have emailed the author of this submission for more information. I commented this modification when I was testing. The patch link: https://patchwork.ozlabs.org/project/uboot/patch/20230504225101.2366414-2-sjg@chromium.org/ > I get > > | U-Boot SPL 2023.07-rc2-00170-g62df7a3944 (Jun 01 2023 - 18:58:50 +0200) > | DDR version: dc2e84f0. > | Trying to boot from MMC2 > | > | > | U-Boot 2023.07-rc2-00170-g62df7a3944 (Jun 01 2023 - 18:58:50 +0200) > | > | CPU: rv64imafdc_zba_zbb > | Model: StarFive VisionFive 2 v1.3B > | DRAM: 8 GiB > | initcall sequence 00000000fffe0260 failed at call 00000000402160ec (err=-19) > | ### ERROR ### Please RESET the board ### > > on that base rev already! > My compiler is gcc (SUSE Linux) 13.0.1 20230421 (prerelease) > [revision f980561c60b0446cc427595198d7f3f4f90e0924], FWIW. > OpenSBI is 1.2 > > A simple switch back to an older branch (based on 6a11fdf0536e02ac) > produces a working U-Boot again. > > Am I missing something? > > Torsten