it finally works; the problem was that indeed the r100 driver was loaded,
and not the r200 driver: radeon_drv.o was the correct version, though.
the cause hid one level deeper: radeon_drv.o correctly identified the
chip as belonging to the r200_family, but we had built a libGL w/
built-in dri
On Fri, Nov 14, 2003 at 10:33:07AM +0200, Ville Syrjälä wrote:
> On Tue, Nov 11, 2003 at 10:50:01AM -0800, Ian Romanick wrote:
> > Any idea how tough it will be (or if it's possible!) to add support for
> > ARB_texture_non_power_of_two? Bascially, it just extends the regular
> > texture modes to
On Sun, Nov 16, 2003 at 03:16:50PM +, Alan Cox wrote:
> On Sul, 2003-11-16 at 12:05, Ville Syrjälä wrote:
> > And apparently it's nobody's job to fix the bugs...
> >
> > > Furthermore, developer relations ignores any questions about
> > > the Parhelia period. :(
> >
> > Developer relations i
On Sul, 2003-11-16 at 12:05, Ville SyrjÃlà wrote:
> And apparently it's nobody's job to fix the bugs...
>
> > Furthermore, developer relations ignores any questions about
> > the Parhelia period. :(
>
> Developer relations ignore all questions/requests :( They even removed the
> developer relati
Am 2003.11.15 20:46:01 +0100 schrieb(en) Peter Meffer:
> after a long odyssey getting xfree86 dri to work (seemingly), everything
> behaves as expected, except that the gl window (also fullscreen) remains
> black; fps is being reported as usual (4300), no error messages appear,
> neither in the
after a long odyssey getting xfree86 dri to work (seemingly), everything
behaves as expected, except that the gl window (also fullscreen) remains
black; fps is being reported as usual (4300), no error messages appear,
neither in the server log nor the kernel log, no hangups, no crashes,
nothing
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=314
[EMAIL PROTECTED] changed:
What|Removed |Added
---
On Sat, Nov 15, 2003 at 12:36:20PM -0600, Ryan Underwood wrote:
>
> A small note, if you contact Matrox about adding features to the driver
> or open sourcing it, the question needs to go to Sales. Support ignores
> any inquiries about added features and redirect the questioner to sales
> instead
