Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.31 as permitted sender) client-ip=23.128.96.31;
Date:   Tue, 12 Dec 2023 15:14:54 +0000
From:   Conor Dooley <conor@kernel.org>
To:     Vitaly Wool <vitaly.wool@konsulko.com>
Cc:     Conor Dooley <Conor.Dooley@microchip.com>,
        Albert Ou <aou@eecs.berkeley.edu>,
        Alexandre Ghiti <alexghiti@rivosinc.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Andy Chiu <andy.chiu@sifive.com>,
        Anup Patel <anup@brainfault.org>, Baoquan He <bhe@redhat.com>,
        =?iso-8859-1?Q?Bj=F6rn_T=F6pel?= <bjorn@rivosinc.com>,
        Chen Jiahao <chenjiahao16@huawei.com>,
        =?iso-8859-1?Q?Cl=E9ment_L=E9ger?= <cleger@rivosinc.com>,
        Frederik Haxel <haxel@fzi.de>,
        Greentime Hu <greentime.hu@sifive.com>,
        Guo Ren <guoren@kernel.org>, Heiko Stuebner <heiko@sntech.de>,
        Masahiro Yamada <masahiroy@kernel.org>,
        Nam Cao <namcaov@gmail.com>,
        Palmer Dabbelt <palmer@dabbelt.com>,
        Paul Walmsley <paul.walmsley@sifive.com>,
        Sami Tolvanen <samitolvanen@google.com>,
        linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH 0/3] Fix XIP boot and make XIP testable in QEMU
Message-ID: <20231212-crabmeat-flatness-3c0d02966551@spud>
References: <20231212130116.848530-1-haxel@fzi.de>
 <20231212-customary-hardcover-e19462bf8e75@wendy>
 <CAM4kBBKBC=ZSQPzAq5MFQvd1g9=Up_oRAK5CV74oJHt=SbcPqg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="+0u/nDWT3CkbhlUL"
Content-Disposition: inline
In-Reply-To: <CAM4kBBKBC=ZSQPzAq5MFQvd1g9=Up_oRAK5CV74oJHt=SbcPqg@mail.gmail.com>
Precedence: bulk


--+0u/nDWT3CkbhlUL
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


Firstly, no html mails, they're rejected by the lists and break people's
mail flows.

On Tue, Dec 12, 2023 at 03:16:13PM +0100, Vitaly Wool wrote:
> tis 12 dec. 2023 kl. 14:23 skrev Conor Dooley <conor.dooley@microchip.com=
<mailto:conor.dooley@microchip.com>>:
> > 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 mac=
hine.
> >=20
> >=20
> > 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.
>=20
> Yes, we surely do, on K210 for instance. It=E2=80=99s using an older kern=
el and

The k210 and nommu are on the block for removal too :)
Is your use case for either the k210 or XIP something other than
"ooh this works"?=20

> I haven=E2=80=99t checked the mainline status for a while

I figured that when the request I sent asking if you could test XIP was
ignored. We've been 50-50 on whether it has been broken since Alex put
the dtb in the fixmap ~9 months ago.

> but it is likely that I will come up with some XIP updates
> before Christmas.

May I ask what you intend updating?

Cheers,
Conor.

--+0u/nDWT3CkbhlUL
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZXh47QAKCRB4tDGHoIJi
0iegAP9vWnOsipXucsygK4bN5Fqo+iSWJF0osyBy+ir9UgSb2wD+Nd9s1gKWU8L2
pYyXJfR4gVj/PQI7ZKedSn3V3zOz5gM=
=xLOI
-----END PGP SIGNATURE-----

--+0u/nDWT3CkbhlUL--