From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
<linuxppc-dev@lists.linuxppc.org>,
<debian-powerpc@lists.debian.org>
Subject: Re: Success! (was Re: External Monitor under Pismo)
Date: Sat, 5 May 2001 03:03:18 +0200 [thread overview]
Message-ID: <20010505010318.5183@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0105042247590.3732-100000@opal.biophys.uni-duesseldorf.de>
>> Yep. The same is true for atyfb (yes, I should add mirrorring/dualhead
>support
>> for the Mobility in my Vaio :-).
>
>Please do - I tried Ben's mirror utility on the Lombard but no success.
>And I still have no aty docs to look up the details in.
Well, if you do that, it may be interesting to impement the same
ioctls I have in my aty128fb version (I'll send it to you later
if you don't want to rsync down my entire tree).
I beleive you can do something very similar by just toggling the
CRT & LCD enable bits on the first CRT. No need for CRTC 2 for
simple mirroring. "Smart" mirroring (with higher refresh rate) would
require use of CRTC2 however.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-05-05 1:03 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
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 [this message]
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=20010505010318.5183@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 \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
/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).