https://redmine.replicant.us/https://redmine.replicant.us/favicon.ico?15984615062018-08-17T05:26:41ZReplicantReplicant - Feature #1794: Use free hardware composer for smdk4412 deviceshttps://redmine.replicant.us/issues/1794?journal_id=71152018-08-17T05:26:41ZJoonas Kylmälä
<ul><li><strong>Assignee</strong> set to <i>Joonas Kylmälä</i></li></ul><p>I'm researching whether drm_hwcomposer works on smdk4412 devices. Now I'm stuck for a while because there is no generic gralloc module that could be used with software renderers.</p> Replicant - Feature #1794: Use free hardware composer for smdk4412 deviceshttps://redmine.replicant.us/issues/1794?journal_id=71162018-08-17T18:21:52ZJoonas Kylmälä
<ul></ul><p>I'm trying to make now the default gralloc (<a class="external" href="https://android.googlesource.com/platform/hardware/libhardware/+/master/modules/gralloc/">https://android.googlesource.com/platform/hardware/libhardware/+/master/modules/gralloc/</a>) conform to the gralloc_handle_t struct defined here: <a class="external" href="https://cgit.freedesktop.org/mesa/drm/tree/android/gralloc_handle.h">https://cgit.freedesktop.org/mesa/drm/tree/android/gralloc_handle.h</a>. The gralloc_handle_t struct is expected by the drm_hwcomposer module's generic buffer importer code.</p>
<p>If that doesn't work out I could still try modifying the gbm_gralloc or minigbm modules.</p> Replicant - Feature #1794: Use free hardware composer for smdk4412 deviceshttps://redmine.replicant.us/issues/1794?journal_id=71192018-08-20T16:03:43ZJoonas Kylmälä
<ul></ul><p>So I got the drm_hwcomposer to be friends with the default gralloc but the DRM subsystem doesn't like ashmem allocated buffer handles so it didn't work out :/ I'm not quite sure about this but it feels like to me that the DRM subsystem expects a buffer handle that is actually pointing to some memory location in a DRM device like gpu0 or fb0 because when I tried to make a "dumb buffer" to the ashmem file descriptor with "drmIoctl(fd, DRM_IOCTL_MODE_CREATE_DUMB, &creq);" it said that it was not a permitted operation, i.e. there is no DRM_IOCTL_MODE_CREATE_DUMB on the "ashmem device".</p> Replicant - Feature #1794: Use free hardware composer for smdk4412 deviceshttps://redmine.replicant.us/issues/1794?journal_id=75632019-08-28T10:45:36ZAndrés Dandresdju@gmail.com
<ul><li><strong>Target version</strong> changed from <i>Replicant 6.0</i> to <i>Replicant 9.0</i></li></ul><p>All the work on hardware accelerated graphics will be done for Replicant 9.</p> Replicant - Feature #1794: Use free hardware composer for smdk4412 deviceshttps://redmine.replicant.us/issues/1794?journal_id=81442020-07-07T09:27:00Zdl luddllud@riseup.net
<ul><li><strong>Target version</strong> changed from <i>Replicant 9.0</i> to <i>replicant 10.0</i></li></ul> Replicant - Feature #1794: Use free hardware composer for smdk4412 deviceshttps://redmine.replicant.us/issues/1794?journal_id=82162020-07-23T14:15:12Zdl luddllud@riseup.net
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>Current dev branch of Replicant 10 is using drm-hwcomposer successfully, with only a few minor issues.</p> Replicant - Feature #1794: Use free hardware composer for smdk4412 deviceshttps://redmine.replicant.us/issues/1794?journal_id=82602020-08-24T22:10:25ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
<ul><li><strong>Target version</strong> changed from <i>replicant 10.0</i> to <i>Replicant 11.0 0001</i></li></ul><p>It will make it in the release so I moved it there.</p>