[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b10e777c-1511-519b-20bb-a682a6119132@MichaelKloos.com>
Date: Thu, 10 Mar 2022 08:37:27 -0500
From: "Michael T. Kloos" <Michael@...haelKloos.com>
To: Palmer Dabbelt <palmer@...belt.com>,
Christoph Hellwig <hch@...radead.org>,
Arnd Bergmann <arnd@...db.de>
Cc: Paul Walmsley <paul.walmsley@...ive.com>, aou@...s.berkeley.edu,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] riscv: Work to remove kernel dependence on the
M-extension
Is there something I can do that would help alleviate your concerns or
apprehension?
On 3/10/2022 8:22 AM, Michael T. Kloos wrote:
> Some other thoughts:
> It sounds like I am not the first person to want this feature and I
> probably won't be the last. I created the change for my own reasons, the
> same as any other contributor. I think we all know that I can not pull
> out some chart and say, "This many people want this and here is why." I
> live in central Ohio and have been doing this as a hobby. I don't even
> know anyone else who knows about systems and operating system development.
> If the justification that you are looking for is that I as some
> hypothetical developer at a major tech company is about to release a new
> RISC-V chip without M support but we want it to run Linux, I can not
> provide that answer. It sounds a bit like some software or hardware,
> chicken or the egg anyway. Trying to maintain my own fork if people
> start contributing patches with incompatible assembly scares me.
> Michael
Powered by blists - more mailing lists