aa651c7f83
In the past it happened several times that some changes in gem5 broke the SystemC coupling. Recently Accelera has changed the licence for SystemC from their own licence to Apache2.0, which is compatible with gem5. However, SystemC usually relies on the Boost library, but I was able to exchange the boost calls by c++11 alternatives. The recent SystemC version is placed into /ext and is integrated into gem5's build system. The goal is to integrate some SystemC tests for the CI in some following patches. Change-Id: I4b66ec806b5e3cffc1d7c85d3735ff4fa5b31fd0 Reviewed-on: https://gem5-review.googlesource.com/2240 Reviewed-by: Andreas Sandberg <andreas.sandberg@arm.com> Maintainer: Andreas Sandberg <andreas.sandberg@arm.com>
34 lines
1.0 KiB
Plaintext
34 lines
1.0 KiB
Plaintext
|
|
TLM-2.0 standard header files
|
|
=============================
|
|
|
|
Dir: include/
|
|
|
|
SubDirs: tlm_core/
|
|
tlm_1/
|
|
tlm_2/
|
|
tlm_utils/
|
|
|
|
Files: README.txt
|
|
tlm
|
|
tlm.h
|
|
|
|
|
|
Comments
|
|
========
|
|
|
|
To use the TLM-2.0 interoperability standard, a user should only include the tlm
|
|
or tlm.h header file. The same holds for the TLM-1.0 implementation that is
|
|
included as part of this kit; only include tlm or tlm.h. These header files
|
|
refer to all the header files within the tlm_core/ subdirectory, everything
|
|
within tlm or tlm.h is contained in the tlm namespace.
|
|
|
|
The tlm_utils subdirectory contains a set of additional definitions supported
|
|
by the TLM-2.0 standard, but which are not part of the interoperability
|
|
requirements. It contains ease-of-use and convenience implementations for the
|
|
interoperability standard. All objects defined in the tlm_utils directory are
|
|
contained in the tlm_util namespace.
|
|
|
|
See the README.txt files in the subdirectories for an explanation of the
|
|
internal organization of the header files.
|