[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210915074727.GB20024@lst.de>
Date: Wed, 15 Sep 2021 09:47:27 +0200
From: Christoph Hellwig <hch@....de>
To: guoren@...nel.org
Cc: anup.patel@....com, atish.patra@....com, palmerdabbelt@...gle.com,
christoph.muellner@...ll.eu, philipp.tomsich@...ll.eu, hch@....de,
liush@...winnertech.com, wefu@...hat.com, lazyparser@...il.com,
drew@...gleboard.org, linux-riscv@...ts.infradead.org,
linux-kernel@...r.kernel.org, taiten.peng@...onical.com,
aniket.ponkshe@...onical.com, heinrich.schuchardt@...onical.com,
gordan.markus@...onical.com, Guo Ren <guoren@...ux.alibaba.com>,
Arnd Bergmann <arnd@...db.de>, Chen-Yu Tsai <wens@...e.org>,
Maxime Ripard <maxime@...no.tech>,
Daniel Lustig <dlustig@...dia.com>,
Greg Favor <gfavor@...tanamicro.com>,
Andrea Mondelli <andrea.mondelli@...wei.com>,
Jonathan Behrens <behrensj@....edu>,
Xinhaoqu <xinhaoqu@...wei.com>,
Bill Huffman <huffman@...ence.com>,
Nick Kossifidis <mick@....forth.gr>,
Allen Baum <allen.baum@...erantotech.com>,
Josh Scheid <jscheid@...tanamicro.com>,
Richard Trauben <rtrauben@...il.com>
Subject: Re: [RFC PATCH V4 2/6] riscv: errata: pgtable: Add custom Svpbmt
supported for Allwinner D1
This is the wrong way around. We need to design around the PBMT
definitions. If we want to hack in support for completely broken SOCs
that intentionally violate the specification it should be done after
the fact, in a separate patch, using alternatives and clearly documenting
how broken these SOCs are.
Powered by blists - more mailing lists