luke
/
nextpnr
mirror of https://github.com/YosysHQ/nextpnr.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs/viaduct: don't reference nonexistent architecture in documentation

This commit is contained in:
Lunaphied 2026-08-02 19:58:30 +02:00
parent 90b9be4859
commit 4d994b81af
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/viaduct.md
View File

@ -123,7 +123,7 @@ struct ExampleArch : ViaductArch
### Adding a new uarch
The reference above provides an overview of what a Viaduct uarch must implement, it's also recommended to look at the `generic` and `okami` examples in `generic/viaduct`. New uarches should have their source contained in subfolders of `generic/viaduct`; and added to `VIADUCT_UARCHES` list in `generic/family.cmake`.
The reference above provides an overview of what a Viaduct uarch must implement, it's also recommended to look at the `generic` and `fabulous` examples in `generic/viaduct`. New uarches should have their source contained in subfolders of `generic/viaduct`; and added to `VIADUCT_UARCHES` list in `generic/family.cmake`.
Once you've implemented `ViaductAPI` and created the `ViaductArch` singleton, you should be able to run nextpnr with the arch by running `nextpnr-generic --uarch <name>`.