On Tue, Jun 18, 2019 at 8:56 AM Paul Walmsley <paul.walmsley@xxxxxxxxxx> wrote: > > On Mon, 17 Jun 2019, Alistair Francis wrote: > > > > The legacy M-mode U-boot handles the phy reset already, and I’ve been > > > able to load upstream S-mode uboot as a payload via TFTP, and then > > > load and boot a 4.19 kernel. > > > > > > It would be nice to get this all working with 5.x, however there are > > > still > > > several missing pieces to really have it work well. > > > > Let me know what is still missing/doesn't work and I can add it. At the > > moment the only known issue I know of is a missing SD card driver in U- > > Boot. > > The DT data has changed between the non-upstream data that people > developed against previously, vs. the DT data that just went upstream > here: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=72296bde4f4207566872ee355950a59cbc29f852 > > and > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c35f1b87fc595807ff15d2834d241f9771497205 > > So Upstream U-Boot is going to need several patches to get things working > again. Clock identifiers and Ethernet are two known areas. Done. I just send-out few patches to fix U-Boot SiFive Clock driver. The U-Boot SiFive Clock driver fix series can be found in riscv_unleashed_clk_sync_v1 branch of: https://github.com/avpatel/u-boot.git Users will also require OpenSBI DTB fix which can be found in sifive_unleashed_dtb_fix_v1 branch of: https://github.com/avpatel/opensbi.git With above fixes, we can now use same DTB for both U-Boot and Linux kernel (5.2-rc1). Although, users are free to pass a different DTB to Linux kernel via TFTP. I have tested SiFive serial and Cadance MACB ethernet on both U-Boot and Linux (5.2-rc1) Regards, Anup
