| Age | Commit message (Collapse) | Author |
|---|
|
Use the backend registry to manage installation routines for different
backends as well. This makes the process more generic and allows us
to move towards plug & play for backends (i.e. there should be no code
changes needed in the general MLIA code to add/support new backends).
Change-Id: Ib7c772ec52b2f4d857c2c9871e44dfff97e9d970
|
|
- Provide "pretty names" to print information for targets and backends.
- Use 'target_config' instead of 'target' if a target profile is
used.
- Fix minor issue in output regarding the output directory.
Change-Id: Ib38231f30b4d609a0d1e8f9c52b2fb547c69cb6a
|
|
- Use the target/backend registries to avoid hard-coded names.
- Cache target profiles to avoid re-loading them
Change-Id: I474b7c9ef23894e1d8a3ea06d13a37652054c62e
|
|
- Remove old backend configuration code
- Install backends into directory ~/.mlia
- Rename targets/backends in registry to make it consistent
across codebase.
Change-Id: I9c8b012fe863280f1c692940c0dcad3ef638aaae
|
|
- Rely on target and backend registry for support information
- Make above information less Ethos(TM)-U specific
Change-Id: I8dbfb84401016412a3d719a84eb592f21d79c46b
|
|
Change-Id: Ieeaa9188ea1e29e2ccaad7475d457bce71e3140d
|
|
- Move backend management/executor code into module backend_core
- Create separate module for each backend in "backend" module
- Move each backend into corresponding module
- Split Vela wrapper into several submodules
Change-Id: If01b6774aab6501951212541cc5d7f5aa7c97e95
|
