Re: s3virge bigendian
Meelis Roos wrote: Do you know what physical memory the card has without looking at xfree86? ViRGE cards can be 2M or 4M. You might try specifying 2M and I googled a little and found that it's likely to be a 2M card. The card is Formac GA6 (Formac Pro Media 20 Plus), it contains 4 RAM chips and 4 places for additional chips. The chips are labeled V53C16258HK40. On Formac Pro Media 40 Plus there are 8 such RAM chips and total 4M of RAM. Some more Googling and now it's sure - there are 4 chips of (256Kx16) so 2M total. I tried the card in x86 to see if the RAM size is detected right there but I had little success. First the PC didn't like F-COde ROM so the card could not be used as the primary card. Running atimach64 as primary and s3virge as secondary didn't work either - both wanted to decode VGA addresses and some chars appeared on screen but some in the video ram of the other card. Finally it booted up using s3virge dx as primary and this (effectively biosless) s3virge as secondary. But I have big trouble running X - I configured XF 4.2.1 for this card but it tends to hang on DDC, Accel etc. I couldn't squeeze the guessed videoram size out of it so I don't know whether X detects the right videoram size on x86. see if that resolves this issue. Of course you will only be able to run modes that fit in 2M, but that will fix the possibility of pixmap cache Will try in the evening (GMT+0200 here). How am I suppsed to force videoram size - no option for that? OK, will just hardcode it and see. Some options that are general to all drivers are only documented in 'man XF86Config' not 'man s3virge'. You should find that 'videoram 2048' works for the s3virge driver in the Device section. -- Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: s3virge bigendian
On Thu, 30 Jan 2003, Meelis Roos wrote: I tried the card in x86 to see if the RAM size is detected right there but I had little success. First the PC didn't like F-COde ROM so the card could not be used as the primary card. Running atimach64 as primary and s3virge as secondary didn't work either - both wanted to decode VGA addresses and some chars appeared on screen but some in the video ram of the other card. Finally it booted up using s3virge dx as primary and this (effectively biosless) s3virge as secondary. But I have big trouble running X - I configured XF 4.2.1 for this card but it tends to hang on DDC, Accel etc. I couldn't squeeze the guessed videoram size out of it so I don't know whether X detects the right videoram size on x86. If you are having problems with DDC you might want to try some of these: Option NoDDC Option NoDDC1 Option NoDDC2 Option NoVBE -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: s3virge bigendian
Some options that are general to all drivers are only documented in 'man XF86Config' not 'man s3virge'. You should find that 'videoram 2048' works for the s3virge driver in the Device section. First, I tested the card in x86 now, NoAccel and NoDDC options made it so far that I saw it detect 4M RAM on x86 too. Using option videoram 2048 doesn't seem to work - it still displays videoram: 4096 on both PPC and x86 and then in the end of the log tells that option videoram was unused. Hardcoding 2048 works, PPC restricts its videoram to 2M and chooses correct video mode. The picture is now OK (with just sawfish, xterm and mozilla), will try try other applications now. -- Meelis Roos ([EMAIL PROTECTED]) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: s3virge bigendian
Now the remanining problem is the garbage in lower part of the screen - any ideas about that? It's there even with NoAccel and changing too. If you have accel enabled, but then use 'sw_cursor' option, does the noise still appear? Yes. Just moving the cursor makes it flicker. The flickering part is the last 0.5 M of the framebuffer. 2M is OK and the last 0.5M is garbage (at 1280x1024,16bpp). Something to do with video ram size detection? Haven't still had time to test this specific card in x86. -- Meelis Roos ([EMAIL PROTECTED]) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: s3virge bigendian
Meelis Roos wrote: Have you tried setting BIT_ORDER_IN_BYTE_LSBFIRST or BIT_ORDER_IN_BYTE_MSBFIRST in the *ColorExpandFillFlags field of the XAAInfoRec ? Wow. Option NoAccel makes the reversion go away and fixes garbage in Mozilla too. Changing MSBFIRST to LSBFIRST fixed the fonts, thanks! Garbage in Mozilla still remains when acceleration is turned on - what other XAA bits should I look over? Now the remanining problem is the garbage in lower part of the screen - any ideas about that? It's there even with NoAccel and changing too. If you have accel enabled, but then use 'sw_cursor' option, does the noise still appear? -- Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: s3virge bigendian
Michel Dänzer wrote: On Mon, 2003-01-20 at 18:57, Meelis Roos wrote: Colors are OK now but the bitmaps are broken. When fonts are drawn in xterm, every 8 pixels are horizontally reversed (in 16bpp mode). Mozilla window contets are mostly OK but some garbage remains inside frames. When moving xterm over mozilla, traces remain (probably the same bitmap reversion problem). Have you tried setting BIT_ORDER_IN_BYTE_LSBFIRST or BIT_ORDER_IN_BYTE_MSBFIRST in the *ColorExpandFillFlags field of the XAAInfoRec ? is fbOffset the right field to use the 32M offset that bigendian mode needs? No, I think you should leave fbOffset at 0 and add the 32M to the pScrn-memPhysBase (and pass that to xf86MapPciMem) instead. The virge supports a seperate config for little/bigendian memory mapping, so this might be a better choice than adding 32M as you suggest. -- Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: s3virge bigendian
On Don, 2003-01-23 at 08:51, Meelis Roos wrote: Now the remanining problem is the garbage in lower part of the screen - any ideas about that? It's there even with NoAccel and changing too. Changing what? Have you tried the modifications I suggested for the framebuffer aperture? I suspect that the pixmap cache is at the end of video RAM and I'm running into it with framebuffer - but I'm not sure. As you say it also happens with NoAccel, it can't really be related to the pixmap cache. No idea what it could be unfortunately, if it's using the correct amount of video RAM. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: s3virge bigendian
On Mit, 2003-01-22 at 08:51, Meelis Roos wrote: Have you tried setting BIT_ORDER_IN_BYTE_LSBFIRST or BIT_ORDER_IN_BYTE_MSBFIRST in the *ColorExpandFillFlags field of the XAAInfoRec ? Wow. Option NoAccel makes the reversion go away and fixes garbage in Mozilla too. Changing MSBFIRST to LSBFIRST fixed the fonts, thanks! Garbage in Mozilla still remains when acceleration is turned on - what other XAA bits should I look over? Not sure, read XAA.HOWTO if you haven't already. Now the remanining problem is the garbage in lower part of the screen - any ideas about that? It's there even with NoAccel and changing too. Changing what? Have you tried the modifications I suggested for the framebuffer aperture? -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
