|
Another perspective on standards for architectures
If you have not seen these, they are a good
If you have not seen these, they are a good
|
By
Al Stone
·
#457
·
|
|
Re: [PATCH v2 0/2] Top-level makefile and cleanups
In general, these look like pretty good cleanups.
I agree with Atish in his reviews where some consistency in the spec
format would be nice. I'm not going to be pedantic about it, though,
as long as
In general, these look like pretty good cleanups.
I agree with Atish in his reviews where some consistency in the spec
format would be nice. I'm not going to be pedantic about it, though,
as long as
|
By
Al Stone
·
#456
·
|
|
Re: [PATCH v2 0/2] Top-level makefile and cleanups
By
Anup Patel
·
#455
·
|
|
Re: [PATCH v2 2/2] Clean-up entire document for consistency and better structure
By
Anup Patel
·
#454
·
|
|
Re: [PATCH v2 2/2] Clean-up entire document for consistency and better structure
I think the current version should be in the title page but in a next
line similar to platform spec.
I think we should move this to a change log section to be in compatible
with Platform
I think the current version should be in the title page but in a next
line similar to platform spec.
I think we should move this to a change log section to be in compatible
with Platform
|
By
atishp@...
·
#453
·
|
|
Re: [PATCH v2 0/2] Top-level makefile and cleanups
I think SBI specification should follow the same formatting as the
platform spec. Here are few differences in generated pdf.
1. First page should contain the title and a version in next line
I think SBI specification should follow the same formatting as the
platform spec. Here are few differences in generated pdf.
1. First page should contain the title and a version in next line
|
By
atishp@...
·
#452
·
|
|
Re: [PATCH v2 1/2] Add a makefile to build usable documents
Reviewed-by: Atish Patra <atish.patra@...>
--
Regards,
Atish
Reviewed-by: Atish Patra <atish.patra@...>
--
Regards,
Atish
|
By
atishp@...
·
#451
·
|
|
[PATCH v2 2/2] Clean-up entire document for consistency and better structure
This patch does following clean-ups in the entire asciidoc:
1. Ensure all lines don't extend beyond 80 characters
2. Have "Function: ", "Function Listing", and "Extension: "
sub-sections under each
This patch does following clean-ups in the entire asciidoc:
1. Ensure all lines don't extend beyond 80 characters
2. Have "Function: ", "Function Listing", and "Extension: "
sub-sections under each
|
By
Anup Patel
·
#450
·
|
|
[PATCH v2 1/2] Add a makefile to build usable documents
Add a simple makefile to build PDF and HTML documents using
asciidoctor. These documents (PDF/HTML) are easy to read and
can be shared/distributed.
Signed-off-by: Anup Patel <anup.patel@...>
---
Add a simple makefile to build PDF and HTML documents using
asciidoctor. These documents (PDF/HTML) are easy to read and
can be shared/distributed.
Signed-off-by: Anup Patel <anup.patel@...>
---
|
By
Anup Patel
·
#449
·
|
|
[PATCH v2 0/2] Top-level makefile and cleanups
This series adds top-level makefile and does cleanups to generate PDF and
HTML documents which are easy to read/navigate.
Changes since v1:
- Use RISC-V privilege style naming convention in PATCH2
This series adds top-level makefile and does cleanups to generate PDF and
HTML documents which are easy to read/navigate.
Changes since v1:
- Use RISC-V privilege style naming convention in PATCH2
|
By
Anup Patel
·
#448
·
|
|
Re: [PATCH 2/2] Clean-up entire document for consistency and better structure
Hi Jonathan,
I don't feel strongly about this convention. I just wanted to have uniform convention for CSRs and registers name in SBI spec.
Let me update this to use lowercase in next patch revision
Hi Jonathan,
I don't feel strongly about this convention. I just wanted to have uniform convention for CSRs and registers name in SBI spec.
Let me update this to use lowercase in next patch revision
|
By
Anup Patel
·
#447
·
|
|
Re: [PATCH 2/2] Clean-up entire document for consistency and better structure
Is there a reason that this convention was chosen? The privileged spec I think uses lowercase fixed-width text for CSRs.
Jonathan
Is there a reason that this convention was chosen? The privileged spec I think uses lowercase fixed-width text for CSRs.
Jonathan
|
By
Jonathan Behrens <behrensj@...>
·
#446
·
|
|
Re: [PATCH 0/2] Top-level makefile and cleanups
Hi All,
PFA, generated PDF after applying this series.
Regards,
Anup
Hi All,
PFA, generated PDF after applying this series.
Regards,
Anup
|
By
Anup Patel
·
#445
·
|
|
[PATCH 2/2] Clean-up entire document for consistency and better structure
This patch does following clean-ups in the entire asciidoc:
1. Ensure all lines don't extend beyond 80 characters
2. Have "Function: ", "Function Listing", and "Extension: "
sub-sections under each
This patch does following clean-ups in the entire asciidoc:
1. Ensure all lines don't extend beyond 80 characters
2. Have "Function: ", "Function Listing", and "Extension: "
sub-sections under each
|
By
Anup Patel
·
#444
·
|
|
[PATCH 1/2] Add a makefile to build usable documents
Add a simple makefile to build PDF and HTML documents using
asciidoctor. These documents (PDF/HTML) are easy to read and
can be shared/distributed.
Signed-off-by: Anup Patel <anup.patel@...>
---
Add a simple makefile to build PDF and HTML documents using
asciidoctor. These documents (PDF/HTML) are easy to read and
can be shared/distributed.
Signed-off-by: Anup Patel <anup.patel@...>
---
|
By
Anup Patel
·
#443
·
|
|
[PATCH 0/2] Top-level makefile and cleanups
This series adds top-level makefile and does cleanups to generate PDF and
HTML documents which are easy to read/navigate.
Anup Patel (2):
Add a makefile to build usable documents
Clean-up entire
This series adds top-level makefile and does cleanups to generate PDF and
HTML documents which are easy to read/navigate.
Anup Patel (2):
Add a makefile to build usable documents
Clean-up entire
|
By
Anup Patel
·
#442
·
|
|
Re: [PATCH v8] Add system reset extension
On 11/16/20 1:28 AM, Anup Patel wrote:
In an ideal world we could just reuse PSCI, but as we've discussed in recent meetings, the IP issues surrounding PSCI are unclear. So since
On 11/16/20 1:28 AM, Anup Patel wrote:
In an ideal world we could just reuse PSCI, but as we've discussed in recent meetings, the IP issues surrounding PSCI are unclear. So since
|
By
Paul Walmsley
·
#441
·
|
|
Re: [PATCH v8] Add system reset extension
LGTM.
Reviewed-by: Al Stone <ahs3@...>
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3@...
-----------------------------------
LGTM.
Reviewed-by: Al Stone <ahs3@...>
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3@...
-----------------------------------
|
By
Al Stone
·
#440
·
|
|
[PATCH v8] Add system reset extension
This patch adds SBI v0.2 compliant system reset extension. It defines
the sbi_system_reset function which does different things based on
reset_type parameter:
1. shutdown - Power-off the entire
This patch adds SBI v0.2 compliant system reset extension. It defines
the sbi_system_reset function which does different things based on
reset_type parameter:
1. shutdown - Power-off the entire
|
By
Anup Patel
·
#439
·
|
|
Re: [PATCH v7] Add system reset extension
By
Anup Patel
·
#438
·
|