From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Chad Miller <cmiller@surfsouth.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: matroxfb on 2.4.0 / PCI: Failed to allocate...
Date: Tue, 16 Jan 2001 19:31:33 MET-1 [thread overview]
Message-ID: <12C27D8E5537@vcnet.vc.cvut.cz> (raw)
On 16 Jan 01 at 13:22, Chad Miller wrote:
> On Tue, Jan 16, 2001 at 05:56:34PM +0000, Petr Vandrovec wrote:
> > What does 'lspci -v' say?
>
> #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: <available only to root>
> #
> #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 64, IRQ 10
> # 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: <available only to root>
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).
Prefetchable memory behind bridge on 0:01.0 should end at 0xd9ffffff.
This is probably what kernel wants to say - memory region is 32MB, but
there is only 16MB behind bridge, so region does not fit...
> > in such case, as matroxfb assumes that if request_mem_region failed,
> > it was because of some other driver already controls this hardware.
>
> Is there a patch available, or should I go looking for it?
Search function initMatrox2() in drivers/video/matrox/matroxfb_base.c.
In this function, you'll find two calls to request_mem_region followed
by 'goto fail' (or 'goto failCtrlMR) without printk. You can try to add
printk() here. Second request_mem_region fails, because of PCI subsystem
reports only 16MB window, while matroxfb requests 32MB one.
You can workaround by changing first value in
'static struct video_board vbG400' from 0x2000000 to 0x1000000. But only
16MB are available then. I'd like to see what XFree does on your hardware...
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 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 19:31 Petr Vandrovec [this message]
2001-01-16 20:55 ` G400 behavior different, 2.2.18->2.4.0 (was: matroxfb on 2.4.0 / PCI: Failed to allocate...) Chad Miller
-- strict thread matches above, loose matches on Subject: below --
2001-01-16 17:56 matroxfb on 2.4.0 / PCI: Failed to allocate Petr Vandrovec
2001-01-16 18:22 ` Chad Miller
2001-01-16 0:22 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=12C27D8E5537@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®