From: Mike Mestnik <cheako911@yahoo.com>
To: Jon Smirl <jonsmirl@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Keith Packard <keithp@keithp.com>
Cc: dri-devel <dri-devel@lists.sourceforge.net>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Design for setting video modes, ownership of sysfs attributes
Date: Sun, 19 Sep 2004 10:19:07 -0700 (PDT) [thread overview]
Message-ID: <20040919171907.6090.qmail@web11905.mail.yahoo.com> (raw)
In-Reply-To: <9e47339104091909465c9a483f@mail.gmail.com>
--- Jon Smirl <jonsmirl@gmail.com> wrote:
> On Sun, 19 Sep 2004 14:45:37 +1000, Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
> > Typically, with X: We don't want X itself to have to be the one
> setting
> > the mode, but rather set the mode and have X be notified properly
> before
> > and after it happens so it can "catch up".
>
> This is going to require some more thought. Mode setting needs two
> things, a description of the mode timings and a location of the scan
> out buffer. With multiple heads you can't just assume that the buffer
> starts at zero. There also the problem of the buffer increasing in
> size and needing to be moved since it won't fit where it is.
>
There will be cases where there won't be enuff memory for both
framebuffers. Most video cards will support power-saving modes or an
"off" state. This can be used so that the user won't see the Framebuffer
get overriten with the new data, whatever gets swaped into that memory
location.
> Keith, how should this work for X? We have to make sure all DRI users
> of the buffer are halted, get a new location for the buffer, set the
> mode, free the old buffer, notify all of the DRI clients that their
> target has been wiped and has a new size.
>
> I was wanting to switch mode setting into an atomic operation where
> you passed in both the mode timings and buffer location.
>
I think it would work best if the buffer where setup/maped/allocated(in
revers order), then the call to program the DAC. It dosen't make any
differance if it is attomic, worst case the user will just see trash.
> --
> Jon Smirl
> jonsmirl@gmail.com
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> --
> _______________________________________________
> Dri-devel mailing list
> Dri-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dri-devel
>
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail
next prev parent reply other threads:[~2004-09-19 17:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-18 18:43 Jon Smirl
2004-09-18 19:58 ` Mike Mestnik
2004-09-18 22:12 ` Jon Smirl
2004-09-18 22:37 ` Mike Mestnik
2004-09-18 23:33 ` Keith Packard
2004-09-19 0:54 ` Jon Smirl
2004-09-19 1:57 ` Vladimir Dergachev
2004-09-19 2:16 ` Jon Smirl
2004-09-19 2:32 ` Vladimir Dergachev
2004-09-19 10:11 ` Mike Mestnik
2004-09-19 9:55 ` Mike Mestnik
2004-09-19 4:48 ` Benjamin Herrenschmidt
2004-09-19 16:12 ` Jon Smirl
2004-09-20 0:07 ` Benjamin Herrenschmidt
2004-09-20 1:06 ` Jon Smirl
2004-09-19 4:45 ` Benjamin Herrenschmidt
2004-09-19 16:46 ` Jon Smirl
2004-09-19 17:19 ` Mike Mestnik [this message]
2004-09-19 20:40 ` Keith Packard
2004-09-20 13:02 ` Alan Cox
2004-09-19 20:44 ` Felix Kühling
2004-09-20 1:25 ` Mike Mestnik
2004-09-20 0:10 ` Benjamin Herrenschmidt
2004-09-21 12:45 ` Pavel Machek
2004-09-21 15:56 ` Jon Smirl
2004-09-21 15:42 ` Alan Cox
[not found] <2FYdH-10h-5@gated-at.bofh.it>
[not found] ` <2G6Et-6D7-31@gated-at.bofh.it>
2004-09-19 14:18 ` Pascal Schmidt
2004-09-19 15:00 ` P. Benie
2004-09-19 19:08 ` Pascal Schmidt
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=20040919171907.6090.qmail@web11905.mail.yahoo.com \
--to=cheako911@yahoo.com \
--cc=benh@kernel.crashing.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=jonsmirl@gmail.com \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome