From: Helge Hafting <helgehaf@aitel.hist.no>
To: Mikhail Kshevetskiy <kl@laska.dorms.spbu.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: framebuffer trouble with AGP MGA G450 and PCI MGA 2064W videocards.
Date: Sun, 6 Jun 2004 00:36:13 +0200 [thread overview]
Message-ID: <20040605223613.GA3326@hh.idb.hist.no> (raw)
In-Reply-To: <20040605231251.1f584e87@laska>
On Sat, Jun 05, 2004 at 11:12:51PM +0400, Mikhail Kshevetskiy wrote:
> i have two matrox videocard. The primary is dualhead AGP MGA G450 and the
> secondary is PCI MGA 2064W. I have a 2.6 kernel compiled with options
>
> CONFIG_FB_MATROX=y
> CONFIG_FB_MATROX_MILLENIUM=y
> CONFIG_FB_MATROX_G450=y
> CONFIG_FB_MATROX_G100=y
> CONFIG_FB_MATROX_MULTIHEAD=y
>
> CONFIG_VGA_CONSOLE=y
> CONFIG_DUMMY_CONSOLE=y
> CONFIG_FRAMEBUFFER_CONSOLE=y
> CONFIG_PCI_CONSOLE=y
>
> In BIOS I select AGP card as primary, but framebuffer initialise PCI card
> first. So fb0 point to PCI card, fb1 and fb2 point to AGP card. As a
> result framebuffer console working on another monitor. How can I link fb0
> and fb1 with AGP card and fb2 with PCI card ?
>
> Please CC me, as i am not subscribed to the list
>
Several solutions:
1. Don't do it.
Is it really a problem? How about using fb1 when you want to use
the AGP card?
2. Use modules, and load the AGP module first. It will then
grap fb0. Then load the pci module, which becomes fb1
3. Use the flexibility that /dev offers. fb0 don't have to
be the first framebuffer, in other words:
cd /dev
mv fb0 temp
mv fb1 fb0
mv temp fb1
>From now on, the name "fb0" actually refer to the second framebuffer.
any program that wants "fb0" get the AGP card, even if it is
initialized last.
4. Or use udev to achieve the same as in (3).
Helge Hafting
prev parent reply other threads:[~2004-06-05 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 19:12 Mikhail Kshevetskiy
2004-06-05 22:36 ` Helge Hafting [this message]
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=20040605223613.GA3326@hh.idb.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=kl@laska.dorms.spbu.ru \
--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®