On Sun, 20 Jul 2003, Mike A. Harris wrote:
On Sat, 19 Jul 2003, Fred Heitkamp wrote:
If the server market is the biggest (and for Linux it is) then
only 2D support if that is required. I'd bet even the big
film studios don't use Linux to view the final rendering. They
probably use a Mac
On Sun, 20 Jul 2003, Sven Luther wrote:
Date: Sun, 20 Jul 2003 14:58:56 +0200
From: Sven Luther [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
Subject: Re: Rant (was Re: ATI Drivers.)
I've responded to Sven off list, simply because
The 'Athlon related mystery' thread concluded by recommending the
removal of O_SYNC on the open to /dev/mem to solve performance problems
in SuSE's XFree86 packages [1]. I still have many users with similar
performance problems, and I want to know how to better debug it.
1. A SuSE user with
On Sun, 20 Jul 2003, Richard A. Hecker wrote:
I encounter this all the time. If someone asks me Why does your
product version x.y not support foo? and I delete their mail,
they are none the wiser. They are unlikely to flame me, or to
even know if I got it.
I will add my own Rant here.
On Mon, 2003-07-21 at 13:29, Billy Biggs wrote:
1. A SuSE user with a Radeon 8500, P4 1.8, that gets 133fps with
xvtest, but seemingly good performance from x11perf -shmput500 [2].
The radeon driver uses the CP for image writes, does
Option XaaNoScanlineImageWriteRect
have a
Michel Dänzer ([EMAIL PROTECTED]):
On Mon, 2003-07-21 at 13:29, Billy Biggs wrote:
1. A SuSE user with a Radeon 8500, P4 1.8, that gets 133fps with
xvtest, but seemingly good performance from x11perf -shmput500 [2].
The radeon driver uses the CP for image writes, does
On Thu, 2003-07-17 at 23:25, Chris Edgington wrote:
Working on my last known bug in the SM731 support in the siliconmotion
driver. Using the current siliconmotion driver and my newly modified driver
on the SM722 hardware, running TuxRacer from RH9 works fine. TuxRacer (or
probably more
This is with RedHat 6.2.
The latest IPv6 fixes allow X to compile, but remote connections
no longer work on a machione without IPv6 configured.
I've recompiled with XTRANSDEBUG set high (5 I think):
% xbiff -display localhost:0
_X11TransOpenCOTSClient(tcp/localhost:0)
This could easily be integrated in the driver (it would be much more
easy to do than writing a separate program) but like you say in your
disclaimer: we cannot guarantee that nothing bad happens. Therefore
I don't think it is the way to go.
However what I find more interesting is that you updated
Dr Andrew C Aitchison wrote (in a message from Monday 21)
This is with RedHat 6.2.
The latest IPv6 fixes allow X to compile, but remote connections
no longer work on a machione without IPv6 configured.
I've recompiled with XTRANSDEBUG set high (5 I think):
% xbiff -display localhost:0
On Mon, Jul 21, 2003 at 08:04:56AM -0400, Mike A. Harris wrote:
On Sun, 20 Jul 2003, Richard A. Hecker wrote:
I will add my own Rant here. Ignoring email from Joe Public who
bought his 'Puter from Walmart' might work, but I feel 'Dissed'
when a person insults my intelligence with this
55 Percent off all printer supplies!
Please see my stores and feel what
others have already, the best ink cartridges
at a great price.
We offer all brands including,
HP, Epson, Canon, and Lexmark
http://smart-pr1nt1ng-suppl1es.com/neb.html
=
wish to stop further
On Mon, 21 Jul 2003, Billy Biggs wrote:
The 'Athlon related mystery' thread concluded by recommending the
removal of O_SYNC on the open to /dev/mem to solve performance problems
in SuSE's XFree86 packages [1]. I still have many users with similar
performance problems, and I want to know
On Mon, 21 Jul 2003, Billy Biggs wrote:
Mark Vojkovich ([EMAIL PROTECTED]):
2. An i815 with a Celeron 800, MX3S-T motherboard. Gets about 60fps
using xvtest, 273 blits/sec with x11perf -shmput500 at 16bpp, using
Gentoo xfree-4.3.0-r2. Does not use O_SYNC on /dev/mem.
Mark Vojkovich ([EMAIL PROTECTED]):
While I'm at it, how hard do you think it would be to do triple
buffering in the NVIDIA driver for this same problem?
NVIDIA hardware can only double buffer. Using more buffers than two
would require queuing them up and programming the new buffers in
Win:
I agree with the spirit of your statement, but I don't want the government
involved in any part of what I do for a living or a hobby.
I agree that M$'s size is a problem now, but I am certain that they will
not be dominant forever. Large companies do fail, and they do get smaller.
JC
On Mon, 21 Jul 2003, Billy Biggs wrote:
Mark Vojkovich ([EMAIL PROTECTED]):
While I'm at it, how hard do you think it would be to do triple
buffering in the NVIDIA driver for this same problem?
NVIDIA hardware can only double buffer. Using more buffers than two
would require
Mark Vojkovich ([EMAIL PROTECTED]):
On Mon, 21 Jul 2003, Billy Biggs wrote:
Mark Vojkovich ([EMAIL PROTECTED]):
While I'm at it, how hard do you think it would be to do triple
buffering in the NVIDIA driver for this same problem?
NVIDIA hardware can only double buffer.
On Mon, 21 Jul 2003, Billy Biggs wrote:
Mark Vojkovich ([EMAIL PROTECTED]):
On Mon, 21 Jul 2003, Billy Biggs wrote:
Mark Vojkovich ([EMAIL PROTECTED]):
While I'm at it, how hard do you think it would be to do triple
buffering in the NVIDIA driver for this same problem?
Billy Biggs [EMAIL PROTECTED] wrote:
Are there more hardware or BIOS configurations can I check that can
change video memory performance? These XVIDEO drivers usually do nothing
more than a memcpy(), at least for SiS and i815. My list:
- MTRRs enabled (they almost always are).
-
Sven Luther [EMAIL PROTECTED] wrote:
Why do these companies not open source their complete drivers?
Because they have intellectual property in their drivers that
As if their concurent where not capable of reverse engineering the
drivers.
And if they did and they got caught, their
Mark Vojkovich [EMAIL PROTECTED] wrote:
The FastWrite capability of P4 processors greatly increases the
CPU throughput to the framebuffer.
You mean the FastWrite capability of the AGP bus/card in AGP4x/8x specs,
or are you talking about something different and specific to P4
processors?
Title: Message
Hello
Everyone!
Iam writing a driver
for 69030 card.
I have to support
CIF and QCIF formats.
1. The format says
that a frame rate of 30fps is required for both.
2.Each frame should
have
a. 144
lines and 176 pixels/line for QCIF.
b.288 lines and 352 pixels/line for
23 matches
Mail list logo
