All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/3] Dockerfile: Install riscv32 toolchain from kernel.org
Date: Fri, 27 Mar 2020 14:05:55 +0800	[thread overview]
Message-ID: <CAEUhbmUpugoJUE_zoD5JF=sSZvp7g3E72mUJPE=PJzUXs0vUFg@mail.gmail.com> (raw)
In-Reply-To: <20200327015959.GD5793@bill-the-cat>

Hi Tom,

On Fri, Mar 27, 2020 at 10:00 AM Tom Rini <trini@konsulko.com> wrote:
>
> On Fri, Mar 27, 2020 at 09:57:47AM +0800, Bin Meng wrote:
> > Hi Tom,
> >
> > On Fri, Mar 27, 2020 at 12:14 AM Tom Rini <trini@konsulko.com> wrote:
> > >
> > > On Thu, Mar 26, 2020 at 09:04:52AM -0700, Bin Meng wrote:
> > >
> > > > This is required to build GRUB UEFI target for RISC-V 32-bit.
> > > >
> > > > Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
> > >
> > > Since we can use the 64bit toolchain for 32bit U-Boot, can we not pass
> > > GRUB the right flags to use the same toolchain?  Thanks!
> >
> > The 32-bit GRUB won't build with the 64-bit toolchain as of the
> > grub-2.04 branch we are using.
>
> Is that something that upstream has fixed or will fix / can be fixed and
> we can bump the tag we're using for?

I tried the latest upstream GRUB, and it still cannot be built using
riscv64 toolchain from kernel.org.

Regards,
Bin

  reply	other threads:[~2020-03-27  6:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 16:04 [PATCH 1/3] Dockerfile: Install riscv32 toolchain from kernel.org Bin Meng
2020-03-26 16:04 ` [PATCH 2/3] Dockerfile: Build GRUB UEFI target for RISC-V 32-bit Bin Meng
2020-04-10 22:24   ` Tom Rini
2020-03-26 16:04 ` [PATCH 3/3] Dockerfile: Build QEMU " Bin Meng
2020-04-10 22:24   ` Tom Rini
2020-03-26 16:14 ` [PATCH 1/3] Dockerfile: Install riscv32 toolchain from kernel.org Tom Rini
2020-03-27  1:57   ` Bin Meng
2020-03-27  1:59     ` Tom Rini
2020-03-27  6:05       ` Bin Meng [this message]
2020-03-27 15:25         ` Tom Rini
2020-03-27 23:55           ` Bin Meng
2020-03-31 15:15             ` Tom Rini
2020-04-01  3:31               ` Bin Meng
2020-04-10 22:23 ` Tom Rini

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='CAEUhbmUpugoJUE_zoD5JF=sSZvp7g3E72mUJPE=PJzUXs0vUFg@mail.gmail.com' \
    --to=bmeng.cn@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.