From: Drew Fustini <drew@beagleboard.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] beaglev: update to new starfive linux and u-boot
Date: Wed, 9 Jun 2021 10:42:34 -0700 [thread overview]
Message-ID: <20210609174234.GA2234548@x1> (raw)
In-Reply-To: <CAOCHtYghkr-KNaQ3jyD3Z6xg-sn1f9kWZGNhbkWg4Mv=W-rk5g@mail.gmail.com>
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
next prev parent reply other threads:[~2021-06-09 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 6:38 [Buildroot] [PATCH 1/3] beaglev: update to new starfive linux and u-boot Drew Fustini
2021-06-09 6:38 ` [Buildroot] [PATCH 2/3] boot/beaglev-ddrinit: add LICENSE file Drew Fustini
2021-06-09 12:25 ` Bin Meng
2021-06-09 6:38 ` [Buildroot] [PATCH 3/3] boot/beaglev-secondboot: " Drew Fustini
2021-06-09 12:25 ` Bin Meng
2021-06-09 7:38 ` [Buildroot] [PATCH 1/3] beaglev: update to new starfive linux and u-boot Alistair Francis
2021-06-09 12:24 ` Bin Meng
2021-06-09 17:49 ` Drew Fustini
2021-06-09 15:08 ` Robert Nelson
2021-06-09 17:42 ` Drew Fustini [this message]
2021-07-13 19:20 ` Arnout Vandecappelle
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=20210609174234.GA2234548@x1 \
--to=drew@beagleboard.org \
--cc=buildroot@busybox.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).