Hello etienne,
You seem to have two problems. One I think is easy to solve, another
I think is very difficult.
At 2003\01\23 10:45 +1100 Thursday, etienne deleflie wrote:
My application uses hardware acceleration (using xv) to draw YUV to
screen using XvShmPutImage(...)
Video
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
Title: glapi_x86.S glx86asm.py
according to its headline glapi_x86.S was generated
by the script glx86asm.py - its just that i cannot
find that script in the XFree86 sources. Any hints?
-Alex.
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
Hello all,
I have the following Problem with a silicon motion Lynx3DM (smi 721) chip when
using Xv.
It looks like the hardware color conversion is not supported. With a nvidia
gforce2 and the nvidia driver, I can see 4 suppoerted Image formats (YUY2,
YV12, UYVY, YUV(packed), YUV(planar)).
On Thu, 30 Jan 2003, Alexander Stohr wrote:
according to its headline glapi_x86.S was generated
by the script glx86asm.py - its just that i cannot
find that script in the XFree86 sources. Any hints?
From CVS/XFree86/xc/extras/Mesa/bin/Attic/glx86asm.py,v
revision 1.2
date: 2000/12/07
On Thu, 30 Jan 2003, Alexander Stohr wrote:
From CVS/XFree86/xc/extras/Mesa/bin/Attic/glx86asm.py,v
really? hmm, if the respective API listing ever changes or extends
it might be simpler to use an existing script and then submitting the
results
than to perform error prone copy and paste
On Thu, 30 Jan 2003, Harold L Hunt II wrote:
...how would you do it, in 150 words or less?
Seriously, I have been working on this for over a year and I would love to
hear some of the ideas that people have because I am completely stumped on
how to make such a clipboard manager work
Alexander Stohr wrote:
From CVS/XFree86/xc/extras/Mesa/bin/Attic/glx86asm.py,v
revision 1.2
date: 2000/12/07 16:12:47; author: dawes; state: dead; lines: +0 -0
Remove from the trunk the Mesa files that aren't needed.
Latest entry in cvs log of c/extras/Mesa/src/X86/glapi_x86.S
revision 1.7
You'd have to ask Brian to be sure, but I believe the
intention is that
if the interface ever changes, a new .S file be generated in the Mesa
tree and imported to the XFree86 DRI trees. There should
never be a
case where the .S file would change in XFree86 and not change in Mesa.
Andrew,
Thanks for responding.
Yes, there are at least 3 clipboard/cut-buffer mechanisms. We
originally set out to watch for CUT_BUFFER0 to change, at which point we
would copy it to the Windows clipboard. That seemed fine, except that
non-U.S. users screamed bloody murder because
Harold L Hunt II [EMAIL PROTECTED] writes:
...how would you do it, in 150 words or less?
Seriously, I have been working on this for over a year and I would love to
hear some of the ideas that people have because I am completely stumped on
how to make such a clipboard manager work properly.
Owen,
Owen Taylor wrote:
Harold L Hunt II [EMAIL PROTECTED] writes:
...how would you do it, in 150 words or less?
Seriously, I have been working on this for over a year and I would love to
hear some of the ideas that people have because I am completely stumped on
how to make such a clipboard
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
On Thu, Jan 30, 2003 at 11:14:13PM +1100, etienne deleflie wrote:
thanks for your reply. I'm not sure that we are talking about the same
thing though.
I want to be able to control the refresh rate programatically. for a
piece of software used in live video performance.
I dont know
what about syncing to the vertical blank?
some cards do provide you an interrupt handler for this.
i mean if you want to do it with OpenGL in fullscreen anyways
then you just have to use double buffered mode and call glSwap()
anytimes you are done with rendering.
if you want to do something more
Hi
I just recognized, that the xclock docs (manual page and --help
option) are not up-to-date. Looks like that -fn option only works if
you also specify -norender (Xserver rendering). -fa option works
for specifying (antialiased) fonts rendered by Xft2/freetype2.
Best regards,
Stefan
Public Key
- Original Message -
From: Owen Taylor [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 30, 2003 12:30 PM
Subject: Re: If you were writing a Windows and X clipboard integration
manager...
Harold L Hunt II [EMAIL PROTECTED] writes:
...how would you do it, in 150 words
- Original Message -
From: Harold L Hunt II [EMAIL PROTECTED]
To: G O Economou [EMAIL PROTECTED]
Sent: Thursday, January 30, 2003 1:01 PM
Subject: Re: If you were writing a Windows and X clipboard integration
manager...
Oh, but I have already release something:
On Thu, Jan 30, 2003 at 03:11:08PM -0500, G O Economou wrote:
In fact, I have made 8 releases :) I originally copied text from
CUT_BUFFER0, which worked fine for me. As soon as I released this
people started complaining about what it did not do (namely, it didn't
handle non-U.S. text).
Harold L Hunt II [EMAIL PROTECTED] writes:
Owen,
Owen Taylor wrote:
Harold L Hunt II [EMAIL PROTECTED] writes:
...how would you do it, in 150 words or less?
Seriously, I have been working on this for over a year and I would love to
hear some of the ideas that people have because I am
Havoc,
Havoc Pennington wrote:
On Thu, Jan 30, 2003 at 03:11:08PM -0500, G O Economou wrote:
In fact, I have made 8 releases :) I originally copied text from
CUT_BUFFER0, which worked fine for me. As soon as I released this
people started complaining about what it did not do (namely, it
PCI-gart is a still developing component
that is maintained in the XFree86 3D instable tree,
which is better known as dri-devel project.
you might have better chances when asking there.
anyways, that far i do know about PCI-gart,
it was under some rather vague development.
there were more
Hi,
On Thu, Jan 30, 2003 at 10:40:12PM +, Markus Kuhn wrote:
What would be the best starting point to write a SunRay driver for
XFree86? What interface is there and where is it documented? Does
XFree86 split nicely into a hardware dependent and hardware independent
layer and is that
On 30 Jan 2003, Nolan Leake wrote:
While poking around the tree, I happened across the reason why
RENDER acceleration was screwed up on dualhead G[45][05]0s.
xaaStateChange.c was not calling RestoreAccelState before doing
CPUToScreenTexture and CPUToScreenAlphaTexture.
This patch fixes that,
Alexander Stohr wrote:
what about syncing to the vertical blank?
some cards do provide you an interrupt handler for this.
what is the vertical blank ? . do you know somewhere where I can
get more information on this?
i mean if you want to do it with OpenGL in fullscreen anyways
then
On Thu, 30 Jan 2003, Harold L Hunt II wrote:
See also this thread:
https://listman.redhat.com/pipermail/xdg-list/2002-November/000881.html
And Keith's X extension to monitor selection changes, though this
won't be in 4.3.
Wow! That looks really cool and it is already in the tree as
xfixes,
27 matches
Mail list logo
