Mark Vojkovich[EMAIL PROTECTED] wrote:
On Sat, 15 Sep 2001, hadron wrote:
Except that it doesn't work, now that I was able to test it.
The second head doesn't show any change in gamma even though
xgamma reports the newly assigned values on screen 1, screen 0
works correctly.
Works fine
Derrik Pates wrote:
Ok, not exactly related, but I wanted to find out if it would work - has
anyone been able to get more than one ATI Rage128 working in a system?
Particularly in a non-x86 system (in my case an Apple PPC G3 box)? I've
tried to get such a setup working, but XFree86
On Wed, Sep 19, 2001 at 07:52:16PM -0700, Mark Vojkovich wrote:
I'd like to propose a change to Xv standard, to add a function
XvGetImage,
which could be used to transfer data from videoram to system memory. 2
possible situations it can be used:
What's the prototype look like. Ie,
Is there an input driver for Linux's generic /dev/input/eventx
interface?
After glancing through the source and mailing list archives, it seems
that the wacom input driver does support it (see the functions with
names including USB in
programs/Xserver/hw/xfree86/input/wacom/xf86Wacom.c), but
Keith Parkins wrote:
That did it! Everything works okay except for when I quit X. The monitor
starts making a funny sound (so I shut it off) and virtual consols don't
work. Do I need to enable video drivers from BootX on the Mac side?
Doing that and using Option UseFBDev should be a
[EMAIL PROTECTED] wrote:
I have a ATI Rage 128 (AGP) and I tried to use the DRI.
Everything works well but I have the following message:
kernel: [drm:r128_do_wait_for_fifo] *ERROR*
r128_do_wait_for_fifo failed!
Make sure you are using the correct version of the kernel module. For XFree86
On Thu, 20 Sep 2001, Michel Dänzer wrote:
It should work. What version are you trying? I seem to remember Xinerama
problems in 4.1.0 which are fixed in CVS.
I'm using thhe 4.1.0-6 debs at present. The system I'm using I haven't
even gotten around to trying to enable Xinerama - it always dies
Hi,
The Gateway 9550 is claimed to have a GeForce2 GO. It does have an SXGA
display.
I've installed XFree86 4.1.0, and the two nVidia rpms from their site.
I had to rpm -ivh --force the kernel module to get it to modprobe.
I've followed the README to the letter, although I still need to
I have been trying for quite some time now to make XFree86 4.1.0 (and other
versions) display both on a CRT and the LCD of a Dell Latitude CPt/V with a
Mach64 chipset. But so far I have only managed to get it to display on either
one but not both at the same time.
The Xserver (XFree86 4.1.0)
Worked like a champ. I'll be writing this up (since it
wasn't a straight Red Hat install), and posting it to
linux-laptops.
Andy Ritger([EMAIL PROTECTED])@Thu, Sep 20, 2001 at 10:42:24AM -0700:
Hi Richard, I saw your post on the Xpert mailing list. Unfortunately,
I've never seen one of the
On Tuesday 18 September 2001 12:18, you wrote:
...and non-primary AGP is detected as having 2M RAM.
Hi, sorry to barge in here like this, but I have a similar situation.
I use a 3Dfx Voodoo3 on AGP, and an ATI 3D Rage PRO on PCI. the Voodoo is
primary.
I am having some serious issues setting
Hello,
My understanding is this chipset (I have an Inspiron) was better supported in
XF 3.3.6 !! The 'reasoning' appears to be that this chipset is now too old to
bother with !! This goes for 3D acceleration as well which seemed to be fully
supported in 3.3.6 !! All I can think is to try
Quoting Georgina O. Economou [EMAIL PROTECTED]:
Hello all:
I'll start with a classic: congratulations for the great work. As
a
developer of CaixaMagica, the first Portuguese Linux distribution
I
would
like to request some informations regarding the XFree project which
is
On Thu, 20 Sep 2001, Peter Surda wrote:
On Wed, Sep 19, 2001 at 07:52:16PM -0700, Mark Vojkovich wrote:
I'd like to propose a change to Xv standard, to add a function
XvGetImage,
which could be used to transfer data from videoram to system memory.
2
possible situations it can be
Evan Martin wrote:
Is there an input driver for Linux's generic /dev/input/eventx
interface?
snip
Has someone attempted to write a driver for it? If not, is there a good
reason I shouldn't attempt to write one? Would it belong as yet another
modification to the (rather complicated) mouse
On Thu, Sep 20, 2001 at 01:30:52PM -0700, Mark Vojkovich wrote:
Then the client API would be the same as XvGetStill but would use
an XvImage as the destination instead of a Drawable.
Er, not quite. XvGetStill seems to have a Drawable as a source and Port as a
destination. What I want is to
Hello all !
I can't find a list XVideo capable XFree86 drivers . The one I have was built
from xine users feedback. Can someone comment , add entries or say something
about future plans ?
This is my list:
3dfx
Voodoo3 (xfree 4.1)
Voodoo4 (xfree 4.1)
Voodoo5 (xfree 4.1)
Nvidia ( xfree 4.1 )
Hello all:
One thing I can't find in the documentation. Are there advantages (or
disadvantages) of using XF86_FBDev over XFree86 4.1 with fbdev driver ? Any
other relevant comments ?
Thank you very much
Gustavo Homem
---
On Thu, Sep 20, 2001 at 02:39:06PM -0700, Mark Vojkovich wrote:
Sorry, I meant XvPutStill.
aha.
There will need to be an option for a shm completion event
on XvShmGetImage so the client isn't blocked while the server
fetches the data.
I must confess I don't know the difference between
I was under the impression that the Matrox G100 that I'm struggling with
also supports Xv? If not, that will save me the continued anguish of
trying to get it to work :)
On Thu, 20 Sep 2001, Gustavo Carvalho Homem wrote:
Hello all !
I can't find a list XVideo capable XFree86 drivers . The
On Thu, 20 Sep 2001, Bob wrote:
I was under the impression that the Matrox G100 that I'm struggling with
also supports Xv? If not, that will save me the continued anguish of
trying to get it to work :)
The driver doesn't support it. Back when I wrote the Xv support
for the mga driver, I
On Thu, 20 Sep 2001, Peter Surda wrote:
On Thu, Sep 20, 2001 at 02:39:06PM -0700, Mark Vojkovich wrote:
Sorry, I meant XvPutStill.
aha.
There will need to be an option for a shm completion event
on XvShmGetImage so the client isn't blocked while the server
fetches the data.
I
Around 16 o'clock on Sep 20, Mark Vojkovich wrote:
XShmGetImage is blocking, so maybe it's not important for XvShmGetImage
to be asynchronous. Having to send the event (and receive it)
probably just increases the latency anyhow. OK, the event is
a bad idea.
The protocol isn't
On Thu, Sep 20, 2001 at 04:27:26PM -0700, Mark Vojkovich wrote:
XvPutImage pushes the data through the socket. With XvShmPutImage
(only available for local clients) data is stored in shared memory
so that the server just copies it from the client's XvImage itself.
I get it now. It seems
On Thu, 20 Sep 2001, Peter Surda wrote:
On Thu, Sep 20, 2001 at 04:27:26PM -0700, Mark Vojkovich wrote:
XvPutImage pushes the data through the socket. With XvShmPutImage
(only available for local clients) data is stored in shared memory
so that the server just copies it from the
Aok, good to know before I beat myself any further.
Thanks
On Thu, 20 Sep 2001, Mark Vojkovich wrote:
On Thu, 20 Sep 2001, Bob wrote:
I was under the impression that the Matrox G100 that I'm struggling with
also supports Xv? If not, that will save me the continued anguish of
trying to
I have a laptop with the ATI Rage Mobility Radeon-M on a Sony VAIO
PCG-GR170K. I did an lspci and this is the ID of the card. It has 8
Megs of RAM
#define PCI_CHIP_RADEON_VE 0x4C59
I got the latest XFree86 4.1.99 by doing a CVS checkout a couple weeks
ago. I am running RedHat 7.1. X is
27 matches
Mail list logo
