From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: linux-kernel@vger.kernel.org
Cc: faith@valinux.com, hulinsky@feld.cvut.cz
Subject: 2.4.x, drm, g400 and pci_set_master
Date: Thu, 8 Feb 2001 16:32:52 MET-1 [thread overview]
Message-ID: <14E7BDF32379@vcnet.vc.cvut.cz> (raw)
Hi,
friend of mine bought g400 on my recommendation, and unfortunately,
mga drm driver did not worked for me. I tracked it down to missing
pci_enable_device and pci_set_master in mga* driver. But even after
looking more than hour into that code I have no idea where I should
place this call, as it looks like that mga driver is completely
shielded from seeing pcidev structure :-(
Does anybody know where I should place pci_enable_device and
pci_set_master into mga code? I worked around pci_enable_device by
using matroxfb, but pci_set_master is not invoked by matroxfb, and
adding this call into matroxfb just to get mga drm driver to work does
not look correctly to me - although it is what I had done just now.
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04) (prog-if 00 [VGA])
Subsystem: Matrox Graphics, Inc. Millennium G400 Dual Head Max
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (4000ns min, 8000ns max), cache line size 08
Interrupt: pin A routed to IRQ 5
Region 0: Memory at f4000000 (32-bit, prefetchable) [size=32M]
Region 1: Memory at fcffc000 (32-bit, non-prefetchable) [size=16K]
Region 2: Memory at fc000000 (32-bit, non-prefetchable) [size=8M]
Expansion ROM at 80000000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [f0] AGP version 2.0
Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2
Command: RQ=31 SBA+ AGP+ 64bit- FW- Rate=x1
Linux version 2.4.1 (root@jenik) (gcc version 2.95.2 20000220 (Debian GNU/Linux)) #1 +t ˙no 6 18:14:01 CET 2001
BIOS-provided physical RAM map:
BIOS-e820: 00000000000a0000 @ 0000000000000000 (usable)
BIOS-e820: 0000000000010000 @ 00000000000f0000 (reserved)
BIOS-e820: 000000000fe9e000 @ 0000000000100000 (usable)
BIOS-e820: 0000000000062000 @ 000000000ff9e000 (reserved)
BIOS-e820: 0000000000500000 @ 00000000ffb00000 (reserved)
BIOS-e820: 0000000000010000 @ 00000000fec00000 (reserved)
BIOS-e820: 0000000000010000 @ 00000000fee00000 (reserved)
...
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 203M
agpgart: Trying generic Intel routines for device id: 2500
agpgart: AGP aperture is 64M @ 0xf0000000
[drm] AGP 0.99 on Intel @ 0xf0000000 64MB
[drm] Initialized mga 2.0.1 20000928 on minor 63
-
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-02-08 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 16:32 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-08 16:39 2.4.x, drm, g400 and pci_set_master Alex Deucher
2001-02-08 17:08 ` Jeff Hartmann
2001-02-08 17:15 ` Alex Deucher
2001-02-08 18:36 Petr Vandrovec
2001-02-08 17:47 ` Jeff Hartmann
2001-02-08 18:14 ` Alex Deucher
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=14E7BDF32379@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=faith@valinux.com \
--cc=hulinsky@feld.cvut.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.