4 ms·
Exactly what I'm wondering since they've been working on this for quite some time and asked for feedback a long time ago. How do you sit on this until they are
by tw04 10y ago
Exactly what I'm wondering since they've been working on this for quite some time and asked for feedback a long time ago. How do you sit on this until they are this far along?
- dflock 10y agoThey've been getting this feedback - and apparently ignoring it - since February: > Cleaning up that is not enough, abstracting kernel API like kmalloc or i2c, or similar, is a no go. If the current drm infrastructure does not suit your need then you need to work on improving it to suit your need. You can not redevelop a whole drm layer inside your code and expect to upstream it. > Linux device driver are about sharing infrastructure and trying to expose it through common API to userspace. > So i strongly suggest that you start thinking on how to change the drm API to suit your need and to start discussions about those changes. If you need them then they will likely be usefull to others down the road. https://lists.freedesktop.org/archives/dri-devel/2016-February/100729.html https://lists.freedesktop.org/archives/dri-devel/2016-Februa...