linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>
To: Adam Jackson <ajax-TAsg7VrFCGc@public.gmane.org>
Cc: xserver-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org, "Sottek,
	Matthew J"
	<matthew.j.sottek-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	dri-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	linux-fbdev-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	mesa3d-dev-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Current discussion about the future of free software graphics
Date: Tue, 11 May 2004 15:24:24 +0200	[thread overview]
Message-ID: <1084281863.807.73.camel@thor.asgaard.local> (raw)
In-Reply-To: <200405102120.48640.ajax-TAsg7VrFCGc@public.gmane.org>


[ Please remove any subject tags when following up ]

On Tue, 2004-05-11 at 04:20, Adam Jackson wrote:
> 
> You only need to trust the user if the operation could have security 
> implications.

[...]

> mode setting isn't sensitive because changing the display mode isn't going 
> to stomp on kernel data structures or on the address space of other running 
> processes.

You're assuming that the user programs a valid mode, but the proposed
interface allows to program any combination of mode register values, of
which valid modes are probably just a small subset, depending on the
hardware. Combinations outside that set might cause unwanted effects
such as lockups or even hardware damage, which is bad enough IMHO.
System RAM access via DMA probably isn't an issue here with the hardware
I'm familiar with, but it might be with others.


> The mechanism _should_ be masked behind a library that abstracts away 
> the device and implementation details as much as possible so the user 
> (where here "user" equals X11 Classic, Y-Windows, Mesa Solo, whatever) 
> doesn't have to care, and also so each new user doesn't have to write 
> the same code again.

Yes, an ALSA-style model is probably the way to go. I'm just pointing
out that the interface between the library and the kernel probably can't
be simply an unrestricted ioctl to dump a bunch of register values.


-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Libre software enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer

  parent reply	other threads:[~2004-05-11 13:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11  0:11 [Linux-fbdev-devel] Current discussion about the future of free software graphics Sottek, Matthew J
2004-05-11  2:20 ` Adam Jackson
     [not found]   ` <200405102120.48640.ajax-TAsg7VrFCGc@public.gmane.org>
2004-05-11 13:24     ` Michel Dänzer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-12  3:30 Jon Smirl
2004-05-13 10:39 ` Michel Dänzer
2004-05-11 18:09 sottek
2004-05-11 19:55 ` James Simmons
2004-05-12 14:14   ` Alan Cox
2004-05-11 20:07 ` Geert Uytterhoeven
2004-05-11 23:10   ` James Simmons
2004-05-11 23:15 ` Nicolas Souchu
2004-05-12 13:34 ` Michel Dänzer
2004-05-12 13:54 ` Egbert Eich
     [not found] <1084205711.804.43.camel@thor.asgaard.local>
2004-05-10 23:45 ` James Simmons
2004-05-10 16:15 Michel Dänzer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1084281863.807.73.camel@thor.asgaard.local \
    --to=michel-otuistvhuppr7s880joybq@public.gmane.org \
    --cc=ajax-TAsg7VrFCGc@public.gmane.org \
    --cc=dri-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-fbdev-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=matthew.j.sottek-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=mesa3d-dev-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=xserver-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).