Fork of the riscv crate to support vexriscv
Go to file
Sean Cross fd54453416 register: add vexriscv-specific registers
Vexriscv in its normal configuration has its own registers for things
such as machine interrupts and system interrupts.  Add wrappers for
these registers.

Signed-off-by: Sean Cross <sean@xobs.io>
2020-01-08 17:22:16 +08:00
.github A unified contributing experience. 2018-08-12 08:59:12 +02:00
bin bin: update name of object file 2019-12-28 18:29:06 +08:00
ci Enable gcc caching 2019-03-17 17:24:07 +03:00
src register: add vexriscv-specific registers 2020-01-08 17:22:16 +08:00
.gitattributes vexriscv: clone from riscv crate 2019-12-28 18:12:31 +08:00
.gitignore Implement asm functions 2019-01-23 01:29:54 +03:00
.travis.yml Add MSRV policy 2019-03-17 17:29:48 +03:00
CODE_OF_CONDUCT.md Rename RISCV to RISC-V 2019-03-28 18:31:57 +01:00
Cargo.toml cargo: remove `vexriscv` category 2019-12-28 18:14:52 +08:00
LICENSE.md vexriscv: clone from riscv crate 2019-12-28 18:12:31 +08:00
README.md vexriscv: clone from riscv crate 2019-12-28 18:12:31 +08:00
asm.S vexriscv: clone from riscv crate 2019-12-28 18:12:31 +08:00
assemble.ps1 bin: update name of object file 2019-12-28 18:29:06 +08:00
assemble.sh bin: update name of object file 2019-12-28 18:29:06 +08:00
build.rs Implement asm functions 2019-01-23 01:29:54 +03:00
check-blobs.sh Implement asm functions 2019-01-23 01:29:54 +03:00

README.md

crates.io crates.io Build Status

veriscv

Low level access to parts of the VexRiscv RISC-V processor

This project is derived from riscv, developed and maintained by the RISC-V team.

Documentation

License

Copyright 2020 Sean "xobs" Cross Copyright 2019 RISC-V team

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Code of Conduct

Contribution to this crate is organized under the terms of the Rust Code of Conduct, the maintainer of this crate, the RISC-V team, promises to intervene to uphold that code of conduct.