From: Paul Walmsley <paul.walmsley@sifive.com>
To: Atish Patra <Atish.Patra@wdc.com>
Cc: "linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"palmer@sifive.com" <palmer@sifive.com>,
"merker@debian.org" <merker@debian.org>
Subject: Re: [PATCH] riscv: modify the Image header to improve compatibility with the ARM64 header
Date: Sat, 14 Sep 2019 06:58:13 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1909140653070.10284@viisi.sifive.com> (raw)
In-Reply-To: <2e697e9c7966cf1a6cac415b6a247a8ba9f4de29.camel@wdc.com>
On Sat, 14 Sep 2019, Atish Patra wrote:
> Thanks for the quick fix. Is there a planned timeline when we can
> remove the deprecated magic ?
If Linus merges this patch, we should probably start the transition in the
bootloaders, QEMU, and user tools as quickly as possible. Probably the
key element in the timeline is when we remove support for the old 64-bit
magic number location in the kernel. I'm told that U-Boot and QEMU have
already issued releases with support for the v0.1 image header format, so
dropping the old magic number from the kernel is probably at least a few
years away. (This is to increase the likelihood that anyone using the old
software has had the chance to update them.)
> I was planning to send a U-boot header documentation patch to match
> Linux one anyways. Do you want me that to rebase based on this patch or
> are you planning to send a U-boot patch as well ?
Once v5.3 comes out, please go ahead.
- Paul
next prev parent reply other threads:[~2019-09-14 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-14 3:08 Paul Walmsley
2019-09-14 4:03 ` Atish Patra
2019-09-14 13:58 ` Paul Walmsley [this message]
2019-09-14 12:18 ` 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=alpine.DEB.2.21.9999.1909140653070.10284@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=Atish.Patra@wdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=merker@debian.org \
--cc=palmer@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
all inboxes | Powered by JetHome®