IBM GXT6000P on parisc linux
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 5 lines · Berthold Gunreben
Hi,
I got a used HP parisc workstation, and found a GXT6000P video card in there. The card was detected and initialized by the firmware of this machine (a C3750).
wow..that's odd. I didn't see any web page which shows HP ever supported GXT6000P with HPUX. I suspect someone sold you the wrong card. Can you explain in more detail what you mean with "detected and initialized by the firmware"?
I suspect magic BIOS code isn't getting run. (It _might_ run under a C8000 but I don't expect it to work).
Quoted 8 lines
I just wanted to give it a try and compiled a module gxt4500 to
try this card. Here are my results:o The module builds without errors after adding PARISC to
Kconfigfor this module
o when loading the module, dmesg contains this:
Console: switching to colour frame buffer device 160x64
fb0: IBM GXT6000P frame buffer device
Ok. that's good.
...
Quoted 6 lines
However - the monitor stays in powersave mode, and no signal reaches the monitor, neither in text mode (console) nor in X11 mode. For some reason, the interrupt for this device (according to lspci it is IRQ 70) does not appear in
/proc/interrupts, but I don't know if this is even necessary for this driver.
Quoted 7 lines
lspci -vn gives me the following for this card:
03:02.0 Class 0300: 1014:0170 (rev 02) (prog-if 00 [VGA])Subsystem: 1092:0173 Flags: bus master, 66MHz, medium devsel, latency 255, IRQ 70 Memory at f7000000 (32-bit, non-prefetchable) [size=128K] Memory at f8000000 (32-bit, non-prefetchable) [size=64M] Expansion ROM at f7040000 [disabled] [size=256K]
You can determine if it's necessary by looking at the driver source code. Try to find where it registers the IRQ handler with request_irq(). Sounds like either it doesn't or it can't (but should print something to dmesg buffer in that case).
hth,
grant
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
A message that is not in the archive (sent off-list or not yet received): [email protected]
Am Sonntag, 30. September 2007 21:35 schrieb Grant Grundler:
Quoted 7 lines · Berthold Gunreben
Quoted 5 lines
Hi,
I got a used HP parisc workstation, and found a GXT6000P video card in there. The card was detected and initialized by the firmware of this machine (a C3750).
Quoted 7 lines
wow..that's odd. I didn't see any web page which shows HP ever supported GXT6000P with HPUX. I suspect someone sold you the wrong card. Can you explain in more detail what you mean with "detected and initialized by the firmware"?
I suspect magic BIOS code isn't getting run. (It _might_ run under a C8000 but I don't expect it to work).
Well, what can I say. The workstation boots up and displays the usual firmware messages like press Tab to choose resolution (only 640x480 seems to be supported at that stage) and I can also enter commands at this console. The card does not seem to be wrong in this respect.
After booting linux, the messages of the kernel are displayed until the console switches:
console handover: boot [ttyB0] -> real [tty0]
Then it takes some more seconds, until the display goes dark and I was not yet successful in bringing it to life again.
Quoted 4 lines
You can determine if it's necessary by looking at the driver source code. Try to find where it registers the IRQ handler with
request_irq(). Sounds like either it doesn't or it can't (but should print something to dmesg buffer in that case).
The driver has no occurence of irq, and it only handles framebuffer (normally, this card also should have 3D capabilities. It looks like it just does not need IRQs.
It looks like the card is switched off by using
pdc_cons.flags &= ~CON_PRINTBUFFER
At least if I comment this line, booting continues with messages until some point where the machine just hangs.
I am sorry, that I did not post more information in the first place, but I don't have much experience with graphics on parisc-linux ...
Thanks for your efforts anyway.
Berthold
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 13 lines · Berthold Gunreben
Am Sonntag, 30. September 2007 21:35 schrieb Grant Grundler:
Quoted 12 lines · Berthold Gunreben
Quoted 5 lines
Hi,
I got a used HP parisc workstation, and found a GXT6000P video card in there. The card was detected and initialized by the firmware of this machine (a C3750).
wow..that's odd. I didn't see any web page which shows HP ever supported GXT6000P with HPUX. I suspect someone sold you the wrong card. Can you explain in more detail what you mean with "detected and initialized by the firmware"?
Quoted 8 lines
Quoted 2 lines
I suspect magic BIOS code isn't getting run. (It _might_ run under a C8000 but I don't expect it to work).
Well, what can I say. The workstation boots up and displays the usual firmware messages like press Tab to choose resolution (only 640x480 seems to be supported at that stage) and I can also enter commands at this console. The card does not seem to be wrong in this respect.
Most likely, all the card hardware required to do 640x480 was a power-on reset signal.
That rate is very non-hp - it is a rare parisc system monitor that can display at that scan.
Quoted 8 lines
After booting linux, the messages of the kernel are displayed until the console switches:
console handover: boot [ttyB0] -> real [tty0]
Then it takes some more seconds, until the display goes dark and I was not yet successful in bringing it to life again.
Sounds like the card never got setup for anything that wasn't hardware defaulted by the power-on signal.
If I recall correctly, that means (from non-parisc, vga mode land) that the video interrupt generation is also disabled on the card.
Quoted 9 lines
Quoted 4 lines
You can determine if it's necessary by looking at the driver source code. Try to find where it registers the IRQ handler with
request_irq(). Sounds like either it doesn't or it can't (but should print something to dmesg buffer in that case).The driver has no occurence of irq, and it only handles framebuffer (normally, this card also should have 3D capabilities. It looks like it just does not need IRQs.
Perhaps the driver was written to use _only_ the power-on defaults with a lot more work required to do anything else.
Like the other 90% of the driver.
Mike
Quoted 9 lines
It looks like the card is switched off by using
pdc_cons.flags &= ~CON_PRINTBUFFERAt least if I comment this line, booting continues with messages until some point where the machine just hangs.
I am sorry, that I did not post more information in the first place, but I don't have much experience with graphics on parisc-linux ...
Quoted 9 lines
Thanks for your efforts anyway.
Berthold
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux