This provides an option to pytest to look at a particular folder (e.g.
`/lib/firmware`) for all required test firmware.

see commit diff for comment with explanation

Resolve "Package firmware for distribution"

Closes #36

See merge request be-cem-edl/common/mockturtle!27

Resolve "Migrate CI software build and publishing to new common pipeline"

Closes #35

See merge request be-cem-edl/common/mockturtle!26

Resolve "Conflict between multiple sync users on same HMQ"

Closes #34

See merge request be-cem-edl/common/mockturtle!25

This modification makes sure that all device handles (to the same MT
devid) are opened at the start of the test and kept open for the
duration of the test. This allows catching race conditions between the
read/write pointers in the HMQ buffers (because the read pointer is
initialised to the value of the write pointer when the device handle is
first acquired, so the sooner we open it, the more such errors we will
detect).

Resolve "Fix broken pytest CI for releases"

Closes #32

See merge request be-cem-edl/common/mockturtle!24

Resolve "Make v4.2.0 release"

Closes #30

See merge request be-cem-edl/common/mockturtle!23

This makes the "code" more readable, target-specific variables can be
confused as additional targets (they are not).

This new target will create two compressed tarballs, one containing the
kernel modules and another one containing software libraries and tools.

Also update gitlab CI to use this new target to pulbish the software
and use it during testing on real hardware.

Resolve "SW reset signals for mock-turtle CPUs"

Closes #31

See merge request be-cem-edl/common/mockturtle!22

There is one reset signal per CPU. Their behavior is the same as the reset bit in the control registers (it resets the corresponding CPU while leaving the RAM intact).

Resolve "Document external RMQ interface"

Closes #28

See merge request be-cem-edl/common/mockturtle!21

Resolve "Run pytests in CI"

Closes #29

See merge request be-cem-edl/common/mockturtle!20

Resolve "Remove driver code to handle sequence numbers"

Closes #27 and #24

See merge request be-cem-edl/common/mockturtle!19

The deprecation of the old interface was already announced in 3.10
kernels:

https://elixir.bootlin.com/linux/v3.10.108/source/include/linux/tty_driver.h#L343

The main issue here is that SVEC base occupies the first 0x4000 of the
address space (as opposed to the 0x2000 for the SPEC base).

This was overlooked when the SVEC demo was updated.

Furthermore, this creates the need for having two separate top-level
drivers (others ways exist of course but this is the simplest).

`seq` is now available to user applications

`sync_id` is defined internally as a unique ID per HMQ+CPU combo. User
applications do not need to define this anymore before sending a sync
message.

Merge branch '26-rmq-tx-interface-erroneously-fetches-next-data-from-out-slot-when-client-is-not-ready' into 'master'

Resolve "RMQ TX interface erroneously fetches next data from out slot when client is not ready"

Closes #26

See merge request be-cem-edl/common/mockturtle!18