Mike Mestnik wrote:
> If you man ascii, which on a hunch I did, you will find that...
> Hex Char
> 51Q
> 57W
> 4CL
> 45E
>
> Hence QW 0x5157, QL 0x514C, and the LE would have Product ID 0x4C45 this product ID
>is not on
> file.
> I'll look into why the Xserver it equating 0x4C4
On July 10, 2002 09:29 pm, Mike Mestnik wrote:
> #
> # List of PCI ID's
> #
> # Maintained by Martin Mares <[EMAIL PROTECTED]> and other volunteers from
> the # Linux PCI ID's Project at http://pciids.sf.net/. New data are
> always # welcome (if they are accurate), we're ea
On Thu, 11 Jul 2002, Stefan Lange wrote:
> compiling from cvs shouldn't be a problem, I just followed the DRI
> Compilation Guide from the website and everything went fine (you might
> have to compile the kernel drm-module manually, but that's no trouble)
>
Completed the compile didn't help me
On Wed, 2002-07-10 at 20:15, Mike Mestnik wrote:
> If you man ascii, which on a hunch I did, you will find that...
> Hex Char
> 51Q
> 57W
> 4CL
> 45E
>
> Hence QW 0x5157, QL 0x514C, and the LE would have Product ID 0x4C45 this product ID
>is not on
> file.
> I'll look into why
If you man ascii, which on a hunch I did, you will find that...
Hex Char
51Q
57W
4CL
45E
Hence QW 0x5157, QL 0x514C, and the LE would have Product ID 0x4C45 this product ID is
not on
file.
I'll look into why the Xserver it equating 0x4C45 to 0x5157. I was working on having
th
#
# List of PCI ID's
#
# Maintained by Martin Mares <[EMAIL PROTECTED]> and other volunteers from the
# Linux PCI ID's Project at http://pciids.sf.net/. New data are always
# welcome (if they are accurate), we're eagerly expecting new entries,
# so if you have anythin
On Thu, 11 Jul 2002, José Fonseca wrote:
> On Wed, Jul 10, 2002 at 10:00:38AM -0400, Allen Barnett wrote:
> > Hi (José and Leif),
> >
> > I'm testing the Mach64 driver on my laptop, which uses a Rage Mobility P/M
> > AGP 2x (rev 64). I'm using the binary snapshot from 2002/7/8.The
> > render/v
On Wed, Jul 10, 2002 at 10:00:38AM -0400, Allen Barnett wrote:
> Hi (José and Leif),
>
> I'm testing the Mach64 driver on my laptop, which uses a Rage Mobility P/M
> AGP 2x (rev 64). I'm using the binary snapshot from 2002/7/8.The
> render/version string is:
> Mesa DRI Mach64 20020227 [Rage Pro
> "Stefan" == Stefan Lange <[EMAIL PROTECTED]> writes:
Stefan> cvs). X starts up fine for me, and 3D also works to some extent
Stefan> (glxgears, glx-screensavers work for example, but q3a, wolf and so on
Stefan> crash after a few minutes of playing). I still got some trouble wi
Michal Kozlowski wrote:
> Hi Stefan, good to hear someone got it working. I'll give the
> r200-0-1-branch a shot, see if I can compile it and get it running. Would
> there be a problem if I had the radeon_dri modules still in the module/dri
> directory (I'll try removing it)
>
if you recompile
Hi Stefan, good to hear someone got it working. I'll give the
r200-0-1-branch a shot, see if I can compile it and get it running. Would
there be a problem if I had the radeon_dri modules still in the module/dri
directory (I'll try removing it)
>
> Did you take a look at /var/log/XFree86.0.log,
Alexander Stohr wrote:
>>I just set up a 2nd PC and ssh'd into mine and ran Tribes 2.
>>My original post said that the lockups occur within 5 seconds of 3D
>>rendering starting. That's not quite correct.
>>The lockups occur only after I move the mouse (which moves
>>the 3D scene
>>around). But
it heavily to support devfs) then I got
>the rest of DRM
>>from http://dri.sourceforge.net/snapshots/radeon-20020710-linux.i386.tar.bz2 I have
>a 7500 QW
>>though.
>>
>>I'l get my 8500 ought of that windowz box and run some tests, K.
>
t; Yes, I had a simular problem, rebooted and every thing was fine.
> I got my kernel mod from cvs (and patched it heavily to support devfs) then I got
>the rest of DRM
> from http://dri.sourceforge.net/snapshots/radeon-20020710-linux.i386.tar.bz2 I have
>a 7500 QW
> though.
>
Yes, I had a simular problem, rebooted and every thing was fine.
I got my kernel mod from cvs (and patched it heavily to support devfs) then I got the
rest of DRM
from http://dri.sourceforge.net/snapshots/radeon-20020710-linux.i386.tar.bz2 I have a
7500 QW
though.
I'l get my 8500 ought of
Hi,
I have a problem when I start X with dri and the radeon_drv module loaded
I lose my video signal I can still log onto the system remotely and get
the log from the startup, here is where is stops.
(II) RADEON(0): Using 8 MB AGP aperture
(II) RADEON(0): Using 1 MB for the ring buffer
(II) RAD
It seams that pci_find_device, that DRI uses, has been replaced. This really doesn't
affect DRI
but it's new and the Linux driver would more closely resemble the BSD one once were
doing things
the new way. Also this will pave the road for my next big idea, changing the card%d
device names
to
> Ehm. Are you disabling 2D accel in XF86Config (see the readme about it)?
No, but I'm hanging my head in shame because I ever read the post where
you talked about using the same 2D/3D locking trick as the mach64 driver.
I'll go read now...
Cheers,
David
--
Hi (José and Leif),
I'm testing the Mach64 driver on my laptop, which uses a Rage Mobility P/M
AGP 2x (rev 64). I'm using the binary snapshot from 2002/7/8.The
render/version string is:
Mesa DRI Mach64 20020227 [Rage Pro] AGP 2x x86/MMX/SSE 1.2 Mesa 4.0.3
You guys have done some really outstand
Mike A. Harris wrote:
> On Tue, 9 Jul 2002, José Fonseca wrote:
>
>
>>Date: Tue, 9 Jul 2002 22:09:58 +0100
>>From: José Fonseca <[EMAIL PROTECTED]>
>>To: [EMAIL PROTECTED]
>>Content-Type: text/plain; charset=iso-8859-1
>>List-Id:
>>Subject: IRC Meetings & ML notification
>>
>>First I would like
This is the first draft of my devfs patch, it moves *most* of the PCI ids into the
shared tree.
gamma_drv.h has both a linux and bsd copy of the PCI ids. Some cards like the
i8{1,3}0 we don't
know the PCI ids. I have tested that it compiles under Linux(Debian) and correctly
makes and
removes
21 matches
Mail list logo
