From 63e63afed27a910dec39b2ed37604c2ced2eba83 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Fri, 8 Apr 2022 19:47:21 +0100 Subject: [PATCH] whoops markdown formatting of migen compat layer not quite right --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 6292843..aac1e0c 100644 --- a/README.md +++ b/README.md @@ -109,9 +109,10 @@ provides a comprehensive Migen compatibility layer! An existing Migen design can be synthesized and simulated with nMigen in three steps: 1. Replace all `from migen import <...>` statements with `from - nmigen.compat import <...>`. 2. Replace every explicit mention - of the default `sys` clock domain with the new default `sync` clock - domain. E.g. `ClockSignal("sys")` is changed to `ClockSignal("sync")`. + nmigen.compat import <...>`. + 2. Replace every explicit mention of the default `sys` clock domain + with the new default `sync` clock domain. E.g. `ClockSignal("sys")` + is changed to `ClockSignal("sync")`. 3. Migrate from Migen build/platform system to nMigen build/platform system. nMigen does not provide a build/platform compatibility layer because both the board definition files and the platform abstraction -- 2.30.2