From: Andreas Schwab <schwab@suse.de>
To: Karsten Merker <merker@debian.org>
Cc: "Palmer Dabbelt" <palmer@sifive.com>,
"Anup Patel" <anup@brainfault.org>,
"Anup Patel" <Anup.Patel@wdc.com>,
"Atish Patra" <Atish.Patra@wdc.com>,
"Lukas Auer" <lukas.auer@aisec.fraunhofer.de>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Troy Benjegerdes" <troy.benjegerdes@sifive.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"Bin Meng" <bmeng.cn@gmail.com>,
"Björn Töpel" <bjorn.topel@gmail.com>
Subject: Re: 5.2-rc1 boot on Unleashed
Date: Mon, 03 Jun 2019 12:49:14 +0200 [thread overview]
Message-ID: <mvmwoi37xlh.fsf@suse.de> (raw)
In-Reply-To: <20190529185951.5rsoozymr32xychb@excalibur.cnev.de> (Karsten Merker's message of "Wed, 29 May 2019 20:59:51 +0200")
On Mai 29 2019, Karsten Merker <merker@debian.org> wrote:
> Mainline U-Boot already uses the distro bootcmd environment for
> the qemu "virt" machine and it works well.
The distro_bootcmd doesn't work for the sifive platform yet because it
doesn't set the correct MAC address for booting.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-06-03 10:49 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 23:31 5.2-rc1 boot on Unleashed Atish Patra
2019-05-21 9:40 ` Andreas Schwab
2019-05-21 18:14 ` Atish Patra
2019-05-22 7:31 ` Andreas Schwab
2019-05-22 8:40 ` Andreas Schwab
2019-05-22 9:58 ` Andreas Schwab
2019-05-22 21:13 ` Paul Walmsley
2019-05-21 17:47 ` Kevin Hilman
2019-05-21 18:18 ` Atish Patra
2019-05-23 9:42 ` Andreas Schwab
2019-05-22 4:42 ` Sagar Kadam
2019-05-22 9:51 ` Atish Patra
2019-05-22 16:42 ` Paul Walmsley
2019-05-22 17:38 ` Atish Patra
2019-05-22 20:43 ` Paul Walmsley
2019-05-22 22:14 ` Troy Benjegerdes
2019-05-25 8:06 ` Anup Patel
2019-05-25 14:16 ` Troy Benjegerdes
2019-05-29 5:00 ` Anup Patel
2019-05-29 8:31 ` Andreas Schwab
2019-05-29 17:38 ` Troy Benjegerdes
2019-05-29 18:59 ` Karsten Merker
2019-05-30 17:00 ` Palmer Dabbelt
2019-06-03 10:49 ` Andreas Schwab [this message]
2019-06-03 14:44 ` Distro bootcmd: " Troy Benjegerdes
2019-06-03 17:02 ` [U-Boot] " Tom Rini
2019-06-03 19:17 ` Palmer Dabbelt
2019-06-03 19:32 ` Tom Rini
2019-06-03 19:47 ` Troy Benjegerdes
2019-05-24 0:23 ` Troy Benjegerdes
2019-05-24 3:59 ` Atish Patra
2019-05-24 14:46 ` Troy Benjegerdes
2019-05-24 15:35 ` Auer, Lukas
2019-05-24 16:01 ` Troy Benjegerdes
2019-05-24 17:40 ` Atish Patra
[not found] ` <CAF5mof3_PSwpsSMnjMALpfvmOPdeAgDLa2p6jp4y+Hmas83mbw@mail.gmail.com>
2019-05-24 21:34 ` Auer, Lukas
2019-05-25 3:49 ` Anup Patel
2019-05-25 16:23 ` Troy Benjegerdes
2019-05-25 18:09 ` Paul Walmsley
2019-05-25 18:40 ` Troy Benjegerdes
2019-05-27 12:21 ` Andreas Schwab
2019-05-27 16:51 ` Troy Benjegerdes
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=mvmwoi37xlh.fsf@suse.de \
--to=schwab@suse.de \
--cc=Anup.Patel@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=anup@brainfault.org \
--cc=bjorn.topel@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=lukas.auer@aisec.fraunhofer.de \
--cc=merker@debian.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=troy.benjegerdes@sifive.com \
/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 NNTP newsgroup(s).