On Fri, May 04, 2001 at 01:32:52AM -0400, Rich 'Forge' Mingin wrote:
> Actually, the issue described here is an ATI/all-non-Intel chipsets one.
> ATI's drivers ship by default with a tweaked AGPgart (they call it the
> 'atigart'). This, of course, causes massive problems when it
> overrides/confli
Actually, the issue described here is an ATI/all-non-Intel chipsets one.
ATI's drivers ship by default with a tweaked AGPgart (they call it the
'atigart'). This, of course, causes massive problems when it
overrides/conflicts with Via/Sis/Ali's AGPgart. I don't believe this
issue is applicable to L
On Thu, May 03, 2001 at 09:47:23PM -0700, Jeffrey W. Baker wrote:
> > There also appears to be a conflict with the Radeon 64 and the KT133A (or
> > at least the Abit KT7A..) Nobody so far has been able to confirm it that
> > I've seen, but the problem is documented with workaround for Win00. Giv
On Fri, May 04, 2001 at 02:47:27PM +1000, Gareth Hughes wrote:
> > There also appears to be a conflict with the Radeon 64 and the KT133A (or
> > at least the Abit KT7A..) Nobody so far has been able to confirm it that
> > I've seen, but the problem is documented with workaround for Win00. Given
Joseph Carter wrote:
>
> There also appears to be a conflict with the Radeon 64 and the KT133A (or
> at least the Abit KT7A..) Nobody so far has been able to confirm it that
> I've seen, but the problem is documented with workaround for Win00. Given
> that I have the same setup, same symptoms,
On Thu, 3 May 2001, Joseph Carter wrote:
> There also appears to be a conflict with the Radeon 64 and the KT133A (or
> at least the Abit KT7A..) Nobody so far has been able to confirm it that
> I've seen, but the problem is documented with workaround for Win00. Given
> that I have the same setu
On Thu, May 03, 2001 at 04:34:11PM -0700, Jeffrey W. Baker wrote:
> > > Could someone add to the "Known Problems" for the Radeon that it
> > > doesn't work with certain AMD chipsets? This is a pretty serious bug
> > > that apparently has been known about for quite some time. I certainly
> > > wou
Brian Paul wrote:
>
> >
> > Hmm. Is EMBM supported/required by OpenGL, or is that strictly a DirectX thing?
>
> It could be supported by an OpenGL extension, but I don't think Matrox
> ever spec'd one out. I don't know enough of the details to say how
> hard it would be to implement.
I think
Brian Paul wrote:
>
> I don't have my G400 installed right now but next time I do I'll look
> into this.
Brian, I'm swapping a G400 in this weekend to finish the 3.5 merge
stuff, so I can take a look if you like.
-- Gareth
PS - Yes, the tdfx stuff is wrapping up nicely.
__
I've got diffs to get BSD DRM almost compiling for tdfx and mga up on my
site. Check bsd-2-0-0-branch diffs (and the drm_agpsupport.h file, I didn't
feel like merging linux and bsd agp into a single file right now). They are
untested, but getting it to compile is a big step. Code tweaks I se
On Thu, May 03, 2001 at 04:26:00PM -0600, Brian Paul wrote:
> Would it be better if the DRI User Guide were divided into a number of
> separate HTML pages, instead of one long document? I could do that
> with the sgml2html converter. I'm hesitant to create new documents
> because that's more wor
On Thu, May 03, 2001 at 04:26:00PM -0600, Brian Paul wrote:
>
> We've got the docs but we have to spend our time working on projects
> which bring in income. We're hopeful that Radeon TCL will get done
> through a future contract. (Yes, I'm being vague).
What is the way / procedure to get hold
Jeffrey W. Baker wrote:
>
> On Thu, 3 May 2001, Brian Paul wrote:
>
>> Mark Allan wrote:
>>
>>> Brian Paul wrote:
>>>
> On Radeon we aren't doing TCL, cube textures, 3D textures and only
> support 2 of the 3 texture units. There's probably a few other things
> but that's off the
On Thu, 3 May 2001, Brian Paul wrote:
> Mark Allan wrote:
> >
> > Brian Paul wrote:
> > > > On Radeon we aren't doing TCL, cube textures, 3D textures and only
> > > > support 2 of the 3 texture units. There's probably a few other things
> > > > but that's off the top of my head.
> > >
> > > I'
Mark Allan wrote:
>
> Brian Paul wrote:
> > > On Radeon we aren't doing TCL, cube textures, 3D textures and only
> > > support 2 of the 3 texture units. There's probably a few other things
> > > but that's off the top of my head.
> >
> > I've just updated the DRI User Guide with more info about
Jon Pennington wrote:
>
> On Thu, May 03, 2001 at 08:33:23AM -0600, Brian Paul wrote:
>
> > Kreuzritter2000 wrote:
> > >
> > > This Feature list would also tell interested people what is done,
> > > and what has still to be done.
> > >
> > > What do you think about such a page?
> >
> > The DRI U
On Thu, May 03, 2001 at 08:33:23AM -0600, Brian Paul wrote:
> Kreuzritter2000 wrote:
> >
> > This Feature list would also tell interested people what is done,
> > and what has still to be done.
> >
> > What do you think about such a page?
>
> The DRI User guide has some of this information for
> Kreuzritter2000 wrote:
>>
>> Hello
>>
>> It would be great if there is a feature list on the dri website.
>>
>> That tells the progress of the driver, in other words what features
>> of the Chip ist are allready supported and what features are not support.
>> In the moment the Driver status page
Mark Allan wrote:
>
> Mark Allan wrote:
> >
> > Brian Paul wrote:
> > >
> > > Pasi Kärkkäinen wrote:
> > > >
> > > > Hello!
> > > >
> > > > Are there known blending bugs in the mga-driver (g400)? When I render many
> > > > additive polygons on the top of each other with small alpha-value
> > > >
Mark Allan wrote:
>
> Brian Paul wrote:
> >
> > Pasi Kärkkäinen wrote:
> > >
> > > Hello!
> > >
> > > Are there known blending bugs in the mga-driver (g400)? When I render many
> > > additive polygons on the top of each other with small alpha-value
> > > (something like 0.05) the result is someth
Brian Paul wrote:
> > On Radeon we aren't doing TCL, cube textures, 3D textures and only
> > support 2 of the 3 texture units. There's probably a few other things
> > but that's off the top of my head.
>
> I've just updated the DRI User Guide with more info about hardware
> features implemented/
On Thu, May 03, 2001 at 09:42:46AM -0700, Daryll Strauss wrote:
> On Thu, May 03, 2001 at 10:09:46AM -0400, David Dawes wrote:
> > On Wed, May 02, 2001 at 02:48:10PM -0500, Andy Isaacson wrote:
> > > Does the DRI project offer CVSUp access?
> > It doesn't, but I'd like to see it available too. Th
On Thu, May 03, 2001 at 10:09:46AM -0400, David Dawes wrote:
> On Wed, May 02, 2001 at 02:48:10PM -0500, Andy Isaacson wrote:
> >Does the DRI project offer CVSUp access? I'm collecting CVS trees in
> >the interest of being able to do speedy local CVS operations, and CVSUp
> >is the most efficient
Brian Paul wrote:
>
> Kreuzritter2000 wrote:
> >
> > Hello
> >
> > It would be great if there is a feature list on the dri website.
> >
> > That tells the progress of the driver, in other words what features
> > of the Chip ist are allready supported and what features are not support.
> > In the
Kreuzritter2000 wrote:
>
> Hello
>
> It would be great if there is a feature list on the dri website.
>
> That tells the progress of the driver, in other words what features
> of the Chip ist are allready supported and what features are not support.
> In the moment the Driver status page only t
Hello
It would be great if there is a feature list on the dri website.
That tells the progress of the driver, in other words what features
of the Chip ist are allready supported and what features are not support.
In the moment the Driver status page only tells you if the chip works
or doesn't w
On Wed, May 02, 2001 at 02:48:10PM -0500, Andy Isaacson wrote:
>Does the DRI project offer CVSUp access? I'm collecting CVS trees in
>the interest of being able to do speedy local CVS operations, and CVSUp
>is the most efficient method of getting the repository.
It doesn't, but I'd like to see i
Frank Worsley wrote:
>
> Since some people asked for it on the FAQ comments I've put together a
> pretty basic DRI Beginner's Guide.
>
> It is a rough, step-by-step guide on how to setup the DRI on a Linux
> system. Instead of explaining everything twice it just gives you a short
> explanation o
Since some people asked for it on the FAQ comments I've put together a
pretty basic DRI Beginner's Guide.
It is a rough, step-by-step guide on how to setup the DRI on a Linux
system. Instead of explaining everything twice it just gives you a short
explanation on what to do and points you to the o
29 matches
Mail list logo
