linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Egbert Eich <eich@pdx.freedesktop.org>
To: sottek@sottekland.com
Cc: eich@pdx.freedesktop.org, agd5f@yahoo.com, michel@daenzer.net,
	keithp@keithp.com, jonsmirl@yahoo.com, jsimmons@infradead.org,
	linux-fbdev-devel@lists.sourceforge.net,
	dri-devel@lists.sourceforge.net
Subject: Re: Current discussion about the future of free software graphics
Date: Wed, 12 May 2004 15:54:59 +0200	[thread overview]
Message-ID: <16546.11443.44701.174054@xf11.fra.suse.de> (raw)
In-Reply-To: sottek@sottekland.com wrote on Tuesday, 11 May 2004 at 13:09:48 -0500

sottek writes:
 > Can we wrap this up the discussion and try to get to a consensus on
 > design requirements? I think most of the opinions are starting to
 > solidify enough to start hashing out the requirements and actual
 > design.
 > 
 > Also, we probably want to drop the communication down to just one
 > list? I think dri-devel seems to have the widest group of subscribers.

Well, I would think there are a lot more people who are interested
in this subject than are subscribed on dri-devel. dri-devel really
has a different scope.

 > 4: Design must insure that user applications may not set the hardware
 > into an unstable state that could lead to lockup or damage display
 > devices.

The 'driver' must do mode validation using data supplied by either the 
display itself or the application (you need the second as some display 
devices may  not support sending this data or the data sent is bogus).

Broken video modes usually result from:
1. broken drivers
2. bogus user level configuration/override


Egbert.


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3

  parent reply	other threads:[~2004-05-12 13:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 18:09 Current discussion about the future of free software graphics sottek
2004-05-11 19:55 ` James Simmons
2004-05-11 20:46   ` Ian Romanick
2004-05-12  3:30     ` Jon Smirl
2004-05-12 14:41       ` Richard Smith
2004-05-12 17:56         ` James Simmons
2004-05-12 18:56           ` Geert Uytterhoeven
2004-05-12 19:11             ` James Simmons
2004-05-12 19:40               ` Geert Uytterhoeven
2004-05-12 21:09                 ` James Simmons
2004-05-12 19:23           ` Richard Smith
2004-05-12 20:45           ` Richard Smith
2004-05-12 16:45       ` James Simmons
2004-05-12 19:00         ` Geert Uytterhoeven
2004-05-12 22:45       ` Nicolas Souchu
2004-05-13 10:39       ` Michel Dänzer
2004-05-12  8:48     ` [Dri-devel] Re: " Keith Whitwell
2004-05-12 17:09       ` James Simmons
2004-05-13  3:32       ` Keith Packard
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-11  0:11 [Linux-fbdev-devel] " 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
     [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=16546.11443.44701.174054@xf11.fra.suse.de \
    --to=eich@pdx.freedesktop.org \
    --cc=agd5f@yahoo.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=jonsmirl@yahoo.com \
    --cc=jsimmons@infradead.org \
    --cc=keithp@keithp.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=michel@daenzer.net \
    --cc=sottek@sottekland.com \
    /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).