On Mon, Sep 16, 2019 at 05:37:51AM +0000, Chang, Abner (HPS SW/FW Technologist)
wrote:
> > -----Original Message-----
> > From: Leif Lindholm [mailto:[email protected]]
> > Sent: Thursday, September 5, 2019 10:28 PM
> > To: [email protected]; Chang, Abner (HPS SW/FW Technologist)
> > <[email protected]>
> > Subject: Re: [edk2-devel] [edk2-staging/RISC-V-V2 PATCH v1 07/22]:
> > MdePkg/BaseIoLibIntrinsic: RISC-V I/O intrinsic functions.
> >
> > On Wed, Sep 04, 2019 at 06:43:02PM +0800, Abner Chang wrote:
> > > RISC-V MMIO library instance. RISC-V only supports memory map I/O.
> > > However the first implementation of RISC-V EDK2 port uses PC/AT as the
> > > RISC-V platform spec. We have to keep the I/O functions as the temporary
> > solution.
> >
> > Can you expand on the I/O port situation?
> > Since the architecture doesn't support it, what do these functions do?
> >
> > For the pure MMIO ops using compliant C, we really don't need yet another
> > implementation pretending it's architecture specific. We should just have a
> > single IoLibMmio.c and an IoLibMmioNonCompliant.c if the x86 folks want to
> > keep their current one.
>
> Hmm. That was for the old RISC-V PC/AT QEUM version back to 2016. We
> pulled in some X86 peripherals to build up RISC-V PC/AT like
> platform . will remove this.
Excellent, thanks.
/
Leif
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#47373): https://edk2.groups.io/g/devel/message/47373
Mute This Topic: https://groups.io/mt/33137129/21656
Group Owner: [email protected]
Unsubscribe: https://edk2.groups.io/g/devel/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
