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=3834
--- Additional Comments From [EMAIL PROTECTED] 2005-12-09 17:27 ---
I get
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=5297
--- Additional Comments From [EMAIL PROTECTED] 2005-12-09 14:50 ---
terri
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=5297
Summary: Udev appears to create, rename and remove the device
On 12/8/05, Roland Scheidegger <[EMAIL PROTECTED]> wrote:
> khaqq wrote:
> > I wonder if different *video* chip revisions could be a factor.
> An interesting idea. I've never heard that there were multiple revisions
> of these chips (which made it to retail), though it might be possible.
> It shoul
khaqq wrote:
I wonder if different *video* chip revisions could be a factor.
An interesting idea. I've never heard that there were multiple revisions
of these chips (which made it to retail), though it might be possible.
It should be printed on the gpu itself afaik, or is it possible to get
th
> >
>
> Still looking at small test program.. but changing the GL_QUADS to two
> GL_TRIANGLES seems to solve the problems.. mayve the M7 has some
> degnerating problems..
Or maybe it doesn't support HW quads as ajax pointed out, and the sw quads
have some problems..
Dave.
--
David Airlie, Softw
>
> As long as the texcoords at all four corners are being translated the same
> amount, I wouldn't expect any differences in interpolation along the shared
> edge for the two triangles.
>
> If you've got a simple test program, perhaps some of us can test w/ different
> hardware.
>
Still looking a
On Fri, 09 Dec 2005 00:58:13 +0100
Stephane Marchesin <[EMAIL PROTECTED]> wrote:
> khaqq wrote:
>
> >Probably not. My FireGL8800 used to crash a lot about one year ago while
> >ajax' never crashed. And as far as I can tell, there is only one BIOS for
> >that card. ( http://www.techpowerup.com/bi
khaqq wrote:
On Tue, 06 Dec 2005 13:13:35 +0100
Roland Scheidegger <[EMAIL PROTECTED]> wrote:
vehemens wrote:
Posting my latest DRM and Mesa patches in case they should prove useful to
anyone else. They are to head as of early Saturday.
I moved the CP idle outside the while loop in
On Fri, 9 Dec 2005 00:42:03 +0100
khaqq <[EMAIL PROTECTED]> wrote:
> On Tue, 06 Dec 2005 13:13:35 +0100
> Roland Scheidegger <[EMAIL PROTECTED]> wrote:
>
> > vehemens wrote:
> > > Posting my latest DRM and Mesa patches in case they should prove useful
> > > to
> > > anyone else. They are to he
On Tue, 06 Dec 2005 13:13:35 +0100
Roland Scheidegger <[EMAIL PROTECTED]> wrote:
> vehemens wrote:
> > Posting my latest DRM and Mesa patches in case they should prove useful to
> > anyone else. They are to head as of early Saturday.
> >
> > I moved the CP idle outside the while loop in radeon_
Hello Andrew,
- correct "Savage video cards" into "S3 Savage video cards"
(this is what prompted me to create a patch, since all other entries
*consistently* mention the vendor first)
- correct too many misspelled product names (you've got to wonder whether
there's a conspiracy to misspell
Malek wrote:
Hey guys,
Just setting up a laptop here, was compiling from CVS and hit an error.
Seems someone left an extra _ in a type definition... did a search thru
the code and the _'ed version isn't used anywhere, so I'm guessing it
was just a typo.
I'm not sure what the format you guys want
On 12/8/05, Keith Whitwell <[EMAIL PROTECTED]> wrote:
> Alan Cox wrote:
> > On Iau, 2005-12-08 at 19:52 +0800, Austin Yuan wrote:
> >
> >>buffer. Because the interface of "alloc_by_type" only receives a
> >>simple parameter "type", here I hide the user space address into
> >>"type" and re-get it in
Alan Cox wrote:
On Iau, 2005-12-08 at 19:52 +0800, Austin Yuan wrote:
buffer. Because the interface of "alloc_by_type" only receives a
simple parameter "type", here I hide the user space address into
"type" and re-get it in alloc_userspace_memory.
That should probably be fixed by extending t
On Iau, 2005-12-08 at 19:52 +0800, Austin Yuan wrote:
> buffer. Because the interface of "alloc_by_type" only receives a
> simple parameter "type", here I hide the user space address into
> "type" and re-get it in alloc_userspace_memory.
That should probably be fixed by extending the API to pass b
Just an idea when thinking about the issue on
http://lists.freedesktop.org/pipermail/xorg/2005-April/007662.html.
I have done some experiment on it, and the idea here is doable, but
the method may be ugly and a little tricky.
For Intel integrated graphics chips, gart driver programs system memory
17 matches
Mail list logo
