From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Chad Miller <cmiller@surfsouth.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: G400 behavior different, 2.2.18->2.4.0 (was: matroxfb o
Date: Tue, 16 Jan 2001 22:40:51 MET-1 [thread overview]
Message-ID: <12C5A55170A3@vcnet.vc.cvut.cz> (raw)
On 16 Jan 01 at 15:55, Chad Miller wrote:
> (CC'd to lkml)
>
> On Tue, Jan 16, 2001 at 07:31:33PM +0000, Petr Vandrovec wrote:
> > There is something wrong with your hardware. First region for G400 should
> > be 32MB, not 16MB (even if you have 16MB G400, which I doubt).
>
> Ooo! Here's an edited diff of 'lspci -v' under 2.2.18 versus 2.4.0:
>
> 36,41c37,42
> < Flags: bus master, VGA palette snoop, medium devsel, latency 32, IRQ 10
> < Memory at d6000000 (32-bit, prefetchable)
> ---
> > Flags: bus master, VGA palette snoop, medium devsel, latency 64, IRQ 10
> > Memory at d8000000 (32-bit, prefetchable) [size=16M]
> Do you think any configuration parameters could affect this? (I haven't
> paid as much attention to the evolution from 2.2 to 2.4 as I should've.)
>
> Here's the diff of X' output, from 2.2.18 to 2.4.0:
>
> 43c43
> < (--) PCI:*(1:0:0) Matrox MGA G400 AGP rev 5, Mem @ 0xd6000000/25, 0xd4000000/14, 0xd5000000/23
> ---
> > (--) PCI:*(1:0:0) Matrox MGA G400 AGP rev 5, Mem @ 0xd6000000/24, 0xd4000000/14, 0xd5000000/23
> 72,73d71
> < (WW) ****INVALID MEM ALLOCATION**** b: 0xd6000000 e: 0xd7ffffff correcting\a
> < (EE) Cannot find a replacement memory range
Output under 2.2.x is correct: '/25' for 32MB range. I have no idea
why X complains about region D6000000-D7FFFFFF - can you look at
'... regions behind bridge' when you boot 2.2.x (they are on 0:01.0
device, AFAIK) ? Under 2.4.x you showed that prefetchable region is
D6000000-D8FFFFFF, which correctly covers 2.2.x framebuffer address
(although it is not power of 2, but who knows...).
You should see D4000000-D5FFFFFF as non-prefetchable memory behind bridge,
and D6000000-D7FFFFFF as prefetchable memory behind bridge.
Best regards,
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 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 22:40 Petr Vandrovec [this message]
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=12C5A55170A3@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=cmiller@surfsouth.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®