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=701
[EMAIL PROTECTED] changed:
What|Removed |Added
---
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=1833
[EMAIL PROTECTED] changed:
What|Removed |Added
--
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=2578
[EMAIL PROTECTED] changed:
What|Removed |Added
--
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=3195
[EMAIL PROTECTED] changed:
What|Removed |Added
--
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=3267
[EMAIL PROTECTED] changed:
What|Removed |Added
--
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=3398
--- Additional Comments From [EMAIL PROTECTED] 2005-06-26 23:20 ---
I bel
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=3495
[EMAIL PROTECTED] changed:
What|Removed |Added
--
On Mon, 2005-06-27 at 01:42 -0400, Vladimir Dergachev wrote:
> >
> >
> > I was just looking at r300 code today for my own system. A few things
> > that I think ought to happen for the merge:
> > - Clean up style. Unindented blocks of code, weird whitespace (closing
> > brackets on the same column
I was just looking at r300 code today for my own system. A few things
that I think ought to happen for the merge:
- Clean up style. Unindented blocks of code, weird whitespace (closing
brackets on the same column as the block containing it, rather than the
surrounding block), lack of wrapping
Attached is a patch to clean up setup and teardown of maps in Linux. I
did it because in the process of making BSD compile again, I kept
finding things that needed to be cleaned up and were making it harder to
get BSD working again, and it was too much doing both OSes at once. I'd
like to get it
On Sun, 2005-06-26 at 18:05 -0700, Eric Anholt wrote:
> On Mon, 2005-06-27 at 01:19 +0100, Alan Cox wrote:
>
> > Disagree also about axing the comment - its useful to know why something
> > is being done.
>
> Wait, the comment says "TODO: Remove this; we can't afford to let
> userspace control so
On Sunday 26 June 2005 21:51, Eric Anholt wrote:
> Heh. One of the suggestions of BSD style is that when 80 columns
> becomes too little, you probably need another function. In the diff I'm
> currently testing for cleaning up map handling (which net removes 200
> lines), I've removed that if stat
On Sun, 2005-06-26 at 21:25 -0400, Jon Smirl wrote:
> On 6/26/05, Eric Anholt <[EMAIL PROTECTED]> wrote:
> > Are you saying this:
> > if ((offset>=dev_priv->fb_location) &&
> > (offsetgart_vm_start)) return 0;
> > is more readable than:
> > if ((offset >= dev_priv->fb_location) &&
On 6/26/05, Eric Anholt <[EMAIL PROTECTED]> wrote:
> Are you saying this:
> if ((offset>=dev_priv->fb_location) &&
> (offsetgart_vm_start)) return 0;
> is more readable than:
> if ((offset >= dev_priv->fb_location) &&
> (offset < dev_priv->gart_vm_start))
>
On Mon, 2005-06-27 at 01:19 +0100, Alan Cox wrote:
> On Llu, 2005-06-27 at 01:02, Eric Anholt wrote:
> > > definitely vote for 120. You will need to do some manual touch up
> > > after Lindent. It will mess up formatting of C99 initializers and some
> > > constant blocks.
> >
> > Please, 80 is sta
On Llu, 2005-06-27 at 01:02, Eric Anholt wrote:
> > definitely vote for 120. You will need to do some manual touch up
> > after Lindent. It will mess up formatting of C99 initializers and some
> > constant blocks.
>
> Please, 80 is standard.
Not for most code I've looked at. 80 generates horrible
On 6/26/05, Eric Anholt <[EMAIL PROTECTED]> wrote:
> > The code in DRM CVS has been run through the kernel 'scripts/Lindent'
> > program. There has been recent discussion on lkml about changing the
> > script from 80 char lines to something more modern like 120. I'd
> > definitely vote for 120. You
On Sun, 2005-06-26 at 19:53 -0400, Jon Smirl wrote:
> On 6/26/05, Eric Anholt <[EMAIL PROTECTED]> wrote:
> > I was just looking at r300 code today for my own system. A few things
> > that I think ought to happen for the merge:
> > - Clean up style. Unindented blocks of code, weird whitespace (clo
Ben Skeggs wrote:
S3TC does seem to be the killer for UT2004. I started porting over the
S3TC stuff from the r200 driver a while
back, but haven't had a lot of time recently to fix a couple of issues
with it. Overall fps doesn't seem to take a
huge gain, but the sudden drops to 1-2fps in certai
Peter Zubaj wrote:
Hi,
For display corruption when switching from fglrx to radeon driver are
responsible RADEON_SURFACEx_ register.
One question: for what are these surfaces good ?
For tiling, if you read/write directly to the graphic card memory.
Should be no issue with xorg cvs howev
On 6/26/05, Eric Anholt <[EMAIL PROTECTED]> wrote:
> I was just looking at r300 code today for my own system. A few things
> that I think ought to happen for the merge:
> - Clean up style. Unindented blocks of code, weird whitespace (closing
> brackets on the same column as the block containing i
On Sun, 2005-06-26 at 18:54 -0400, Vladimir Dergachev wrote:
> Hi all,
>
>I have fixed known issues with r300 DRM driver:
>
> * r300_emit_unchecked_state properly fallbacks to
>r300_emit_carefully_checked_state() when asked to set
>touchy registers (i.e. those with off
Hi all,
I have fixed known issues with r300 DRM driver:
* r300_emit_unchecked_state properly fallbacks to
r300_emit_carefully_checked_state() when asked to set
touchy registers (i.e. those with offsets).
* r300_emit_raw properly checks LOAD_VBPNTR packet that
Adam K Kirchhoff wrote:
FYI
I've had a chance today to test the r300 driver (using a Radeon
9550) with every 3d game and application I have installed. This
includes UnrealTournament, ut2004, q3a, RTCW, Rune, Tribes2, Orbz,
MarbleBlast (both from GarageGames), neverball, neverputt, NWN,
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=2516
[EMAIL PROTECTED] changed:
What|Removed |Added
--
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=3460
--- Additional Comments From [EMAIL PROTECTED] 2005-06-26 14:29 ---
Could
Hi,
For display corruption when switching from fglrx to radeon driver are
responsible RADEON_SURFACEx_ register.
One question: for what are these surfaces good ?
Peter Zubaj
---
SF.Net email is sponsored by: Discover Easy Linux Migrati
FYI
I've had a chance today to test the r300 driver (using a Radeon
9550) with every 3d game and application I have installed. This
includes UnrealTournament, ut2004, q3a, RTCW, Rune, Tribes2, Orbz,
MarbleBlast (both from GarageGames), neverball, neverputt, NWN, doom3,
blender, ppracer,
28 matches
Mail list logo
