From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Otto Solares <solca@guug.org>
Cc: James Simmons <jsimmons@infradead.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] fbdv/fbcon pending problems
Date: Wed, 25 Feb 2004 13:33:00 +1100 [thread overview]
Message-ID: <1077676380.1129.55.camel@gaston> (raw)
In-Reply-To: <20040225021808.GB17390@guug.org>
> Hmm, how does winxp and macosx get their respectives video modes,
> what is missing in fbdev for that? MacOSX always gives you valid modes
> including refresh rates per adaptor/monitor, WinXP always give you valid
> modes and valid refresh rates for the video card, you actually
> 'Apply' to test, most of the time it simply works.
They do the same as I described. As you wrote, it works most of the
time. That's the whole point. You submit a "proposed" configuration
and gets back something .... most of the time, you do get back what
you asked. But you _might_ not. In some cases, what will happen is
that the "other" head will be affected. For example, enabling
mirroring on a non-4.3 LCD laptop like a titanium powerbook while
having a 4.3 display (CRT) plugged on the second output will cause
the LCD to be resized to a 4.3 ratio in MacOS.
So in this case, you get _more_ than what you asked.
> Great! i think your idea is great, does that library will be xserver
> dependant or will be an independent lib so others projects like mine
> could benefit from it? Any bits somewhere? This alone could boom
> and revolutionize the graphics solutions for linux. A step in the
> right direction for "World Domination" in the desktop field.
It's meant to be independant of anything else but the actual low
level driver model. Xserver would be one client, but others could
enter the game of course ;)
Ben.
next prev parent reply other threads:[~2004-02-25 2:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 0:53 fbdv/fbcon pending problems Benjamin Herrenschmidt
2004-02-23 15:52 ` Johannes Stezenbach
2004-02-23 18:59 ` James Simmons
2004-02-23 22:50 ` Benjamin Herrenschmidt
2004-02-24 1:19 ` James Simmons
2004-02-24 8:37 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-02-24 8:33 ` Benjamin Herrenschmidt
2004-02-23 20:35 ` Thorsten Kranzkowski
2004-02-23 22:18 ` James Simmons
2004-02-24 2:37 ` [Linux-fbdev-devel] " Otto Solares
2004-02-24 8:35 ` Geert Uytterhoeven
2004-02-24 17:21 ` James Simmons
2004-02-24 21:41 ` Otto Solares
2004-02-25 1:21 ` James Simmons
2004-02-25 1:26 ` Benjamin Herrenschmidt
2004-02-25 21:24 ` James Simmons
2004-02-25 23:46 ` Benjamin Herrenschmidt
2004-02-26 0:20 ` James Simmons
2004-02-26 0:33 ` Benjamin Herrenschmidt
2004-02-26 1:11 ` James Simmons
2004-02-25 1:29 ` Benjamin Herrenschmidt
2004-02-25 2:18 ` Otto Solares
2004-02-25 2:33 ` Benjamin Herrenschmidt [this message]
2004-02-25 3:15 ` Otto Solares
2004-02-25 11:41 ` Geert Uytterhoeven
2004-02-25 14:01 ` Sven Luther
2004-02-25 14:08 ` Geert Uytterhoeven
2004-02-25 21:43 ` James Simmons
2004-02-26 19:40 ` Otto Solares
2004-02-26 19:45 ` James Simmons
2004-02-26 20:12 ` Otto Solares
2004-02-25 21:42 ` James Simmons
2004-02-26 15:26 ` Michel Dänzer
2004-02-24 5:57 ` Stuart Young
2004-02-24 8:36 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-02-25 7:14 ` Stuart Young
2004-02-26 15:11 ` Michel Dänzer
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=1077676380.1129.55.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=solca@guug.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