Date: Wed, 25 Sep 2019 22:30:28 +1200 From: mko <me@mko.io> To: John-Mark Gurney <jmg@funkthat.com> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@FreeBSD.org> Subject: Re: RockPro64 booting w/ u-boot v2019-rc3 Message-ID: <D27B4CCA-3E30-4212-A973-12DB52A8FCDE@mko.io> In-Reply-To: <20190924221308.GX96402@funkthat.com> References: <20190916064640.GN96402@funkthat.com> <20190924221308.GX96402@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi John, Thanks for the the additional information for building the uboot. Do you = think all the fixes will available in the next u-boot release, so I can = use the upstream u-boot to boot freebsd on RK3399? mko=20 > On 25/09/2019, at 10:13 AM, John-Mark Gurney <jmg@funkthat.com> wrote: >=20 > John-Mark Gurney wrote this message on Sun, Sep 15, 2019 at 23:46 = -0700: >> I may have forgotten to include some steps. After building, I >> installed the parts via: >> dd if=3Didbloader.img of=3D/dev/disk4 oseek=3D64 bs=3D512 >=20 > It turns out that I did forget some steps. It appears that the file > idbloader.img was built from git checkout > 87d5b225585f341ea8e926a2c26fb72585fc9d0c, and NOT the [missing from > my email] branch v2019.10-rc3 like I had thought. It does appear that > idbloader.img is built by cat'ing tpl/u-boot-tpl.img and > spl/u-boot-spl.bin together, but I have not tried it from the > rc3 branch to verify. >=20 > --=20 > John-Mark Gurney Voice: +1 415 225 5579 >=20 > "All that I will do, has been done, All that I have, has not." > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D27B4CCA-3E30-4212-A973-12DB52A8FCDE>