From: Palmer Dabbelt <palmer@sifive.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: anup@brainfault.org, Anup.Patel@wdc.com,
Christoph Hellwig <hch@infradead.org>,
atish.patra@wdc.com, schwab@suse.de,
linux-riscv@lists.infradead.org
Subject: Re: kernel after 5.0-rc2 may not boot using BBL
Date: Mon, 11 Feb 2019 11:54:55 -0800 (PST) [thread overview]
Message-ID: <mhng-5eccb799-c5da-4bfe-ac1f-b8d0aaa5b1fc@palmer-si-x1c4> (raw)
In-Reply-To: <20190211082506.GA13103@infradead.org>
On Mon, 11 Feb 2019 00:25:06 PST (-0800), Christoph Hellwig wrote:
> On Sat, Feb 09, 2019 at 09:00:27AM +0530, Anup Patel wrote:
>> IMHO, best solution would be to use mature open-source bootloader as
>> payload (i.e. U-Boot or similar) and always boot Linux from bootloader. Using
>> Linux as BBL/OpenSBI payload can still continue to exist but it can be more
>> of a developer usage.
>
> Yes, that is a good long term plan. But in the meantime we should not
> gratiously break the precious setups people got working..
I agree. I don't think anyone wants to move away from BBL more than I do, and
while the OpenSBI+u-boot stuff is progressing well we can't just instantly
deprecate every other boot flow -- particularly not the one that I use :).
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2019-02-11 19:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 6:08 kernel after 5.0-rc2 may not boot using BBL Atish Patra
2019-02-08 8:32 ` Christoph Hellwig
2019-02-08 9:02 ` Anup Patel
2019-02-08 9:13 ` Christoph Hellwig
2019-02-08 9:17 ` Anup Patel
2019-02-08 17:28 ` Palmer Dabbelt
2019-02-09 3:30 ` Anup Patel
2019-02-11 8:25 ` Christoph Hellwig
2019-02-11 8:45 ` Anup Patel
2019-02-12 1:24 ` Michael Clark
2019-02-13 21:00 ` Palmer Dabbelt
2019-02-11 19:54 ` Palmer Dabbelt [this message]
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=mhng-5eccb799-c5da-4bfe-ac1f-b8d0aaa5b1fc@palmer-si-x1c4 \
--to=palmer@sifive.com \
--cc=Anup.Patel@wdc.com \
--cc=anup@brainfault.org \
--cc=atish.patra@wdc.com \
--cc=hch@infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=schwab@suse.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 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).