linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
To: Magnus Damm <damm@opensource.se>, linuxppc-dev@lists.linuxppc.org
Subject: Re: aty128fb and EDID
Date: Sun, 9 Feb 2003 19:40:10 -0500	[thread overview]
Message-ID: <200302091940.10202.kevin.hendricks@sympatico.ca> (raw)
In-Reply-To: <20030209232633.414c0fc0.damm@opensource.se>


Hi,

Steal the code from the radeon dirver in the kernel.  It finds and parses
the EDID block in OF for ppc linux systems for LCD.

It works fine with my 17 in lcd display.

Kevin

On February 9, 2003 06:26, Magnus Damm wrote:
> Hi,
>
> I recently bought a Cube G4 and got a 17" Apple Studio Display (CRT,
> ADC) with it. However, that combination seems hard to use out of the box
> if you want to use something else than the open firmware framebuffer.
>
> The thing is that the monitor only supports two modes:
> 1600x1200 64Hz
> 1280x1024 75Hz
>
> This gives me no picture at all when I try to use the aty128 driver.
>
> However, when I hardcode this video mode as default things work out ok:
> /* default modedb mode */
> /* 1600x1200, 64Hz, Non-Interlaced */
> static struct fb_videomode defaultmode __initdata = {
>         refresh:        64,
>         xres:           1600,
>         yres:           1200,
>         pixclock:       5952,
>         left_margin:    304,
>         right_margin:   24,
>         upper_margin:   38,
>         lower_margin:   1,
>         hsync_len:      184,
>         vsync_len:      3,
>         sync:           3,
>         vmode:          FB_VMODE_NONINTERLACED
> };
>
> The information above was built from my EDID file.
>
> To create some kind of generic solution I need to add EDID support to
> the aty128 driver, or even better - a generic framebuffer layer.
>
> My question to you is:
> All probing that is done by checking if "machine_is_compatible()", could
> that all be replaced by EDID code?
>
> If you could send me your EDID files with together with information
> about your machine and monitor I would be really happy. Then I could
> parse them and see if they contain enough information. If you don't find
> any EDID file then I would be glad to know that too.
>
> These machines are extra interesting:
> * PowerMac2,1 first r128 iMacs
> * PowerMac2,2 summer 2000 iMacs
> * PowerMac4,1 january 2001 iMacs "flower power"
> * iBook SE
> * PowerBook Firewire (Pismo), iBook Dual USB
> * PowerBook Titanium
>
> I find my EDID file in /proc/device-tree/pci/ATY,Rage128Pd@10/EDID
>
> Thanks.
>
> / magnus
>


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

  reply	other threads:[~2003-02-10  0:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-09 23:26 aty128fb and EDID Magnus Damm
2003-02-10  0:40 ` Kevin B. Hendricks [this message]
2003-02-10  9:35   ` Geert Uytterhoeven
2003-02-10 10:14     ` Magnus Damm
2003-02-10 13:16       ` Kevin B. Hendricks
2003-02-10 18:41         ` Dan Burcaw
2003-02-10 18:59           ` Kevin B. Hendricks
2003-02-10 10:34     ` Benjamin Herrenschmidt
2003-02-10 12:36     ` Kevin B. Hendricks

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=200302091940.10202.kevin.hendricks@sympatico.ca \
    --to=kevin.hendricks@sympatico.ca \
    --cc=damm@opensource.se \
    --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).