Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Informative E-Trace Spec file name #141

Open
markuslauterbach opened this issue Sep 4, 2024 · 1 comment
Open

Informative E-Trace Spec file name #141

markuslauterbach opened this issue Sep 4, 2024 · 1 comment

Comments

@markuslauterbach
Copy link

Hi,

the current PDF file name of the E-Trace Spec is "riscv-trace-spec.pdf". The problem with this name is that:

  • This name is not distinguishable from N-Trace.
  • This name is not aligned with the file names of the other trace specs.

My suggestion would be to rename it to "RISC-V-E-Trace.pdf" (to align it with RISC-V-N-Trace.pdf, RISC-V-Trace-Connectors.pdf, RISC-V-Trace-Control-Interface.pdf).

I vaguely remember that in the past there was the argument that there are fixed links in other places that link to riscv-trace-spec.pdf, and that this can not easily be changed. But where are these links?

On the GitHub page https://github.com/riscv-non-isa/riscv-trace-spec I can not find any "riscv-trace-spec.pdf" (any more?) that could be linked to.
Also, https://wiki.riscv.org/display/HOME/RISC-V+Technical+Specifications uses a Google drive link, which probably changes each time that we upload a new file version (or does it not?).

Thanks,
Markus

@bcstrongx
Copy link
Collaborator

I'd prefer if we keep the name riscv-trace-spec, but incorporate all of the trace specs within it. That way there is one comprehensive non-ISA spec that includes all components of RISC-V trace, including chapters on the interface, connectors, and each trace format, but without all the duplication (e.g., itype definitions) that is currently required in the separate specs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants