linux-kernel - Re: Proposal for a low-level Linux display framework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <yunpqivfbtf.fsf@aiko.keithp.com>
Date:	Tue, 20 Sep 2011 08:55:24 -0700
From:	Keith Packard <keithp@...thp.com>
To:	Patrik Jakobsson <patrik.r.jakobsson@...il.com>,
	Tomi Valkeinen <tomi.valkeinen@...com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-fbdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
	linaro-dev@...ts.linaro.org, "Clark\, Rob" <rob@...com>,
	Archit Taneja <archit@...com>
Subject: Re: Proposal for a low-level Linux display framework

On Tue, 20 Sep 2011 10:29:23 +0200, Patrik Jakobsson <patrik.r.jakobsson@...il.com> wrote:

> It would be nice to have a model that fits both DSI and SDVO, and the option
> to configure some of it from userspace.

> I thought the purpose of drm_encoder was to abstract hardware like this?

SDVO is entirely hidden by the drm_encoder interface; some of the
controls (like TV encoder parameters) are exposed through DRM
properties, others are used in the basic configuration of the device.

I'm not sure we need a new abstraction that subsumes both DSI and SDVO,
but we may need a DSI library that can be used by both DRM and other
parts of the kernel.

-- 
keith.packard@...el.com

Content of type "application/pgp-signature" skipped