On Sat, 20 Aug 2005, Dave Airlie wrote:
In for a penny in for a pound, (old saying..) i.e. if I could do that I
would have working 3D... the CP crashes on startup...
I assume that you have a version of PCIGART working, right ? You can test
this
using MMIO by doing bitblt from GART
http://bugzilla.kernel.org/show_bug.cgi?id=2754
--- Additional Comments From [EMAIL PROTECTED] 2005-08-21 02:54 ---
Sorry, i can't test it.
I changed notebook model and vendor, so i can't help with report in
future.
Thanks
--
sign: Josef Rysanek (ailas) [EMAIL PROTECTED]
www:
nope a working PCIEGART isn't the same as a working PCIGART, I have
all the information I think I need (though an R42x 2D programmers guide as
opposed to the R42x regref would help a bit), I just can't connect the
dots... I also suffer from the fact that fglrx doesn't work on my PCIE
On Sun, 21 Aug 2005, john wrote:
hi!
i'm not too experienced in programming, but here it goes: but i've been able
to check out the Mesa cvs and the r300 cvs. i've been trying for quite a long
time, to compile r300 Mesa drivers. the drm works fine from r300 cvs, but i
cant get mesa to compile.
Ian Romanick a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There's been quite a bit of discussion about this on #dri-devel the past
few days. I thought I'd write up a quick summary and post it to the
list. I know that there are a lot of interested parties that are on the
list, but
hi!
i'm not too experienced in programming, but here it goes: but i've been able
to check out the Mesa cvs and the r300 cvs. i've been trying for quite a long
time, to compile r300 Mesa drivers. the drm works fine from r300 cvs, but i
cant get mesa to compile. if i try to compile the r300 code
The few sources I've read have said that the hardware for AGP, and PCI-E
was designed to emulate the software interface of PCI so that the
underlying hardware would be transparent to software. This can be seen
in the output of lspci, where my marginally supported R200 (Where's
6.2.2 when you need
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4150
--- Additional Comments From [EMAIL PROTECTED] 2005-08-21 11:24 ---
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4150
--- Additional Comments From [EMAIL PROTECTED] 2005-08-21 11:28 ---
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4150
--- Additional Comments From [EMAIL PROTECTED] 2005-08-21 11:34 ---
(In
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4150
[EMAIL PROTECTED] changed:
What|Removed |Added
I picked up an X800 XL a few days ago. Apparently ATI is using a
different chipset than the previously-tested X800 board mentioned on
the r300 website; this one has an R430 in it.
01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 554d
01:00.1 Display controller: ATI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Dodge wrote:
| libGL error: dlopen .../r300_dri.so failed (.../r300_dri.so:
undefined symbol: _glapi_add_dispatch)
Hmm.. you have LD_LIBRARY_PATH pointing to a libGL from CVS, right?
That's the problem I had, but it sounds like everything
Now the bad stuff:
- Some programs run without acceleration. LIBGL_DEBUG=verbose reports
things like:
libGL error: dlopen .../r300_dri.so failed (.../r300_dri.so: undefined
symbol: _glapi_add_dispatch)
Did you install Mesa from CVS ? There were quite a few big change in CVS
and one
My understanding of bus operation is that it's sole function is to
provide memory mapped IO, IO ports, and interrupt control, after these
features are configured -- by the BIOS -- software only has to worry
about the device at the other end... After this initial configuration,
so I thought,
I'm curious if anyone has gotten r300 working on FreeBSD now that the
driver has been merged with Mesa and the DRM cvs tree?
I managed to get Mesa CVS to build on FreeBSD with some help from Adam
Jackson and Daniel Stone on irc today. DRM from the cvs tree compiled
as well. The kernel
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4150
--- Additional Comments From [EMAIL PROTECTED] 2005-08-21 16:44 ---
I
And so on, through /dev/dri/card254
Mind you, /dev/dri/card0 exists:
[ [EMAIL PROTECTED] - ~ ]: ls -la /dev/dri
total 1
dr-xr-xr-x 2 root wheel 512 Aug 21 18:37 .
dr-xr-xr-x 5 root wheel 512 Dec 31 1969 ..
crw-rw-rw- 1 root wheel0, 162 Aug 21 18:35 card0
Any ideas?
Is
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4150
--- Additional Comments From [EMAIL PROTECTED] 2005-08-21 17:44 ---
(In
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4150
--- Additional Comments From [EMAIL PROTECTED] 2005-08-21 17:45 ---
I
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4150
--- Additional Comments From [EMAIL PROTECTED] 2005-08-21 18:46 ---
(In
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=4150
--- Additional Comments From [EMAIL PROTECTED] 2005-08-21 20:49 ---
(In
22 matches
Mail list logo
