All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Hartmann <jhartmann@valinux.com>
To: Michael Guntsche <m.guntsche@epitel.at>
Cc: linux-kernel@vger.kernel.org,
	"Dri-devel@lists.sourceforge.net"
	<Dri-devel@lists.sourceforge.net>
Subject: Re: AGPGART problems with VIA KX133 chipsets under 2.2.18/2.4.0
Date: Tue, 23 Jan 2001 09:51:03 -0700	[thread overview]
Message-ID: <3A6DB677.2060109@valinux.com> (raw)
In-Reply-To: <NDBBJOKGIPCDBEEFHNFPGECPCAAA.m.guntsche@epitel.at>

[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]

Michael Guntsche wrote:

> Hello all,
> 
> While playing around with the agpgart module I noticed the following strange
> behaviour.
> 
> The hardware in question is an Asus K7V with the KX133 chipset and has been
> tested on both 2.4.0 and 2.2.18 kernels.
> 
> The output below is just from insmod,rmmod,insmod agpgart without starting
> X.
> 
> insmod agpgart for the first time:
> Jan 22 23:17:10 deepblue kernel: Linux agpgart interface v0.99 (c) Jeff
> Hartmann
> Jan 22 23:17:10 deepblue kernel: agpgart: Maximum main memory to use for agp
> memory: 204M
> Jan 22 23:17:10 deepblue kernel: agpgart: Detected Via Apollo Pro chipset
> Jan 22 23:17:10 deepblue kernel: agpgart: AGP aperture is 64M @ 0xe4000000
>                                                                   ^-------
> 
> rmmod, insmod agpgart:
> Jan 22 23:17:16 deepblue kernel: Linux agpgart interface v0.99 (c) Jeff
> Hartmann
> Jan 22 23:17:16 deepblue kernel: agpgart: Maximum main memory to use for agp
> memory: 204M
> Jan 22 23:17:16 deepblue kernel: agpgart: Detected Via Apollo Pro chipset
> Jan 22 23:17:16 deepblue kernel: agpgart: AGP aperture is 64M @ 0x4000000
>                                                                   ^------
> Apparently AGP isnt working afterwards.
> Someone know what might be causing this?
> 
> 
> If you need more information or a want me to help debug this issue further
> dont hestitate to tell me.
> 
> Since Im not subscribed to the list, please CC any replies to me directly.
> 
> 
> 
> 
> Cheers,
> Mike
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/

Can you try this patch and tell me if it fixes the problem (against 2.4.0)?

Apply the patch when in the directory drivers/char/agp.

-Jeff

[-- Attachment #2: via_try_this.diff --]
[-- Type: text/plain, Size: 364 bytes --]

--- agpgart_be.c~	Fri Dec 29 15:07:21 2000
+++ agpgart_be.c	Tue Jan 23 09:45:49 2001
@@ -1384,7 +1384,9 @@
 	aper_size_info_8 *previous_size;
 
 	previous_size = A_SIZE_8(agp_bridge.previous_size);
+#if 0
 	pci_write_config_dword(agp_bridge.dev, VIA_ATTBASE, 0);
+#endif
 	pci_write_config_byte(agp_bridge.dev, VIA_APSIZE,
 			      previous_size->size_value);
 }

  reply	other threads:[~2001-01-23 16:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-23  7:33 AGPGART problems with VIA KX133 chipsets under 2.2.18/2.4.0 Michael Guntsche
2001-01-23 16:51 ` Jeff Hartmann [this message]
2001-01-23 17:05   ` Wayne Whitney
2001-01-31  0:55     ` Bob_Tracy
2001-01-23 17:58   ` [Dri-devel] " Markus Hadwiger
2001-01-23 20:34     ` Jeff Hartmann

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=3A6DB677.2060109@valinux.com \
    --to=jhartmann@valinux.com \
    --cc=Dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.guntsche@epitel.at \
    /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.