aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/video/sis/oem300.h
diff options
context:
space:
mode:
authorIan Romanick <idr@us.ibm.com>2005-09-09 13:04:42 -0700
committerLinus Torvalds <torvalds@g5.osdl.org>2005-09-09 13:58:01 -0700
commit5c06e2aa6339112befdc87b350b8bf712890d7a7 (patch)
tree13a3b008a6a64f051b75f59d194d32e290be5fbc /drivers/video/sis/oem300.h
parentf510a3c3d48fd5aaa7757aebbc37e9ee417913a3 (diff)
downloadmrst-s0i3-test-5c06e2aa6339112befdc87b350b8bf712890d7a7.tar.gz
mrst-s0i3-test-5c06e2aa6339112befdc87b350b8bf712890d7a7.tar.xz
mrst-s0i3-test-5c06e2aa6339112befdc87b350b8bf712890d7a7.zip
[PATCH] matroxfb: read MGA PInS data on PowerPC
This updates the matroxfb code so that it can find the PInS data embedded in the BIOS on PowerPC cards. The process for finding the data is different on OpenFirmware cards than on x86 cards, and the code for doing so was missing. After patching, building, installing, and booting a kernel, you should grep for "PInS" in /var/log/messages. You should see two messages in the log: PInS data found at offset XXXXX PInS memtype = X On the GXT135p card I get "31168" and "5". The first value is irrelevant, but it's presence lets me know that the PInS data was actually found. On a GXT130p, the second value should be 3. Since I don't have access to that hardware, if someone can verify that, I will submit a follow-on patch that rips out all the memtype parameter stuff. Signed-off-by: Ian Romanick <idr@us.ibm.com> Signed-off-by: Petr Vandrovec <vandrove@vc.cvut.cz> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'drivers/video/sis/oem300.h')
0 files changed, 0 insertions, 0 deletions