From: Jeff Hartmann <jhartmann@valinux.com>
To: Markus Hadwiger <msh@parsec.org>
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 13:34:58 -0700 [thread overview]
Message-ID: <3A6DEAF2.9090108@valinux.com> (raw)
In-Reply-To: <NDBBJOKGIPCDBEEFHNFPGECPCAAA.m.guntsche@epitel.at> <3A6DB677.2060109@valinux.com> <3A6DC64A.82CA93AA@parsec.org>
Markus Hadwiger wrote:
> 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/
All the VIA chipsets are pretty much the same so this should fix the
problem on everyone's system. I'll send a proper patch to Linus later
today.
-Jeff
-
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/
prev parent reply other threads:[~2001-01-23 20:38 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 ` [Dri-devel] " Markus Hadwiger
2001-01-23 20:34 ` Jeff Hartmann [this message]
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=3A6DEAF2.9090108@valinux.com \
--to=jhartmann@valinux.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.guntsche@epitel.at \
--cc=msh@parsec.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