From: "dhiltgen@toocool.calpoly.edu" <dhiltgen@toocool.itslab.calpoly.edu>
To: mlan@cpu.lu, O.Waller@ee.qub.ac.uk
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: matroxfb, anybody?
Date: Sat, 30 Jan 1999 02:00:06 -0800 [thread overview]
Message-ID: <19990130020006.A580@toocool.calpoly.edu> (raw)
In-Reply-To: <199812172146.WAA00356@piglet.cpu.lu>; from Michel Lanners on Thu, Dec 17, 1998 at 10:46:30PM +0100
Add me to the list of people playing with matroxfb and controlfb.
Does anyone have some fbset outputs suitable for fb.modes for the
matrox Mil I card? I'm having a heck of a time trying to change from the
default mode. In Documentation/fb/matroxfb they talk about passing kernel
parameters to set the modes, but whenever I do that the kernel panics
before ever spitting anything out. I assume it's a "no bios" thing.
I'm hoping someone with a Mac version of the card might already have
the various timings etc that fbset wants, and that they'll be the same
as the PC version.
And the one other simple question... how in the heck do you tell
XF68 which /dev/fb* to go to? Right now I'm moving the devices
around by hand, but I'd eventually like to get a Dual headed X setup
going.
...aside...
I'm running an x86 Matrox card in my 8600, and it "sort of" works
right now on 2.2.0. It appears that there are definitely some kernel
bugs as far as mode switching, as sometimes control and matrox end up
duplicating each other resulting in very funky displays. I had to hack
the kernel slightly, in that it assumes if you have a Mac, well then you
must have a Mac matrox card, and OF should take care of initialization.
Nope, I've got a x86 card, and it has to be initialized by the kernel.
Simple one line hack in the init function for matroxfb.
Thanks for any input.
--
Daniel Kerry Hiltgen Computer Science Cal Poly, San Luis Obispo, CA
dhiltgen@www.itslab.calpoly.edu http://www.itslab.calpoly.edu/~dhiltgen/
"In a world without fences who needs Gates?" 1997 JavaOne Conference
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-01-30 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-13 10:40 matroxfb, anybody? Michel Lanners
1998-12-15 12:00 ` Owen Waller
1998-12-17 21:46 ` Michel Lanners
1999-01-30 10:00 ` dhiltgen@toocool.calpoly.edu [this message]
1999-01-30 12:09 ` Matt McLean
1999-01-30 15:32 ` Owen Waller
1999-01-30 23:34 ` matroxfb, anybody? (More details...) dhiltgen@toocool.calpoly.edu
1999-01-31 9:38 ` Gerd Knorr
1999-01-31 14:24 ` Geert Uytterhoeven
1999-02-06 15:22 ` Gerd Knorr
1999-01-31 14:36 ` Geert Uytterhoeven
1998-12-16 4:42 ` matroxfb, anybody? Troy Benjegerdes
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=19990130020006.A580@toocool.calpoly.edu \
--to=dhiltgen@toocool.itslab.calpoly.edu \
--cc=O.Waller@ee.qub.ac.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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;
as well as URLs for NNTP newsgroup(s).