-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vermaete #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This version is now on Ubuntu 20.04 Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
When having other names that 'example', as used in the test, the indentation of the read and write functions in VHDL and SV was not optimal. Now, it looks for the '(' in the first line of the function to indent the arguments of the function. Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
E.g. spirit:AddressOffset and spirit:reset can now be specified in hex. If the Python built-in function 'int' has a value 0 for the second argument, it will discover the base of the first argument. Note this is not 100% the same as specified in the IP-XACT schema (simpleTypes.xsd). E.g. the magnitude (K, M, ...) is not supported. Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
There was a space after the '(' and before the ')' in only one function. The emacs formatter, see Makefile, was removed these. Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
In the VHDL code, these values are in decimal format. But it's useful to be able to read them in hex format too. Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Removed some not well working indentation in VHDL. Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Bring the golden reference of the tests in line with the previous commit. Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
It is now possible to use the argument --config and specify an ini config file. E.g ipxact2rst --srcFile register.xml --destDir=. --config default.ini Without the config file the behaviour is the same. For now, in the config file it is possible request not to generate the unused bits if there is a gap between two fields in a register. And it is possible to request that enums of fields of 1 bit long are generated. Default, there will be no enums generated if the field is only one bit width. The testing will test it without config file, with a default config file and with a config file where the values are none default. Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
It's shorter and cleaner code. Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Hex addresses just read a bit easier if it is going over registers. Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
These are generated by tools outside the scope of this project. And the date of creation is in it. So, every build will create a git modified result. Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
They are generated by running the test. But in a second degree. Therfor, they should not be part of the golden reference. Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
…rom object, can be safely removed from bases in python3 Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Added a config file for prospector. Ignore the PEP8 notes about the used naming style. Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
This reverts commit 72f1ff1. Reverted on request of the maintainer. Having the PDF and docx is usefull for users so see what they can expect as output.
Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Now the register description can be generated as Markdown. This makes a a bit easier to add register documention into e.g. github.com or gitlab. Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
And fixed some wrong cut-and-past characters from my previous commit. Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
trigger circleci
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
trying to trigger ci of #17