i might be able to get time to move the i810 to texmem soon, firstly as
Keith has let me know, I need to move the i810 to using its own texture
formats (it's still stuck back in the mesa3.4 days)...
so is there a set of comphrensive tests that I can run before and after to
make sure that I
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-22-07 07:21 ---
Thank you Hui for doing this,
The kernel patch does not apply cleanly to vanilla 2.4.18 neither 2.4.19. I
applied it by hand against 2.4.18(*) whitch is the most close
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-22-07 09:04 ---
Hi Hui,
I also tried your patches, but with different success. The kernel patch worked ok
for me (vanilla 2.4.18, nu patch problems). AGP and DRM initialize fine.
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-22-07 10:03 ---
Thanks for testing. One thing I can think of about the error you got is that
you might have loaded the original radeon dri module come with the Linux kernel
source. This
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-22-07 10:22 ---
Thanks for testing.
Thank you for your work Hui,
One thing I can think of about the error you got is that you might have
loaded the original radeon dri module come
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-22-07 10:32 ---
Hi Wouter, my previous message is the reply to Frederik Nosi (you got in before
I sent). You may have the same problem as Frederik -- loaded the original radeon
DRI kernel
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-22-07 11:44 ---
The correct thing to do then would be to bump the DRM minor version and only
attempt to initialize the DRI on IGP chips if the DRM has high enough a minor
version.
--
On Tue, 2003-07-22 at 07:06, Leigh Dyer wrote:
I've just been lucky enough to get a 1Ghz Powerbook G4 with 64Mb Radeon
Mobility 9000 to work on,
Great machine, isn't it? :)
and I've been having a little trouble getting X and DRI working
nicely. The process so far has been:
1.
I don't think we can get away with breaking older clients, though this does
look like it would only break the situation where you have old 3d client with
new 2d driver, which is a slightly unusual situation.
The real question is how much does the 3d client actually rely on the radeon
memory
On Tue, 2003-07-22 at 23:53, Keith Whitwell wrote:
I don't think we can get away with breaking older clients, though this does
look like it would only break the situation where you have old 3d client with
new 2d driver, which is a slightly unusual situation.
Yes, I think the 2D driver and in
Hi.
I have a Radeon:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY
[Radeon 7000/VE] (prog-if 00 [VGA])
Subsystem: Palit Microsystems Inc.: Unknown device 5159
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping+ SERR- FastB2B-
On Wed, 2003-07-23 at 00:42, Daniel Kasak wrote:
I'm using XFree86-4.3.0 compiled with the latest Gentoo ebuild.
Everything works fine at home ( with my Radeon 64MB DDR VIVO ), but here
at work DRI only works as root. As a normal user, glxinfo gives me:
name of display: :0.0
libGL
Michel Dänzer wrote:
On Wed, 2003-07-23 at 00:42, Daniel Kasak wrote:
I'm using XFree86-4.3.0 compiled with the latest Gentoo ebuild.
Everything works fine at home ( with my Radeon 64MB DDR VIVO ), but here
at work DRI only works as root. As a normal user, glxinfo gives me:
name of display:
http://www.skynet.ie/~airlied/patches/dri/i810_tex_upload.diff
I used the texenv demos from Mesa 5.0 to test this, I tested it with the
old driver and this one, and they both look the same..
however neither of them show the intensity row like my Nvidia card on my
main desktop .. on the i810 I
http://bugs.xfree86.org/show_bug.cgi?id=314
--- Additional Comments From [EMAIL PROTECTED] 2003-22-07 22:49 ---
The patch doesn't really break any existing code. You can apply the patch and
all supported cards should still work (if not, it's a bug). I've tested a 7500
breifly with
15 matches
Mail list logo
