mirror of
https://github.com/wfjm/w11.git
synced 2026-04-25 03:45:42 +00:00
build flow now Vivado 2022.1 ready [skip ci]
This commit is contained in:
@@ -28,8 +28,9 @@ The full set of tests is only run for tagged releases.
|
||||
### Summary
|
||||
- cleanup tbrun setup, drop nexys4 and add nexys4d ([see blog](https://wfjm.github.io/blogs/w11/2019-07-27-nexys4-obituary.html))
|
||||
- add ostest support for rsx11m-31_rk, rsx11m-40_rk and rsx11mp-30_rp oskits
|
||||
- Doxygen support now for V1.9.4 and without discontinued Tcl
|
||||
- all actively used commands have now a man page
|
||||
- Doxygen support now for V1.9.4; remove discontinued Tcl support
|
||||
- build flow Vivado 2022.1 ready; handle synth 8-3331 -> 8-7129 transition)
|
||||
### New features
|
||||
### Changes
|
||||
- tools changes
|
||||
|
||||
@@ -32,7 +32,7 @@ The maintainer of the [simh/simh](https://github.com/simh/simh) GitHub project,
|
||||
[Mark Pizzolato](https://github.com/markpizz), decided on May 15th, 2022 with
|
||||
commit [ce2adce6](https://github.com/simh/simh/commit/ce2adce6) to change the
|
||||
license of the repository. The bottom line of the change is, that some files
|
||||
are declared proprietary and this repository is not longer a
|
||||
are declared proprietary and this repository is no longer a
|
||||
[FOSS](https://en.wikipedia.org/wiki/Free_and_open-source_software) project,
|
||||
see also issue [#1163](https://github.com/simh/simh/issues/1163).
|
||||
This triggered massive reactions, see issue
|
||||
@@ -40,7 +40,7 @@ This triggered massive reactions, see issue
|
||||
SimH mailing list [simh@groups.io](https://groups.io/g/simh), starting with post
|
||||
[New license?](https://groups.io/g/simh/topic/new_license/91108560).
|
||||
See especially Bob Supnik's post
|
||||
[SimH licensing and the state of the project](https://groups.io/g/simh/topic/simh_licensing_and_the_state/91173868)
|
||||
[SimH licensing and the state of the project](https://groups.io/g/simh/topic/simh_licensing_and_the_state/91173868).
|
||||
|
||||
Given that situation using version `v3.11-1` as described above is the
|
||||
only prudent option for the time being.
|
||||
|
||||
Reference in New Issue
Block a user