From: Christoph Hellwig <hch@infradead.org>
To: Anup Patel <anup@brainfault.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Atish Patra <atish.patra@wdc.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
Anup Patel <Anup.Patel@wdc.com>, Andreas Schwab <schwab@suse.de>
Subject: Re: kernel after 5.0-rc2 may not boot using BBL
Date: Fri, 8 Feb 2019 01:13:05 -0800 [thread overview]
Message-ID: <20190208091305.GE16932@infradead.org> (raw)
In-Reply-To: <CAAhSdy3GZHn9k7VvcUkM4s2SpU7SjtW3HmWcHVD342arWHYZLw@mail.gmail.com>
On Fri, Feb 08, 2019 at 02:32:51PM +0530, Anup Patel wrote:
> It is a bug in BBL because it is not keeping sufficient gap between
> Linux kernel end and DTB. The change pointed by Atish actually
> reduced flat kernel binary size by almost 1MB.
And that is all great. But it breaks peoples few existing RISC-V
setups, which is the best way to frustate every single of the few
users out there. And that is best way to lose any interested in this
already hard to use mess.
> Here's my BBL pull request:
> https://github.com/riscv/riscv-pk/pull/144
And that isn't going to help anyone who doesn't want to update every
single fragile piece of crap involved in booting RISC-V every day..
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-02-08 9:13 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 [this message]
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
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=20190208091305.GE16932@infradead.org \
--to=hch@infradead.org \
--cc=Anup.Patel@wdc.com \
--cc=anup@brainfault.org \
--cc=atish.patra@wdc.com \
--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 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.