search for: dithering_mod

[PATCH 1/3] kms: Don't hardcode the output properties [PATCH 2/3] kms: Implement output->get_property when RandR1.3 is available. [PATCH 3/3] kms: Add TV-out support src/drmmode_display.c | 403 ++++++++++++++++++++++++++++++++----------------- 1 files changed, 261 insertions(+), 142 deletions(-)

Hello, This is an attempt at providing generic support for underscan connector props. We already have 3 drivers defining the same underscan, underscan vborder and underscan hborder properties (amd, radeon and nouveau) and I am about to add a new one, hence my proposal to put the prop parsing code in the core and add ->underscan fields to drm_connector_state. In this v2, I also converted the

...r/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: max.kammerer at yahoo.com QA Contact: xorg-team at lists.x.org There is probably a bug in dither.depth property set cause its value compared with dither.mode: //nouveau_connector.c if (property == disp->dithering_mode) { if (asyc->dither.mode != val) { asyc->dither.mode = val; asyc->set.dither = true; } } else if (property == disp->dithering_depth) { if (asyc->dither.mode != val) { //Should be dither.depth asyc->dither.depth = val; asyc->set.dithe...

We want to be able to guarantee the location of the allocated buffer object if we're going to be able to reliably allocate the existing framebuffer at startup. Add an argument to do so and pass that through to the ttm core. Signed-off-by: Matthew Garrett <mjg at redhat.com> --- drivers/bcma/main.c | 1 - drivers/gpu/drm/nouveau/nouveau_bo.c | 8 +++++++-