From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Radeon issue on x86
Date: Wed, 18 Feb 2004 10:37:49 +1100 [thread overview]
Message-ID: <1077061068.1080.46.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.58.0402171503150.2154@home.osdl.org>
Hi Linus !
One of the issue I'm having with raeonfb on x86 is the need
to retreive the panel informations out of the BIOS. My current
algorithm is to try to retreive that from the PCI ROM of the
video chip, and if I cannot find any, then look at the BIOS ROM
image in low memory.
However, I got a few reports of that not working. Usually, on
laptops, apparently, the PCI ROM doesn't exist and it can all
be found in the low memory image (I suppose the video BIOS on
these is hidden somewhere with the main BIOS and copied to RAM
at aboot). BUT, some laptops like some Dell inspirons will show
a valid PCI ROM (valid signature) on the video chip, though
this ROM appear to not contain any useable panel information
table :( However, on these, the RAM image do seem to contain
the table... So I would need to reverse my algorithm and
default to the RAM BIOS on laptops at least...
The problem with the RAM image is that it's only there for the
primary display chip that was initialized at boot. So I would
need to "know" which PCI card is the primary display. That's all
x86 architecture black magic, so I'd like your advice on the best
way to do that. Also, that low memory region at c0000, what is
it's exact format ? I currently copied a search routine from
XFree but it does very little verifications in there, I'm a bit
paranoid about picking the wrong thing...
What do you suggest ?
Ben.
next prev parent reply other threads:[~2004-02-17 23:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 3:51 Linux 2.6.3-rc4 Linus Torvalds
2004-02-17 6:19 ` Felix Seeger
2004-02-17 8:54 ` Martin Diehl
2004-02-17 9:27 ` Martin Diehl
2004-02-17 15:39 ` Bartlomiej Zolnierkiewicz
2004-02-17 16:21 ` Linux 2.6.3-rc4 (compile stats) John Cherry
2004-02-17 18:45 ` Linux 2.6.3-rc4 GCS
2004-02-17 19:09 ` Linus Torvalds
2004-02-17 20:05 ` Adrian Bunk
2004-02-17 20:16 ` Linus Torvalds
2004-02-17 22:59 ` Adrian Bunk
2004-02-17 23:11 ` Linus Torvalds
2004-02-17 23:37 ` Benjamin Herrenschmidt [this message]
2004-02-18 0:17 ` Radeon issue on x86 Linus Torvalds
2004-02-18 0:33 ` Benjamin Herrenschmidt
2004-02-18 0:00 ` Linux 2.6.3-rc4 Adrian Bunk
2004-02-18 1:28 ` Roman Zippel
2004-02-18 0:39 ` Roman Zippel
2004-02-18 1:06 ` Roman Zippel
2004-02-18 2:45 ` Roman Zippel
2004-02-18 2:58 ` Linus Torvalds
2004-02-18 0:15 ` Roman Zippel
2004-02-18 0:21 ` GCS
2004-02-17 18:56 ` Jonathan Brown
2004-02-17 19:06 ` Linus Torvalds
2004-02-18 10:18 ` Andreas Happe
2004-02-18 4:06 ` Stephen Rothwell
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=1077061068.1080.46.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.