[PATCH] Read MGA PInS data on PowerPC

STALE7660d

2 messages, 1 author, 2005-08-25 · open the first message on its own page

[PATCH] Read MGA PInS data on PowerPC

From: Ian Romanick <hidden>
Date: 2005-08-24 22:45:05

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.

fa76838aa195ee448d788ba65d73fa30  matroxfb_PInS-01.patch

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDDPhgX1gOwKyEAw8RApKwAJ0SMcNCzdZJceCeJ8fi8pvfKaVhOwCfU1tD
+RfH4M6ACtK9v/u2LUtSuy4=
=56qc
-----END PGP SIGNATURE-----

Re: [PATCH] Read MGA PInS data on PowerPC

From: Ian Romanick <hidden>
Date: 2005-08-25 17:41:26

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.

fa76838aa195ee448d788ba65d73fa30  matroxfb_PInS-01.patch

Signed-off-by: Ian Romanick <redacted>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDDgJIX1gOwKyEAw8RAp3pAJ0djJUY6XsURmuofK/c8u0cf8w/fwCfafo6
tCfdbEK4qB5q/JY0ywk04N0=
=+XtZ
-----END PGP SIGNATURE-----
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help