All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Dittmer <j.dittmer@portrix.net>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: agpgart, nforce2, radeon and agp fastwrite
Date: Sat, 12 Jul 2003 23:10:22 +0200	[thread overview]
Message-ID: <3F10793E.5080202@portrix.net> (raw)
In-Reply-To: <20030712202622.GB7741@suse.de>

Dave Jones wrote:
> On Sat, Jul 12, 2003 at 05:51:42PM +0200, Jan Dittmer wrote:
>  > just took me half a hour to figure out. On nforce2 you have to disable 
>  > agp fastwrites, otherwise X locks hard on startup with the following 
>  > (from serial console).
>  > ...
>  > 
>  > Without AGP Fastwrites turned on, it all works wonderful. Just if 
>  > anybody encounters the same problem.
>  > Mainboard is nForce2 based, graphics is radeon 8500le (R200).
> 
> Could be that the nforce & radeon don't play well together.
> Anyone using fast writes without problems with non-ATI cards & nforce ?
> If it works there, it's trivial to blacklist ATI cards and make them
> unable to enable fast writes in the gart driver.
> 
Forgot to mention I had to use this patchlet to get nvidia-agp to link 
properly.

Jan

--- linux-mm/drivers/char/agp/generic.c Thu Jul  3 15:04:06 2003
+++ 2.5.73-mm3/drivers/char/agp/generic.c       Wed Jul  9 10:04:34 2003
@@ -39,7 +39,7 @@

  __u32 *agp_gatt_table;
  int agp_memory_reserved;
-
+EXPORT_SYMBOL(agp_memory_reserved)
  /*
   * Generic routines for handling agp_memory structures -
   * They use the basic page allocation routines to do the brunt of the 
work.


-- 
Linux rubicon 2.5.75-mm1-jd10 #1 SMP Sat Jul 12 19:40:28 CEST 2003 i686


  reply	other threads:[~2003-07-12 20:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-12 15:51 agpgart, nforce2, radeon and agp fastwrite Jan Dittmer
2003-07-12 20:26 ` Dave Jones
2003-07-12 21:10   ` Jan Dittmer [this message]
2003-07-12 21:17     ` Dave Jones
2003-07-13 13:37       ` Jamie Lokier
2003-07-13 20:35         ` Rahul Karnik
  -- strict thread matches above, loose matches on Subject: below --
2003-07-13 10:17 Jaakko Niemi

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=3F10793E.5080202@portrix.net \
    --to=j.dittmer@portrix.net \
    --cc=davej@codemonkey.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.