mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Stian Jordet <liste@jordet.nu>
Cc: Dave Jones <davej@codemonkey.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Unsupported AGP-bridge on VIA VT8633
Date: Tue, 3 Dec 2002 10:53:28 +0100	[thread overview]
Message-ID: <20021203105328.A27071@bitwizard.nl> (raw)
In-Reply-To: <1037919383.856.3.camel@chevrolet.hybel>

On Thu, Nov 21, 2002 at 11:56:23PM +0100, Stian Jordet wrote:
> tor, 2002-11-21 kl. 23:40 skrev Dave Jones:
> > On Thu, Nov 21, 2002 at 11:20:31PM +0100, Stian Jordet wrote:
> > 
> >  > You were not really clear here. I tried it as a boot-time argument, because I
> >  > have agp-support compiled in. But I guess I could and should try it as a module.
> > 
> > Yup. Then do a `modprobe agpgart agp_try_unsupported=1'
> > 
> >  > I'll do that now. But why do I have to use agp_try_unsupported=1?
> > 
> > Because if it works, we can then add it to the ID table.
> 
> It works, i think. I get this message when I load it:
> 
> Linux agpgart interface v0.99 (c) Jeff Hartmann
> agpgart: Maximum main memory to use for agp memory: 439M
> agpgart: Trying generic Via routines for device id: 3091
> agpgart: AGP aperture is 64M @ 0xf8000000

Hi Dave, Stian,

"Same here": The module loads...

However, I have the impression that it doesn't work.  I first noticed 
that my Xserver was taking 50% of my CPU while playing videos. This
is much less on all other computers that I tried that on. 

Turns out that "write bandwidth" to video memory is less than 40Mb
per second. On another system with the same video card, but with a 
supported AGP bridge, I get almost 200Mbyte per second. I'll go and
dig for "testgart" and see what that proves.... 

			Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* The Worlds Ecosystem is a stable system. Stable systems may experience *
* excursions from the stable situation. We are currently in such an      * 
* excursion: The stable situation does not include humans. ***************

      parent reply	other threads:[~2002-12-03  9:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21 22:01 Stian Jordet
2002-11-21 22:11 ` Dave Jones
2002-11-21 22:20   ` Stian Jordet
2002-11-21 22:40     ` Dave Jones
2002-11-21 22:56       ` Stian Jordet
2002-11-21 23:14         ` Dave Jones
2002-11-21 23:37           ` Stian Jordet
2002-11-24 15:55           ` Stian Jordet
2002-12-03  9:53         ` Rogier Wolff [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=20021203105328.A27071@bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liste@jordet.nu \
    /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

Powered by JetHome