From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
<linuxppc-dev@lists.linuxppc.org>,
<debian-powerpc@lists.debian.org>
Subject: Re: Success! (was Re: External Monitor under Pismo)
Date: Fri, 4 May 2001 16:54:22 +0200 [thread overview]
Message-ID: <20010504145422.25284@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10105041612120.2886-100000@callisto.of.borg>
>
>
>If you point the second CRTC to the same frame buffer region, you'll have
>mirrorring, else you have two different heads.
In most cases (like what I do with aty128fb), you don't even need to use the
second CRTC. Just enable both outputs and let them source from the first CRTC.
>> So i suppose the you will need to use a trick similar to the matrox one
>to get
>> dual headed accelerated X to work.
>
>Yep. The same is true for atyfb (yes, I should add mirrorring/dualhead
support
>for the Mobility in my Vaio :-).
>
>> But could it be possible to block this in hardware, and thus force
mirroring
>> only operation ?
>
>I suppose yes.
>
>> How many different rage 128 mobility are around anyway ?
>
>No idea. I just at the ATI website earlier today, and they seem to have new
>variants called M4 and Radeon Mobility.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-05-04 14:54 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 9:21 External Monitor under Pismo Iain Sandoe
2001-04-04 17:01 ` Andrew Sharp
2001-04-04 18:43 ` Jason E. Stewart
2001-04-04 18:01 ` Michel Dänzer
2001-04-04 19:28 ` Jason E. Stewart
2001-04-04 21:45 ` Michel Dänzer
2001-04-04 23:19 ` Jason E. Stewart
2001-04-04 22:22 ` Michel Dänzer
2001-04-05 19:55 ` Jason E. Stewart
2001-04-05 19:48 ` Michel Dänzer
2001-04-05 21:49 ` Jason E. Stewart
2001-04-05 23:46 ` Jason E. Stewart
2001-04-05 23:28 ` Michel Dänzer
2001-04-06 3:04 ` Steven Hanley
[not found] ` <87itjmf7lf.fsf_-_@amadeus.openinformatics.com>
2001-04-30 23:03 ` Success! (was Re: External Monitor under Pismo) Michel Dänzer
2001-05-04 2:10 ` Jason E. Stewart
2001-05-03 22:18 ` Michel Dänzer
2001-05-04 9:08 ` Jason E. Stewart
2001-05-04 12:05 ` Michel Dänzer
2001-05-04 17:14 ` Jason E. Stewart
2001-05-04 17:16 ` Jason E. Stewart
2001-05-05 1:37 ` Michel Dänzer
2001-05-05 9:38 ` Jason E. Stewart
2001-05-05 17:59 ` Michel Dänzer
2001-05-05 21:14 ` Jason E. Stewart
2001-05-06 13:32 ` Michel Dänzer
2001-05-06 21:55 ` Jason E. Stewart
2001-05-07 8:15 ` Michel Dänzer
2001-05-04 12:29 ` Benjamin Herrenschmidt
2001-05-04 13:34 ` Sven LUTHER
2001-05-04 13:57 ` Benjamin Herrenschmidt
2001-05-04 14:06 ` Sven LUTHER
2001-05-04 14:13 ` Benjamin Herrenschmidt
2001-05-04 14:14 ` Geert Uytterhoeven
2001-05-04 14:23 ` Sven LUTHER
2001-05-04 14:54 ` Benjamin Herrenschmidt [this message]
2001-05-04 15:05 ` Ramprasad Rao
2001-05-04 15:09 ` Benjamin Herrenschmidt
2001-05-04 15:17 ` Ramprasad Rao
2001-05-04 20:50 ` Michael Schmitz
2001-05-05 1:03 ` Benjamin Herrenschmidt
2001-05-05 18:49 ` Michael Schmitz
2001-05-04 17:10 ` Jason E. Stewart
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=20010504145422.25284@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.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).