linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: daRonin <daronin@digimerc.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: external cinema 22" display
Date: Mon, 3 Feb 2003 10:44:52 -0700 (MST)	[thread overview]
Message-ID: <Pine.LNX.4.50L0.0302031032090.1676-100000@daronin.digimerc.com> (raw)
In-Reply-To: <20030202213541.GC22344@haar.ae.gatech.edu>


  I finally got my Cinema display working on TiBook G4 with Radeon M6 LY
in it.

 It would seem that radeonfb doesn't even look for CRT port on M6 LY.

 At the line 1058 of radeonfb.c (v 0.1.6):
 <snip>
        switch (rinfo->arch) {
                case RADEON_M6:
                case RADEON_M7:
                case RADEON_M9:
                        rinfo->dviDisp_type = MT_LCD;
                        break;

   <snip>

  The code just assumes that if I have RADEON_M6 all I've got is LCD. So I
added another command line option called "crt" and added a line:

<snip>

        switch (rinfo->arch) {
                case RADEON_M6:
                case RADEON_M7:
                case RADEON_M9:
                        /* modified by daRonin */
                        if (force_crt) radeon_get_moninfo(rinfo);
                        else rinfo->dviDisp_type = MT_LCD;
                        break;

<snip>

  After this my cinema display started working properly, though still
throughing me into 640x480-8@70 mode.

 So I added an fbset command in my rc scripts. I still had to play with
timings quite a bit. For one I had to set vsync to high, otherwise the
monitor wouldn't even come up in any resolution.

  I also got this working only with my ebuild Gentoo kernel (2.4.20-r2), I
tried 2.4.20-ben4 and 2.4.20-ben5. In both of those, after my
modifications the cinema display worked, but the LCD didn't blank, instead
it went white. I played around with the code, but couldn't find the source
of the problem...

  If anyone is interested I can send them the modified radeonfb.c as well
as the timings for 1600x1024-60...

  Andrew


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-02-03 17:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-20 15:59 VGA out/External Monitor on ibook 2 Manuj Dhingra
2003-01-20 18:22 ` Owen Stampflee
2003-02-02 21:35   ` Manuj Dhingra
2003-02-03 17:44     ` daRonin [this message]
2003-02-09 10:44 ` Harald Welte
2003-02-10 10:06   ` Michael Schmitz
2003-02-10 15:06     ` Manuj Dhingra
2003-02-10 16:24       ` Michael Schmitz
2003-02-10 17:27         ` Michel Dänzer
2003-02-10 18:43           ` Manuj Dhingra
2003-02-11  0:38             ` Michel Dänzer
2003-02-13 22:52           ` DVI External Monitor on TiBook IV daRonin
2003-02-14 11:06             ` Benjamin Herrenschmidt
2003-02-25 18:43           ` VGA out/External Monitor on ibook 2 --Success!! Manuj Dhingra

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=Pine.LNX.4.50L0.0302031032090.1676-100000@daronin.digimerc.com \
    --to=daronin@digimerc.com \
    --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).