- Original Message -
From: netpython [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, February 04, 2004 9:38 AM
Subject: *** GMX Spamverdacht *** Re: *** GMX Spamverdacht *** Re:
Manufacturers who fully disclosed specifications for agp cards?
[...]
(reverse engineering)
Are
Subject: *** GMX Spamverdacht *** Re: Manufacturers who fully disclosed
It is possible to gain the specs for a chip by discetion for i.e R300
chip or NV 30 chips with the right tools like a electon microscope?
full specifications as the headline does say is more than just the
register
tryout the closed source drivers from ATI´s website.
if you find out about any problem then call either
ATI or SuSE support on them. they must have a solution.
-Alex.
- Original Message -
From: William W. Austin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, December 28, 2003 11:47
the _ is the mailmain default but can be canged.
only the fglrx closed source drivers from ATI
for the i386/Linux platform do have 3D.
Databooks are no longer state of the art
in the information technologies age.
On Wednesday 10 December 2003 12:48, wim delvaux wrote:
Any idea
I have tried these drivers but refuse to work.
They think I have an (unsupported) OEM card (=powered by ATI)
while according to the identity check programs
run under XP it 'should' be an ATI one (=Built by ATI)
There is no general OEM barrier anymore.
It only was it
I suppose I could have a hardware problem, since my PC is a
couple years
old now. However, I can leave the same computer just running a 2.4.x
kernel for days with no problems. Would the redesigned kernel
2.6.x bang the hardware so much more; going beyond that of
kernel 2.4.x?
It can be
I always get these errormessage when I load agpgart and fglrx
and then startx.
The weird thing is that X starts up with this gray screen and
the mouse
working. It only crashes the instant when the KDE dialog
should be coming up.
(==) Using config file: /etc/X11/XF86Config-4
(WW)
run ldd on your glxgears or glxinfo executables and see
which libGL it
is using.
It is using the ones from the driver. It uses libGL which
points to a link
which is the drvier lib. I made a diff on the file which is
in the driver
directory and the installed libGL.so.1.2 and they are
I tried just leaving the display running without doing anything
interactive with the interface and X ran for several hours before
freezing. All that was running was Xscreensaver. I then tried
again using
X normally but with a different window manager (XFCE 4) and
it worked for
about an
Hello,
i stumbled across the above mentioned define and
related code in the XFree86 sources (lnx_video.c).
comparing X4.1.0 and X4.3.0 i found that the
condtitnal coding of if (base % size) has
vanished at some point in time and the handling
is now hardcoded at this code location.
to my best
This is the minimum work to get this program into ansi shape.
This patch is
ready for inclusion. If their are no objections to the patch,
it would be
very nice to get this in ASAP. It will make some other projects I am
working on go smoother.
Thanks, Warren Turkal
i have no reason to
CP mode means using an engine on the chip
that gets the command data from main memory
by itselves, some sort of busmaster DMA stream.
MMIO means that the driver does program the
chipset directly via its memory mapped registers.
DRI means direct rendering and is the most common
socket for current
(WW) RADEON(0): monitor1: Using default hsync range of 28.00-33.00kHz
(WW) RADEON(0): monitor1: using default vrefresh range of 43.00-72.00Hz
(II) RADEON(0): Clock range: 20.00 to 350.00 MHz
(II) RADEON(0): Not using default mode 800x600 (hsync out of range)
(II) RADEON(0): Not using mode
I have laptop with 320m radeon. radeonfb didn't seem
to work for it on 2.4.21. Has this changed in 2.6.0-test2?
this is the XF86 development mailing list
for the XF86 windowing system infrastructure.
there are other people around that do
work on the framebuffer device support.
you might
just a short comment on the illustrations...
Mode 1: (fixed width font required for viewing)
+--+
|++ +-+|
||| | ||
||| | ||
||
I'm running XFree 4.3.99.8 with kernel 2.6.0.test2 on a via M1
motherboard.
I loaded the modules for mtrr, i2c and agpgart for via.
Into XF86Config I choose via driver
When I start X there's always this warning:
(WW) via(0): Failed to set up write-combining range (0x
I tried
mobile devices will always have more limitations,
so you wont get rid of any sort of low bpp formats.
in multi buffer environments, such as OGL with front,
back, depth, stencil, overlay, whatever you will be
in need to deal with any sort of pixel depth at the
same time as well.
for imaging
from 24 hours to 7 days depending on complexity
and on people having time working on it.
-Alex.
-Original Message-
From: Sven Goethel [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 24, 2003 19:17
To: [EMAIL PROTECTED]
Subject: patch procedure ..
sorry for being lazy and not
On Fri, 18 Jul 2003, Mark Vojkovich wrote:
For consumer desktop that's true. There is one potential business
case in the professional desktop market. SGI's, HP's and Sun's old
workstation customers have been moving over to Linux.
Thats no market secret to anyone at all. You just
From: William Suetholz [mailto:[EMAIL PROTECTED]
Mr. Harris, yes I am one of Those people who want a device to work
in my chosen operating system,
/me wants Commodore 64 - BASIC BIOS 2.0 support, call it my favorite!
Cool machine, boots in 2 seconds to a fully useable prompt.
It must be an
From: Mike A. Harris [mailto:[EMAIL PROTECTED]
I plan on replacing the Cards database in Red Hat Linux with a
new mechanism sometime in the future which will be much more
flexible, allow per architecture overrides, allow the config tool
to know what hardware supports DRI and on what specific
I dont really know driver or chipset in detail,
but its the way that it needs programming so
that the timing for the LCD does match. black
or striped or whatever effects do indcate
wront timing for the flat pane display.
If the device is capable of dual head in other
OS condtions then it can do
i am seeing constructs like this at
several locations of the XFree86 sources:
*.h:
extern char *Xpermalloc(
#if NeedFunctionPrototypes
unsingend int /* size */
#endif
);
*.c:
char *Xpermalloc(unsigned int length)
{ ... }
#if NeedFunctionPrototypes
XrmQuark
[snipped the patch]
Is there a better way to submit patches like this? I've just
subscribed
to the devel list in the last 10 minutes :).
Fred Clift
sending to [EMAIL PROTECTED] queues your patch for integration.
maybe unified diffs are the prefered style (diff -u src dst).
it improves
RandR integration with partial enable of features?
-Original Message-
From: Alan Hourihane [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 19, 2003 12:15
To: [EMAIL PROTECTED]
Subject: RELNOTES for 4.3.0
Here's a list of items for the RELNOTES for 4.3.0, if anyone
has
Gatos is focussing on video and TV playback,
TV/video-in functionality and video capture.
But they are _not_ focussed on 3D to my understanding.
thanks for the link to the AIW Radeon 9700 comments.
the text outlines that even gatos has not timeframe
how their development will proceed.
for my
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?
www.opengl.org is of course some central place
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.
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.
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
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
31 matches
Mail list logo
