From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Jan Mynarik <mynarikj@phoenix.inf.upol.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [matroxfb] Second head is on but fb1 not accessible
Date: Mon, 9 Feb 2004 14:29:43 +0200 [thread overview]
Message-ID: <32704C258F@vcnet.vc.cvut.cz> (raw)
On 9 Feb 04 at 14:21, Jan Mynarik wrote:
> > Make sure that /dev/fb1 is character device 29,1 and not 29,32. 2.2.x kernels
> > accept 29,32 only, 2.4.x accept both, and 2.6.x accept 29,1 only.
>
> Thanks for super-fast reply :-), I did think it could be related to
> minor device number.
>
> But anyway, shouldn't I have at least console visible on the second head
> (even if /dev/fb1 is not accessible)? I tested it by attaching my
> monitor to second head and nothing appeared.
Only G450/G550 display same picture (from CRTC1) on all outputs, MAVEN output
is by default disabled until you'll configure it with 'matroxset'.
If you want same picture on both outputs even for G400, it should be
enough to replace
ACCESS_FBINFO(outputs[1]).src = MATROXFB_SRC_NONE;
with
ACCESS_FBINFO(outputs[1]).src = MATROXFB_SRC_CRTC1;
in maven_init_client() in drivers/video/matrox/matroxfb_maven.c.
(it is not enabled by default as on G400 you can have either Maven output
or DFP output but not both; G450/G550 does not have such restriction,
and so on G450/G550 all three outputs show same picture by default).
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2004-02-09 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 12:29 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-09 13:09 [matroxfb] Second head is on but fb1 not accessible Jan Mynarik
2004-02-09 12:12 Petr Vandrovec
2004-02-09 13:21 ` Jan Mynarik
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=32704C258F@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mynarikj@phoenix.inf.upol.cz \
/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