public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Cavan <johncavan@home.com>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Odd behaviour with agpgart
Date: Sun, 19 Nov 2000 15:47:01 -0500	[thread overview]
Message-ID: <3A183C45.EA116735@home.com> (raw)
In-Reply-To: <3A174C58.141E0C91@home.com> <20001119203903.E670@ppc.vc.cvut.cz>

Petr Vandrovec wrote:
> 
> On Sat, Nov 18, 2000 at 10:43:20PM -0500, John Cavan wrote:
> > Bus  1, device   0, function  0:
> >   VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 5).
> >     IRQ 16.
> >     Master Capable.  Latency=64.  Min Gnt=16.Max Lat=32.
> >     Prefetchable 32 bit memory at 0xf6000000 [0xf7ffffff].
> >     Non-prefetchable 32 bit memory at 0xfeafc000 [0xfeafffff].
> >     Non-prefetchable 32 bit memory at 0xfe000000 [0xfe7fffff].
> >
> > But agpgart sets up:
> >
> > agpgart: Maximum main memory to use for agp memory: 440M
> > agpgart: Detected Intel 440BX chipset
> > agpgart: AGP aperture is 32M @ 0xfa000000
> 
> AGP aperture is feature of host bridge:
> 
> 00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 02)
>         Flags: bus master, medium devsel, latency 32
>         Memory at d0000000 (32-bit, prefetchable) [size=64M]
>                   ^^^^^^^^                        ^^^^^^^^^^
>         Capabilities: [a0] AGP version 1.0
> 
> 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G200 AGP (rev 01) (prog-if 00 [VGA])
>         Subsystem: Matrox Graphics, Inc. Millennium G200 AGP
>         Flags: bus master, medium devsel, latency 32, IRQ 11
>         Memory at d8000000 (32-bit, prefetchable) [size=16M]
>         Memory at d4000000 (32-bit, non-prefetchable) [size=16K]
>         Memory at d5000000 (32-bit, non-prefetchable) [size=8M]
>         Expansion ROM at <unassigned> [disabled] [size=64K]
>         Capabilities: [dc] Power Management version 1
>         Capabilities: [f0] AGP version 1.0
> 
> So it matters what you have listed in 00:00.0 node, not on Matrox device.

Ah, now it makes sense. Interestingly, yours show that the bridge
address is lower than the card address, mine is reversed. 

> > Needless to say, the two disagree and direct rendering is disabled.
> > Attached is my .config for 2.4.0-test11-pre7. I've been wading through
> > the code for AGP and DRM support, but nothing jumps out at me.
> 
> > (http://www.matrox.com/mga/support/drivers/latest/home.htm)
> 
> As matrox driver contains large BLOB which does all important things
> (dualhead) usual practices about binary only software applies.

Unfortunately, dual head is what I want from it. I can get dual head,
but not accelerated 3D on the primary display. The stock XFree86 driver
just chokes even trying dual head. Oh well. I guess I'll be waiting for
Matrox to sort themselves out or for the XFree86 guys to get it.
-
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/

      reply	other threads:[~2000-11-19 21:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-19  3:43 Odd behaviour with agpgart John Cavan
2000-11-19 19:39 ` Petr Vandrovec
2000-11-19 20:47   ` John Cavan [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=3A183C45.EA116735@home.com \
    --to=johncavan@home.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vandrove@vc.cvut.cz \
    /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