From: "Benjamin Herrenschmidt" <benh@kernel•crashing.org>
To: "Ani Joshi" <ajoshi@unixbox•com>
Cc: "Stefan Jeglinski" <jeglin@4pi•com>, <linuxppc-dev@lists•linuxppc.org>
Subject: Re: part deux Re: Radeon 7000 in 9500 - which slot?
Date: Wed, 16 Oct 2002 21:53:39 +0200 [thread overview]
Message-ID: <20021016195339.21549@192.168.4.1> (raw)
In-Reply-To: <Pine.BSF.4.44.0210161110480.97189-100000@shell.unixbox.com>
>It is not detecting the heads properly because on many "mac" radeons, the
>firmware doesn't initialize the SCRATCH registers properly which contain
>information about display type. There is no reliable method of probing
>display type on ppc so I will end up adding a display type option to
>radeonfb next version.
Well... It should be possible to get that info from OF properties
or is the OF driver broken enough to not export that either ?
How does the MacOS driver to probe displays ? Isn't it possible
to just try the various i2c channels until an EDID is found to
figure what's up ? The CRT port can definitely probe for the
presence of the display by measuring the load on the analog
outputs.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-10-16 19:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 6:13 Radeon 7000 in 9500 - which slot? Stefan Jeglinski
2002-10-10 9:51 ` Benjamin Herrenschmidt
2002-10-10 13:31 ` Michel Dänzer
2002-10-10 20:32 ` Olaf Hering
2002-10-10 21:59 ` Benjamin Herrenschmidt
2002-10-11 7:20 ` Olaf Hering
2002-10-11 10:09 ` Benjamin Herrenschmidt
2002-10-11 10:41 ` Olaf Hering
2002-10-16 6:04 ` part deux " Stefan Jeglinski
2002-10-16 12:16 ` Benjamin Herrenschmidt
2002-10-16 17:27 ` Olaf Hering
2002-10-16 18:33 ` Stefan Jeglinski
2002-10-16 19:53 ` Olaf Hering
2002-10-16 18:12 ` Ani Joshi
2002-10-16 18:27 ` Stefan Jeglinski
2002-10-16 19:53 ` Benjamin Herrenschmidt [this message]
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=20021016195339.21549@192.168.4.1 \
--to=benh@kernel$(echo .)crashing.org \
--cc=ajoshi@unixbox$(echo .)com \
--cc=jeglin@4pi$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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