From: John Zielinski <grim@undead.cc>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: fbdev upstream
Date: Wed, 24 Dec 2003 20:53:15 -0500 [thread overview]
Message-ID: <3FEA430B.603@undead.cc> (raw)
In-Reply-To: <1072313855.15477.26.camel@gaston>
Benjamin Herrenschmidt wrote:
>Moving that to userland is a 2.7 goal. For 2.6, we should probably
>stay around what I'm doing in radeonfb. Also, we want the machine to
>have some sort of working console at boot. The VGA console exist
>only on some platforms like x86, for example, PPC needs a working mode
>at boot time.
>
>
That's why it's the ultimate goal. ;-) I'll still be working on it
for this project I have but I'll keep it seperate until it's time to
work on 2.7 stuff. I keep all my patches in small pieces so I can pick
an chose which ones I want to work with at the moment. As for the
working mode at boot time, that's not a problem. The initramfs archive
is unpacked extrememly early in the boot process. The message for that
apears way before the fbdev or fbcon messages come up. Many HDTV's
don't sync to standard VGA signals so i need the proper mode up as soon
as possible as well. The only problem is that a couple of models don't
supply the correct DDC timings and the picture rolls. That's why I'd
like to have the database available that early and to not require a
kernel recompile to change it. But this is 2.7 stuff.
>Also, some drivers may have different monitor probing mecanism that
>DDC2/EDID. For example, old PowerMac drivers can probe the monitor
>type using an old Apple sepcific mecanism that leads to a modelist
>(macmodes) which is different. We currently don't deal with that
>very well though.
>
>
Then a standard generic way to retrieve this information from the fbdev
might be an idea. At the very least you should get the bare modelist
but if the other info is available (manufacturer, model number, serial
number, raw edid data) then that can be returned as well. Again this
is 2.7 material.
>The important point here is that fbdev must remain independant of fbcon,
>you can have fbdev without fbcon, all of the console cruft is not
>fbdev business.
>
>
>
That's why I'm putting a lot of my stuff into fbcon as it's console
related. Is X the only other system to use fbdev other than fbcon?
John
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next prev parent reply other threads:[~2003-12-25 1:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 7:03 Changing modes with fbset John Zielinski
2003-12-14 1:14 ` John Zielinski
2003-12-24 8:20 ` fbdev upstream (was: Changing modes with fbset) Benjamin Herrenschmidt
2003-12-24 8:26 ` Carlo E. Prelz
2003-12-24 20:40 ` fbdev upstream John Zielinski
2003-12-24 22:42 ` Benjamin Herrenschmidt
2003-12-25 0:45 ` John Zielinski
2003-12-25 0:57 ` Benjamin Herrenschmidt
2003-12-25 1:53 ` John Zielinski [this message]
2003-12-25 10:46 ` Benjamin Herrenschmidt
2003-12-25 16:53 ` John Zielinski
2004-01-05 14:41 ` Geert Uytterhoeven
2004-01-06 0:51 ` James Simmons
2004-01-06 1:03 ` Benjamin Herrenschmidt
2004-01-06 10:08 ` Geert Uytterhoeven
2004-01-09 20:05 ` James Simmons
2004-01-06 0:47 ` James Simmons
2004-01-08 2:17 ` John Zielinski
2004-01-08 20:37 ` James Simmons
2004-01-06 0:06 ` Changing modes with fbset James Simmons
2004-01-06 0:28 ` Otto Solares
2004-01-06 0:35 ` Benjamin Herrenschmidt
2004-01-06 1:08 ` Otto Solares
2004-01-06 1:09 ` Benjamin Herrenschmidt
2004-01-06 1:44 ` Otto Solares
2004-01-06 1:44 ` Benjamin Herrenschmidt
2004-01-06 2:06 ` Otto Solares
[not found] ` <1073354986.761.208.camel@gaston>
2004-01-06 2:24 ` Otto Solares
2004-01-06 11:38 ` Michel Dänzer
2004-01-06 15:23 ` Geert Uytterhoeven
2004-01-09 0:03 ` James Simmons
2004-01-09 1:31 ` Otto Solares
2004-01-06 0:33 ` Benjamin Herrenschmidt
2004-01-06 0:38 ` James Simmons
2004-01-08 2:06 ` John Zielinski
2004-01-08 20:38 ` James Simmons
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=3FEA430B.603@undead.cc \
--to=grim@undead.cc \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).