From: Tilman Sauerbeck <tilman@code-monkey.de>
To: "Hans-Jürgen Koch" <hjk@linutronix.de>
Cc: linux-fbdev-devel@lists.sourceforge.net, xorg@lists.freedesktop.org
Subject: Re: Matrox G550, dual head, 1680x1050
Date: Mon, 5 Mar 2007 07:59:12 +0100 [thread overview]
Message-ID: <20070305065911.GA1017@code-monkey.de> (raw)
In-Reply-To: <200703042247.21590.hjk@linutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1053 bytes --]
Hans-Jürgen Koch [2007-03-04 22:47]:
> @matroxfb developers: Thanks a lot, guys! Well done! Most people I asked about
> having a dual-head framebuffer console at 1680x1050 thought it would be
> impossible.
>
> @mga xorg developers: Well... Can you tell me why the kernel guys can
> initialize and use the second head and you can't? If you can give me hints
> where in the source I can start to look for the bug, I'm willing to spend
> some time there. Is there something I could try in my configuration?
matroxfb is much better organized wrt dual-head configurations. It also
has support for some hardware that xf86-video-mga doesn't support yet.
I'm working on that.
I think you might be hitting this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=9854
I just attached a temporary fix that you could try.
Regards,
Tilman
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
next prev parent reply other threads:[~2007-03-05 6:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703021053.00955.hjk@linutronix.de>
[not found] ` <200703021610.58188.hjk@linutronix.de>
[not found] ` <20070302152414.GC907@code-monkey.de>
2007-03-04 21:47 ` Matrox G550, dual head, 1680x1050 Hans-Jürgen Koch
2007-03-05 4:59 ` Petr Vandrovec
2007-03-05 6:33 ` Geert Uytterhoeven
2007-03-05 8:09 ` [Linux-fbdev-devel] " Michel Dänzer
2007-03-05 7:34 ` Hans-Jürgen Koch
2007-03-05 20:02 ` Hans-Jürgen Koch
2007-03-06 9:25 ` Petr Vandrovec
2007-03-06 9:38 ` [Linux-fbdev-devel] " Hans-Jürgen Koch
2007-03-06 9:48 ` Geert Uytterhoeven
2007-03-06 11:35 ` Petr Vandrovec
2007-03-05 6:59 ` Tilman Sauerbeck [this message]
2007-03-01 23:25 Hans-Jürgen Koch
2007-03-01 23:29 ` Alex Deucher
2007-03-01 23:49 ` Hans-Jürgen Koch
2007-03-01 23:56 ` Hans-Jürgen Koch
2007-03-02 1:49 ` 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=20070305065911.GA1017@code-monkey.de \
--to=tilman@code-monkey.de \
--cc=hjk@linutronix.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=xorg@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).