I'm trying to get s3 virge to work on PPC (PowerMac with PCI) - a
bigendian platfornm. Stock s3virge driver compiles fine and runs without
crashing but knows nothing about bigendian so the colors & images are
"mildly" distorted.
I asked xpert list for advice and got some. With that in mind I
devel
On Mon, Jan 20, 2003 at 07:57:20PM +0200, Meelis Roos wrote:
[..]
> If somebody has some programming information about virge family and is
> free from NDA-s, I would very much like to get a copy - the only source
> I had right now is a letter form Ani Joshi and kgi source.
Hmm, I have a pdf, but I
On Mon, Jan 20, 2003 at 07:29:00PM +0100, Bernd Ernesti wrote:
>On Mon, Jan 20, 2003 at 07:57:20PM +0200, Meelis Roos wrote:
>[..]
>> If somebody has some programming information about virge family and is
>> free from NDA-s, I would very much like to get a copy - the only source
>> I had right now
Title: RE: s3virge & bigendian
> >Hmm, I have a pdf, but I think I got it from the xfree86 ftp
> devel area,
> >so I'm not sure about the status right now.
>
> If you got it from there, then you can't redistribute it. If you get
> it from another (no
Title: RE: s3virge & bigendian
> +
> +#if X_BYTE_ORDER==X_BIG_ENDIAN
> + pScrn->fbOffset = 32*1024*1024; /* bigendian aperture is at 32M */
> +#else
> + pScrn->fbOffset = 0;
> +#endif
> + pScrn->memPhysBase = ps3v->
On Mon, Jan 20, 2003 at 08:34:51PM +0100, Alexander Stohr wrote:
>> >Hmm, I have a pdf, but I think I got it from the xfree86 ftp
>> devel area,
>> >so I'm not sure about the status right now.
>>
>> If you got it from there, then you can't redistribute it. If you get
>> it from another (non-NDA)
On Mon, 20 Jan 2003, David Dawes wrote:
> On Mon, Jan 20, 2003 at 08:34:51PM +0100, Alexander Stohr wrote:
> >> >Hmm, I have a pdf, but I think I got it from the xfree86 ftp
> >> devel area,
> >> >so I'm not sure about the status right now.
> >>
> >> If you got it from there, then you can't redist
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 mozil
> 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
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
> > 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.
Will do.
> > Now the remanining problem is the garbage in lower part of the screen -
> > any ideas about that? It's there even wit
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 aper
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 fix
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 fr
> The virge supports a seperate config for little/bigendian memory
> mapping, so this might be a better choice than adding 32M as you
> suggest.
Can you elaborate a litte?
--
Meelis Roos ([EMAIL PROTECTED])
___
Devel mailing list
[EMAIL PROTECTED]
htt
> > 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 fli
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.
> >
> > If you have accel enabled, but then use 'sw_cursor' option, does the
> > noise still appear?
>
> Yes. Just movin
> 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 ad
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 conta
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 wo
> 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
21 matches
Mail list logo
