From: Conor Dooley <conor.dooley@microchip.com>
To: Frederik Haxel <haxel@fzi.de>
Cc: "Vitaly Wool" <vitaly.wool@konsulko.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Greentime Hu" <greentime.hu@sifive.com>,
"Andy Chiu" <andy.chiu@sifive.com>,
"Heiko Stuebner" <heiko@sntech.de>,
"Clément Léger" <cleger@rivosinc.com>,
"Sami Tolvanen" <samitolvanen@google.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Guo Ren" <guoren@kernel.org>, "Nam Cao" <namcaov@gmail.com>,
"Alexandre Ghiti" <alexghiti@rivosinc.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Anup Patel" <anup@brainfault.org>, "Baoquan He" <bhe@redhat.com>,
"Chen Jiahao" <chenjiahao16@huawei.com>,
"Björn Töpel" <bjorn@rivosinc.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Fix XIP boot and make XIP testable in QEMU
Date: Tue, 12 Dec 2023 13:22:46 +0000 [thread overview]
Message-ID: <20231212-customary-hardcover-e19462bf8e75@wendy> (raw)
In-Reply-To: <20231212130116.848530-1-haxel@fzi.de>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
On Tue, Dec 12, 2023 at 02:01:11PM +0100, Frederik Haxel wrote:
> XIP boot seems to be broken for some time now. A likely reason why no one
> seems to have noticed this is that XIP is more difficult to test, as it is
> currently not easily testable with QEMU.
>
> These patches fix the XIP boot and allow an XIP build without BUILTIN_DTB,
> which in turn makes it easier to test an image with the QEMU virt machine.
Are you actually using XIP in something other than QEMU? The fact that
some of the blamed fixes are over 18 months old suggests that you are
not actively using XIP builds of the mainline kernel.
There is a desire to remove XIP support (among other things), so if you
do actually have a use case for it, speak up.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-12-12 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 13:01 Frederik Haxel
2023-12-12 13:01 ` [PATCH 1/3] riscv: Make XIP bootable again Frederik Haxel
2023-12-12 13:01 ` [PATCH 2/3] riscv: Fixed wrong register in XIP_FIXUP_FLASH_OFFSET macro Frederik Haxel
2023-12-12 13:01 ` [PATCH 3/3] riscv: Allow disabling of BUILTIN_DTB for XIP Frederik Haxel
2023-12-12 13:22 ` Conor Dooley [this message]
[not found] ` <CAM4kBBKBC=ZSQPzAq5MFQvd1g9=Up_oRAK5CV74oJHt=SbcPqg@mail.gmail.com>
2023-12-12 15:14 ` [PATCH 0/3] Fix XIP boot and make XIP testable in QEMU Conor Dooley
2023-12-13 16:08 ` Palmer Dabbelt
2024-01-11 14:50 ` patchwork-bot+linux-riscv
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=20231212-customary-hardcover-e19462bf8e75@wendy \
--to=conor.dooley@microchip.com \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--cc=andy.chiu@sifive.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=bhe@redhat.com \
--cc=bjorn@rivosinc.com \
--cc=chenjiahao16@huawei.com \
--cc=cleger@rivosinc.com \
--cc=greentime.hu@sifive.com \
--cc=guoren@kernel.org \
--cc=haxel@fzi.de \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=namcaov@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samitolvanen@google.com \
--cc=vitaly.wool@konsulko.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®