From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: Ian Romanick <idr@us.ibm.com>,
Egbert Eich <eich@pdx.freedesktop.org>,
DRI Devel <dri-devel@lists.sourceforge.net>,
mesa3d-dev <mesa3d-dev@lists.sourceforge.net>,
fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Mesa3d-dev] RE: [Dri-devel] Memory management of AGP and VRAM
Date: Mon, 10 May 2004 08:59:07 +0100 [thread overview]
Message-ID: <1084175946.24578.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20040509164514.17651.qmail@web14922.mail.yahoo.com>
On Sul, 2004-05-09 at 17:45, Jon Smirl wrote:
> Also, these is no rule saying a device driver can't have several tables of _init
> register values that can be used to set the mode on a primary monitor at boot. I
> would just like to see all of the code that does DDC decoding and modeline
> computations moved to user space.
But there should also be no rule that says it cannot be in kernel space.
Lets take the Voodoo2 again, the mode computation is *tiny*.
Or many embedded devices where the modes are very simple to set up.
The API at user space for the driver modules has to leave the question
of *who* does what private to the driver.
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-05-10 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A98078D7EF5BEA4D8D8FD797FFBBC75F0742A3A0@fmsmsx402.fm.intel.com>
[not found] ` <16539.63659.810291.931565@xf11.fra.suse.de>
2004-05-07 21:23 ` RE: [Dri-devel] Memory management of AGP and VRAM Ian Romanick
2004-05-09 16:45 ` Jon Smirl
2004-05-09 21:27 ` Holger Waechtler
2004-05-09 21:53 ` Holger Waechtler
2004-05-10 7:59 ` Alan Cox [this message]
2004-05-10 16:16 ` [Linux-fbdev-devel] " James Simmons
2004-05-11 16:50 ` Egbert Eich
2004-05-11 18:48 ` [Linux-fbdev-devel] " James Simmons
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=1084175946.24578.12.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.sourceforge.net \
--cc=eich@pdx.freedesktop.org \
--cc=idr@us.ibm.com \
--cc=jonsmirl@yahoo.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=mesa3d-dev@lists.sourceforge.net \
/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).