Home
last modified time | relevance | path

Searched hist:bb916eed (Results 1 – 5 of 5) sorted by relevance

/dragonfly/sys/dev/drm/
H A Ddrm_dragonfly.cbb916eed Tue Dec 10 17:45:22 GMT 2019 François Tigeot <ftigeot@wolfpond.org> drm: Stop using an embedded struct drm_device in driver softcs

* All drm drivers use a struct drm_device record but are free to
allocate it by themselves in different ways or let the generic
drm subsystem code do it.

* This drm_device record can even be part of another data structure,
dynamically or statically allocated.

* We cannot just assume the length of a drm_device structure in the
softc memory block will be enough to store all driver private data.

* Make the drm softc the equivalent of a void* pointer and let the
upstream code behave as expected on Linux
H A Ddrm_drv.cbb916eed Tue Dec 10 17:45:22 GMT 2019 François Tigeot <ftigeot@wolfpond.org> drm: Stop using an embedded struct drm_device in driver softcs

* All drm drivers use a struct drm_device record but are free to
allocate it by themselves in different ways or let the generic
drm subsystem code do it.

* This drm_device record can even be part of another data structure,
dynamically or statically allocated.

* We cannot just assume the length of a drm_device structure in the
softc memory block will be enough to store all driver private data.

* Make the drm softc the equivalent of a void* pointer and let the
upstream code behave as expected on Linux
/dragonfly/sys/dev/drm/i915/
H A Di915_drv.cbb916eed Tue Dec 10 17:45:22 GMT 2019 François Tigeot <ftigeot@wolfpond.org> drm: Stop using an embedded struct drm_device in driver softcs

* All drm drivers use a struct drm_device record but are free to
allocate it by themselves in different ways or let the generic
drm subsystem code do it.

* This drm_device record can even be part of another data structure,
dynamically or statically allocated.

* We cannot just assume the length of a drm_device structure in the
softc memory block will be enough to store all driver private data.

* Make the drm softc the equivalent of a void* pointer and let the
upstream code behave as expected on Linux
/dragonfly/sys/dev/drm/include/drm/
H A DdrmP.hbb916eed Tue Dec 10 17:45:22 GMT 2019 François Tigeot <ftigeot@wolfpond.org> drm: Stop using an embedded struct drm_device in driver softcs

* All drm drivers use a struct drm_device record but are free to
allocate it by themselves in different ways or let the generic
drm subsystem code do it.

* This drm_device record can even be part of another data structure,
dynamically or statically allocated.

* We cannot just assume the length of a drm_device structure in the
softc memory block will be enough to store all driver private data.

* Make the drm softc the equivalent of a void* pointer and let the
upstream code behave as expected on Linux
/dragonfly/sys/dev/drm/radeon/
H A Dradeon_drv.cbb916eed Tue Dec 10 17:45:22 GMT 2019 François Tigeot <ftigeot@wolfpond.org> drm: Stop using an embedded struct drm_device in driver softcs

* All drm drivers use a struct drm_device record but are free to
allocate it by themselves in different ways or let the generic
drm subsystem code do it.

* This drm_device record can even be part of another data structure,
dynamically or statically allocated.

* We cannot just assume the length of a drm_device structure in the
softc memory block will be enough to store all driver private data.

* Make the drm softc the equivalent of a void* pointer and let the
upstream code behave as expected on Linux