From: Markus Hadwiger <msh@parsec.org>
To: Jeff Hartmann <jhartmann@valinux.com>
Cc: Michael Guntsche <m.guntsche@epitel.at>,
linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: [Dri-devel] Re: AGPGART problems with VIA KX133 chipsets under 2.2.18/2.4.0
Date: Tue, 23 Jan 2001 18:58:34 +0100 [thread overview]
Message-ID: <3A6DC64A.82CA93AA@parsec.org> (raw)
In-Reply-To: <NDBBJOKGIPCDBEEFHNFPGECPCAAA.m.guntsche@epitel.at> <3A6DB677.2060109@valinux.com>
Michael Guntsche wrote:
> > 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.
Jeff Hartmann wrote:
> Can you try this patch and tell me if it fixes the problem (against 2.4.0)?
I tried it out on a VIA Apollo Pro 133A system (Pentium III)
and it seems to work. Previously, I had the same problem as Michael
and only got agpgart to work by temporarily hard-coding the correct
aperture base address in agpgart_be.c.
Thanks,
Markus
--
-
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/
next prev parent reply other threads:[~2001-01-23 17:59 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
2001-01-23 17:05 ` Wayne Whitney
2001-01-31 0:55 ` Bob_Tracy
2001-01-23 17:58 ` Markus Hadwiger [this message]
2001-01-23 20:34 ` [Dri-devel] " 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=3A6DC64A.82CA93AA@parsec.org \
--to=msh@parsec.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=jhartmann@valinux.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox