public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Jesse Barnes <jbarnes@engr.sgi.com>,
	Dave Jones <davej@redhat.com>, Andrew Morton <akpm@osdl.org>,
	Dave Airlie <airlied@linux.ie>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: drm bugs hopefully fixed but there might still be one..
Date: Thu, 24 Mar 2005 21:09:06 +0100	[thread overview]
Message-ID: <20050324210906.727543f6.khali@linux-fr.org> (raw)
In-Reply-To: <3LFzj-40t-15@gated-at.bofh.it>

Ho all,

> > Aparently backing out the changes to via's tlb_flush routine fixed
> > it for one VIA user. I've not had a chance to look into it just yet.
> > Worse case we can just drop those changes for 2.6.12

I am that one.

> You mean these changes?
> 
> --- a/drivers/char/agp/via-agp.c        2005-03-24 10:33:45 -08:00
> +++ b/drivers/char/agp/via-agp.c        2005-03-24 10:33:45 -08:00
> @@ -83,8 +83,10 @@
>  
>         pci_read_config_dword(agp_bridge->dev, VIA_GARTCTRL, &temp);
>         temp |= (1<<7);
> +       temp &= ~0x7f;
>         pci_write_config_dword(agp_bridge->dev, VIA_GARTCTRL, temp);
>         temp &= ~(1<<7);
> +       temp &= ~0x7f;
>         pci_write_config_dword(agp_bridge->dev, VIA_GARTCTRL, temp);
>  }

Exactlty. I had to revert this one since 2.6.11-bk3, or starting X kills
the machine. By "kill", I mean the real thing, black screen, dead
network, reset is the only choice. This is a (surprise!) VIA-based
motherboard (Asus A7V133-C) with Radeon 9200-based graphics adapter.
Dave Airlie was asking for a tester with such a configuration. I can
test whatever you want. Just tell me what we are looking for :)

With the patch above reverted, 2.6.12-rc1-mm2 seems to work just fine
for me. glxgears is OK and I just had a game of UT (first of the name).
However, I am not a regular gamer so I'm not sure what to look for.

Thanks,
-- 
Jean Delvare

       reply	other threads:[~2005-03-24 20:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3LxV3-5Is-25@gated-at.bofh.it>
     [not found] ` <3LE0y-2Kn-55@gated-at.bofh.it>
     [not found]   ` <3LFg5-3MJ-37@gated-at.bofh.it>
     [not found]     ` <3LFzj-40t-15@gated-at.bofh.it>
2005-03-24 20:09       ` Jean Delvare [this message]
2005-03-24 10:33 drm bugs hopefully fixed but there might still be one Dave Airlie
2005-03-24 11:04 ` Andrew Morton
2005-03-24 17:02 ` Jesse Barnes
2005-03-24 18:18   ` Dave Jones
2005-03-24 18:35     ` Jesse Barnes
2005-03-24 21:58 ` cliff white
2005-03-24 22:21   ` Andrew Morton
2005-03-24 23:04     ` cliff white
2005-03-24 23:12       ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050324210906.727543f6.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=airlied@linux.ie \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=jbarnes@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox