Skip to content

Adding proper support for RISC-V #315

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

Open
tact1m4n3 opened this issue Dec 15, 2024 · 0 comments
Open

Adding proper support for RISC-V #315

tact1m4n3 opened this issue Dec 15, 2024 · 0 comments

Comments

@tact1m4n3
Copy link
Collaborator

tact1m4n3 commented Dec 15, 2024

Just some thoughts to improve the riscv support in microzig. 😀 Maybe we could discuss this further in this issue.

Problem:

Currently, it seems that for each riscv chip we are creating a new cpu implementation from scratch which creates a lot of code duplication.

Solution:

All riscv cpus should depend on a generic riscv implementation so that csrs, interrupt related functions, generic vector table, etc don't have to be duplicated. Each cpu module can select what it wants from this generic implementation and reexport the definitions (if they are aplicable for that cpu).

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

1 participant