[Buildroot] [PATCH 1/3] beaglev: update to new starfive linux and u-boot

[Drew Fustini <drew@beagleboard.org>]

On Wed, Jun 09, 2021 at 10:08:55AM -0500, Robert Nelson wrote:
> On Wed, Jun 9, 2021 at 2:15 AM Drew Fustini <drew@beagleboard.org> wrote:
> >
> > Update the commit id for u-boot to include fixes from the starfive-tech
> > u-boot repository:
> >
> > 494e5ef7b807 jh7100: Enable full 2M L2 cache
> > 4571f5a4e1e4 vic7100: enable cache ways (L2 cache)
> > abb06422a5cd Remove fdt_high and initrd_high for Starfive
> > 93099a61c7b0 starfive: beaglev: Disable SIFIVE_CLINT and enable RISCV_TIMER
> > bfb5abac3d1f Revert "riscv: Enable the SiFive CLINT block driver in S-Mode(VIC7100 ONLY)"
> > 7b70e1d44ba9 defconfig: enable cache_wayenable for better performance
> > 7c585978616b configs: earlycon=sbi is deprecated
> >
> > The commit abb06422a5cd ("Remove fdt_high and initrd_high for Starfive")
> > has removed the need for buildroot to patch the fdt_addr_r address.
> >
> > Update linux from commit in the old 5.10 branch that Fedora image was
> > using to head of esmil_starlight branch [1] which is currently based
> > on 5.13-rc5 and represents the best kernel for this board [2].
> >
> > In addition, the updated kernel now has jh7100-beaglev-starlight.dtb so
> > buildroot no longer needs to copy the dtb from u-boot.
> >
> > [1] https://github.com/starfive-tech/linux/tree/esmil_starlight
> > [2] https://github.com/starfive-tech/linux/issues/26
> >
> > Signed-off-by: Drew Fustini <drew@beagleboard.org>
> > ---
> 
> 
> 
> > +# HEAD of the 5.13 branch (esmil_starlight)
> > +BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,starfive-tech,linux,83dba1f25dfc118cacec991c31a7a4cfa7405c89)/linux-83dba1f25dfc118cacec991c31a7a4cfa7405c89.tar.gz"
> > +BR2_LINUX_KERNEL_DEFCONFIG="starlight"
> > +BR2_LINUX_KERNEL_DTS_SUPPORT=y
> > +BR2_LINUX_KERNEL_INTREE_DTS_NAME="starfive/jh7100-beaglev-starlight"
> 
> Careful, @Drew Fustini this branch get's rebased on every kernel rc..
> Unless we manually create a tag, this sha will disappear next week..

I do not believe the commit [1] will ever go away as long as the repo
still exists. But to make sure, I created buildroot-20210609 tag [2] to
represent what is being used to indicate what is being used in upstream
buildroot.

-Drew

[1] https://github.com/starfive-tech/linux/commit/83dba1f25dfc118cacec991c31a7a4cfa7405c89
[2] https://github.com/starfive-tech/linux/releases/tag/buildroot-20210609