# Adding AMD v1000 BSP Support to balenaOS

**URL:** <https://forums.balena.io/t/adding-amd-v1000-bsp-support-to-balenaos/29756>\
**Category:** balenaOS\
**Created:** [September 3, 2019, 5:22pm UTC](https://forums.balena.io/t/adding-amd-v1000-bsp-support-to-balenaos/29756 "2019-09-03T17:22:40Z")\
**Posts on this page:** 1\
**Showing post:** 33

<div class="post-metadata">

**Author:** ![kasemq](https://avatars.discourse-cdn.com/v4/letter/k/7ba0ec/32.png) [@kasemq](https://forums.balena.io/u/kasemq)\
**Post date:** [September 27, 2019, 4:06pm UTC](https://forums.balena.io/t/adding-amd-v1000-bsp-support-to-balenaos/29756/33 "2019-09-27T16:06:32Z")

</div>

Ah, yeah I agree it is a bit odd.

For reference, here is the dependency chain that `meta-amd` adds that requires `x11`. Specifically `libdrm`:

```auto
ERROR: Nothing PROVIDES 'libxrender' (but /code/balena-amd/build/../layers/meta-amd/meta-amd-bsp/recipes-graphics/drm/libdrm_git.bb DEPENDS on or otherwise requires it)
libxrender was skipped: missing required distro feature 'x11' (not in DISTRO_FEATURES)
NOTE: Runtime target 'plymouth' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['plymouth', 'libdrm', 'libxrender']
ERROR: Required build target 'resin-image-flasher' has no buildable providers.
Missing or unbuildable dependency chain was: ['resin-image-flasher', 'resin-image', 'plymouth', 'libdrm', 'libxrender']

```

From what you are saying, I take it the recommendation is to find a way to remove `libdrm`?

## 

The `network-manager` and related issues seem to be because some of the bitbake files assume that `BASE_LIB` is `lib` and break if it is `lib64`

---

_[View the full topic](https://forums.balena.io/t/adding-amd-v1000-bsp-support-to-balenaos/29756)._