From 8945407874c3031f13a5453598e9923268259698 Mon Sep 17 00:00:00 2001 From: Lunaphied Date: Sun, 2 Aug 2026 19:58:30 +0200 Subject: [PATCH] docs/viaduct: don't reference nonexistent architecture in documentation --- docs/viaduct.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/viaduct.md b/docs/viaduct.md index 88398a05..aa6332ce 100644 --- a/docs/viaduct.md +++ b/docs/viaduct.md @@ -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 `.