From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: Re: [edk2-devel] [edk2-staging/RiscV64QemuVirt PATCH V7 17/20] OvmfPkg/RiscVVirt: Add PciCpuIo2Dxe module
To: Sunil V L <sunilvl@ventanamicro.com>,devel@edk2.groups.io
From: dhaval@rivosinc.com
X-Originating-Location: Bengaluru, Karnataka, IN (171.76.82.41)
X-Originating-Platform: Linux Chrome 109
User-Agent: GROUPS.IO Web Poster
MIME-Version: 1.0
Date: Mon, 30 Jan 2023 02:12:58 -0800
References: <20230128191807.2080547-18-sunilvl@ventanamicro.com>
In-Reply-To: <20230128191807.2080547-18-sunilvl@ventanamicro.com>
Message-ID: <26729.1675073578100850032@groups.io>
Content-Type: multipart/alternative; boundary="6wWcRKThWphG23DiRFC3"

--6wWcRKThWphG23DiRFC3
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

What I see in the current implementation is:

* UEFICpuPkg implements gEfiCpuIo2ProtocolGuid which does not seem to be ge=
neric.
* ARMPkg implements it which seems similar to what RV needs.

Do we really expect this to be platform specific implementation and hence i=
t should be in respective platform folders? Neither x86/ARM seem to follow =
this model?

--6wWcRKThWphG23DiRFC3
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

What I see in the current implementation is:&nbsp;<br />
<ul>
<li>UEFICpuPkg implements gEfiCpuIo2ProtocolGuid which does not seem to be =
generic.</li>
<li>ARMPkg implements it which seems similar to what RV needs.</li>
</ul>
Do we really expect this to be platform specific implementation and hence i=
t should be in respective platform folders? Neither x86/ARM seem to follow =
this model?

--6wWcRKThWphG23DiRFC3--