From: Linda Walsh <lkml@tlinx.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: device support VGA compat Matrox MGA G200ew
Date: Tue, 12 Jul 2011 14:15:14 -0700 [thread overview]
Message-ID: <4E1CB962.1000308@tlinx.org> (raw)
I was reviewing my kernel config and seeing what devices were
handled by what drivers -- and that all of them were configurable
via kernel devices.
I used an lspci -bkv to show me the kernel driver being used for each
device.
One that would seem to be of some importance is the graphics controller.
There were some others devs that were 'unclaimed', but don't know
that they have a tangible effect and have yet to try a few
options, so won't bother with them here, but this one is a puzzler:
08:03.0 VGA compatible controller: Matrox Graphics, Inc. MGA G200eW
WPCM450 (rev 0a) (prog-if 00 [VGA controller])
Subsystem: Dell PowerEdge T610 MGA G200eW WPCM450
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at d9800000 (32-bit, prefetchable)
Memory at de7fc000 (32-bit, non-prefetchable)
Memory at de800000 (32-bit, non-prefetchable)
Capabilities: [dc] Power Management version 1
I have tried the dev support under the 'frame buffer devs'
for Matrox accel, with ghe G100/G200/... options checked 'on'
(and Matrox I2C support as a module). But that modules doesn't
seem to be attached to this HW.
The only other Matrox G200 related option under the DRM support, but it
says it requires /dev/agpgart to be enabled. I know the computer doesn't
have an AGP 'slot' (the card is built-in), but is is possible AGP
would still be the choice for the interface?
Other ideas or not-supported?
Thanks!
Linda
next reply other threads:[~2011-07-12 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 21:15 Linda Walsh [this message]
2011-07-12 22:26 ` device support VGA compat Matrox MGA G200ew Francois Romieu
2011-07-12 23:07 ` Linda Walsh
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=4E1CB962.1000308@tlinx.org \
--to=lkml@tlinx.org \
--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