Jegeva
Jegeva
sorry for the slightly chaotic commit history, it's midnight here
just saw your answer, will take care of that tomorrow
see pull #97 for a data fix but not a fix of the underlying issue
The documentation states that there should be one : http://cloudbridge.cloudve.org/en/latest/api_docs/cloud/resources.html#cloudbridge.interfaces.resources.Instance, the abstract is here already : https://github.com/CloudVE/cloudbridge/blob/7882bda211eacc67c33b013c7906bf5860d0fcf6/cloudbridge/interfaces/resources.py#L587 It's just that the implementation is missing in GCP (maybe in others, i...
this is still alive and kicking with both latest versions from debian testing
@JonatanAntoni Hi Jonatan, Yes, i understand the non modular nature of the SVDs but : - the current state of 'things' is that the core peripherals should be in the...
@JonatanAntoni Jonatan, would it be possible to add something like Device/ARM/SVD_full with the complete SVDs in there ? - That shouldn't mess with vendors toolset while allowing people with less...
@JonatanAntoni Well it's a shame, maybe you have some machine parseable data that describe them in another format that SVD that i could use to publish these svds ? It...
@JonatanAntoni hummm... apparently ARM does maintain full fledged SVDs in the CMSDK (they are integrated in keil's BSP packs pointed by reinhard keil in #46 that is available publicly on...
i think it is relatively easy keep all sides happy either : Sol1: by having the cpu elements in the svd definition accepting a "derivedfrom style" pointing to an arm...