From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Chad Miller <cmiller@surfsouth.com>
Cc: linux-kernel@vger.kernel.org, mj@suse.cz
Subject: Re: G400 behavior different, 2.2.18->2.4.0
Date: Tue, 16 Jan 2001 23:27:02 MET-1 [thread overview]
Message-ID: <12C66A4F35BB@vcnet.vc.cvut.cz> (raw)
On 16 Jan 01 at 17:16, Chad Miller wrote:
(added mj@suse.cz, as he may be interested in one range behind bridge
overlapping both forwarding ranges...)
> #00:01.0 PCI bridge: VIA Technologies, Inc. VT8371 [KX133 AGP] (prog-if \
> #00 [Normal decode])
> # Flags: bus master, 66Mhz, medium devsel, latency 0
> # Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
> # Memory behind bridge: d4000000-d6ffffff
> # Prefetchable memory behind bridge: d7000000-d8ffffff
> # Capabilities: [80] Power Management version 2
> #01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP \
> #(rev 05) (prog-if 00 [VGA])
> # Subsystem: Matrox Graphics, Inc. Millennium G400 MAX/Dual Head 32Mb
> # Flags: bus master, VGA palette snoop, medium devsel, latency 32, IRQ 10
> # Memory at d6000000 (32-bit, prefetchable)
> # Memory at d4000000 (32-bit, non-prefetchable)
> # Memory at d5000000 (32-bit, non-prefetchable)
> # Capabilities: [dc] Power Management version 2
> # Capabilities: [f0] AGP version 2.0
Please, add your BIOS into list of broken BIOSes and stop complaining ;-)
Your BIOS splitted 32MB G400 range into 16MB non-prefetchable d600-d6ff
and 16MB prefetchable (d700-d7ff) range. Probably BIOS though that it
is setting G400 framebuffer at D7000000 for 32MB, but as D7000000 is not
multiple of 32MB, it cannot work.
You should try upgrading BIOS. If it does not help... you can try
kernel resources assigning code, but as it skips VGA adapters currently,
it is long way to go.
BTW, correct BIOS should put G400's resource #1 at D4000000, #2 at D4800000,
and #0 at D6000000. Programming non-prefetchable range for D400-D4FF,
and prefetchable as D600-D7FF... Leaving D5xx unused.
Sorry for bad news,
Petr Vandrovec
vandrove@vc.cvut.cz
-
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 reply other threads:[~2001-01-16 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 23:27 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-16 22:40 G400 behavior different, 2.2.18->2.4.0 (was: matroxfb o Petr Vandrovec
2001-01-16 22:16 ` G400 behavior different, 2.2.18->2.4.0 Chad Miller
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=12C66A4F35BB@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=cmiller@surfsouth.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@suse.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
all inboxes | Powered by JetHome®