|
Re: [PATCH v4 1/6] Additional requirements for H-extension
The phrase
"Platforms are allowed to operate only in little-endian mode"
literally means that
* some platforms may be little-endian only and
* others may provide and *use* further modes
which
The phrase
"Platforms are allowed to operate only in little-endian mode"
literally means that
* some platforms may be little-endian only and
* others may provide and *use* further modes
which
|
By
Heinrich Schuchardt
·
#1237
·
|
|
Re: [PATCH v3 1/6] Additional requirements for H-extension
Hello Anup,
do you have a link to the thread?
Best regards
Heinrich
Hello Anup,
do you have a link to the thread?
Best regards
Heinrich
|
By
Heinrich Schuchardt
·
#1236
·
|
|
Re: [PATCH v4 2/6] Update terminology and specification tables
Hi Greg,
All these links are in one place so can be easily updated once specs are ratified/approved.
We certainly can’t finalize RISC-V platform spec having links to draft specifications.
Hi Greg,
All these links are in one place so can be easily updated once specs are ratified/approved.
We certainly can’t finalize RISC-V platform spec having links to draft specifications.
|
By
Anup Patel
·
#1235
·
|
|
Re: [PATCH v4 2/6] Update terminology and specification tables
When I try some of the added links, I end up at "404" pages.
Many of these links are to revs of spec's that are current but only temporary - until superseded by a later rev.
Ultimately these links
When I try some of the added links, I end up at "404" pages.
Many of these links are to revs of spec's that are current but only temporary - until superseded by a later rev.
Ultimately these links
|
By
Greg Favor
·
#1234
·
|
|
Re: [PATCH v3 1/6] Additional requirements for H-extension
It now strikes me that requiring 2022-compliant platforms to hardware MBE to zero will result in future platform specs - that allow MBE to be writeable - to not be compatible with the 2022 platform
It now strikes me that requiring 2022-compliant platforms to hardware MBE to zero will result in future platform specs - that allow MBE to be writeable - to not be compatible with the 2022 platform
|
By
Greg Favor
·
#1233
·
|
|
[PATCH v4 6/6] Follow profile naming as-per latest RISC-V profiles spec
We should follow profile naming as-per latest RISC-V profiles
specification. Also, we should avoid explicit mentions of
"RV32xxx" and "RV64xxx" ISA strings.
Signed-off-by: Anup Patel
We should follow profile naming as-per latest RISC-V profiles
specification. Also, we should avoid explicit mentions of
"RV32xxx" and "RV64xxx" ISA strings.
Signed-off-by: Anup Patel
|
By
Anup Patel
·
#1232
·
|
|
[PATCH v4 5/6] Minor cosmetic changes in SBI section of OS/A-base platform
We don't need a table for required SBI extensions and UEFI interfaces
implemented by UEFI firmware.
Signed-off-by: Anup Patel <anup.patel@...>
---
riscv-platform-spec.adoc | 49
We don't need a table for required SBI extensions and UEFI interfaces
implemented by UEFI firmware.
Signed-off-by: Anup Patel <anup.patel@...>
---
riscv-platform-spec.adoc | 49
|
By
Anup Patel
·
#1231
·
|
|
[PATCH v4 4/6] Re-write the interrupts and timer section
We re-write the interrupts and timer section to align the
interrupts and timer table. We also add more fine grained
requirements for AIA.
Signed-off-by: Anup Patel <anup.patel@...>
---
Makefile
We re-write the interrupts and timer section to align the
interrupts and timer table. We also add more fine grained
requirements for AIA.
Signed-off-by: Anup Patel <anup.patel@...>
---
Makefile
|
By
Anup Patel
·
#1230
·
|
|
[PATCH v4 3/6] Move terminology and specifications tables to correct location
The terminology table should be at start and specification table
should be at the end. Also, specification table should be replaced
with bibliography reference list.
Signed-off-by: Anup Patel
The terminology table should be at start and specification table
should be at the end. Also, specification table should be replaced
with bibliography reference list.
Signed-off-by: Anup Patel
|
By
Anup Patel
·
#1229
·
|
|
[PATCH v4 2/6] Update terminology and specification tables
This patch updates terminology and specification table in
following ways:
1) Provide complete expansion of terms for APLIC and ACLINT
2) Add links to unprivileged and privileged specifications
3) Add
This patch updates terminology and specification table in
following ways:
1) Provide complete expansion of terms for APLIC and ACLINT
2) Add links to unprivileged and privileged specifications
3) Add
|
By
Anup Patel
·
#1228
·
|
|
[PATCH v4 1/6] Additional requirements for H-extension
To have a meaningful H-extension support, both OS/A-base and
OS/A-server platforms must comply with additional requirements
for H-extension.
Signed-off-by: Anup Patel <anup.patel@...>
---
To have a meaningful H-extension support, both OS/A-base and
OS/A-server platforms must comply with additional requirements
for H-extension.
Signed-off-by: Anup Patel <anup.patel@...>
---
|
By
Anup Patel
·
#1227
·
|
|
Re: [PATCH v3 5/6] Minor cosmetic changes in SBI section of OS/A-base platform
On 06/08/21, 1:21 PM, "Heinrich Schuchardt" <heinrich.schuchardt@...> wrote:
%s/is//
[Anup] Okay, will update.
An article is missing. I prefer the complete term over the
On 06/08/21, 1:21 PM, "Heinrich Schuchardt" <heinrich.schuchardt@...> wrote:
%s/is//
[Anup] Okay, will update.
An article is missing. I prefer the complete term over the
|
By
Anup Patel
·
#1226
·
|
|
Re: [PATCH v3 4/6] Re-write the interrupts and timer section
On 06/08/21, 1:17 PM, "Heinrich Schuchardt" <heinrich.schuchardt@...> wrote:
verb missing
verb missing
[Anup] Okay, will update.
Regards,
Anup
Best regards
On 06/08/21, 1:17 PM, "Heinrich Schuchardt" <heinrich.schuchardt@...> wrote:
verb missing
verb missing
[Anup] Okay, will update.
Regards,
Anup
Best regards
|
By
Anup Patel
·
#1225
·
|
|
Re: [PATCH v3 1/6] Additional requirements for H-extension
On 06/08/21, 1:14 PM, "tech-unixplatformspec@... on behalf of Heinrich Schuchardt" <tech-unixplatformspec@... on behalf of heinrich.schuchardt@...> wrote:
On 06/08/21, 1:14 PM, "tech-unixplatformspec@... on behalf of Heinrich Schuchardt" <tech-unixplatformspec@... on behalf of heinrich.schuchardt@...> wrote:
|
By
Anup Patel
·
#1224
·
|
|
Next Platform HSC Meeting on Mon Aug 9th 2021 8AM PST
Hi All,
The next platform HSC meeting is scheduled on Mon Aug 9th at 8AM PST.
Here are the details:
Agenda and minutes kept on the github
Hi All,
The next platform HSC meeting is scheduled on Mon Aug 9th at 8AM PST.
Here are the details:
Agenda and minutes kept on the github
|
By
Kumar Sankaran
·
#1223
·
|
|
fyi
https://www.cnx-software.com/2021/08/06/the-risc-v-platform-specification-aims-to-ensure-risc-v-hardware-and-software-compatibility/
--------
sent from a mobile device. please forgive any typos.
https://www.cnx-software.com/2021/08/06/the-risc-v-platform-specification-aims-to-ensure-risc-v-hardware-and-software-compatibility/
--------
sent from a mobile device. please forgive any typos.
|
By
mark
·
#1222
·
|
|
Re: [PATCH v3 5/6] Minor cosmetic changes in SBI section of OS/A-base platform
%s/is//
An article is missing. I prefer the complete term over the abbreviation:
%s/OS/The operating system/
%s/Platform specific/platform specific/
Best regards
Heinrich
%s/is//
An article is missing. I prefer the complete term over the abbreviation:
%s/OS/The operating system/
%s/Platform specific/platform specific/
Best regards
Heinrich
|
By
Heinrich Schuchardt
·
#1221
·
|
|
Re: [PATCH v3 4/6] Re-write the interrupts and timer section
verb missing
verb missing
Best regards
Heinrich
verb missing
verb missing
Best regards
Heinrich
|
By
Heinrich Schuchardt
·
#1220
·
|
|
Re: [PATCH v3 1/6] Additional requirements for H-extension
Please, add period at end of sentence.
According to the privileged architecture specification:
<cite>
If this feature is provided, after an illegal instruction trap, mtval will contain the shortest
Please, add period at end of sentence.
According to the privileged architecture specification:
<cite>
If this feature is provided, after an illegal instruction trap, mtval will contain the shortest
|
By
Heinrich Schuchardt
·
#1219
·
|
|
[PATCH v3 6/6] Follow profile naming as-per latest RISC-V profiles spec
We should follow profile naming as-per latest RISC-V profiles
specification. Also, we should avoid explicit mentions of
"RV32xxx" and "RV64xxx" ISA strings.
Signed-off-by: Anup Patel
We should follow profile naming as-per latest RISC-V profiles
specification. Also, we should avoid explicit mentions of
"RV32xxx" and "RV64xxx" ISA strings.
Signed-off-by: Anup Patel
|
By
Anup Patel
·
#1218
·
|