From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Framebuffers and VC setup (via fbcon.c)
Date: Tue, 9 Mar 2004 15:39:51 +0100 [thread overview]
Message-ID: <20040309143950.GS17857@lug-owl.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
Hi!
I've got some trouble getting a local FB console to work, maybe you've
got some suggestions...
This all happens on a VAX 4000 Model 46. I've already done the FB driver
(http://cvs.sourceforge.net/viewcvs.py/linux-vax/kernel-2.5/drivers/video/vaxlcgfb.c)
which basically works - cat'ting a properly prepared image to it
produces a proper display output.
Now I tried to bring CONFIG_VT and CONFIG_FRAMEBUFFER_CONSOLE into the
game. However, I end up with no working FB console. No penguin image, no
login prompt. This is because vc->vc_bottom ends up being 0, while it
should be at around 60.
Adding some printk()s and initcall_debug, here is what happens:
tty_class_init()
chr_dev_init()
vaxlcgfb_init()
tty_init()
vty_init()
fb_console_init()
"fbcon_startup: mode: VAX LCGfb"
"fbcon_startup: visual: 3"
"fbcon_startup: res: 1280x1024-8"
"Console: switching to frame buffer device"
pty_init()
fb_console_init()
"Console: switching to frame buffer device"
...
vc_init():
currcons=0, rows=64, cols=160, clear=1
then colors 0..15 are set
Two things look odd to me:
- fb_console_init is called twice. Once from
tty_init() -> vty_init() -> fb_console_init(), second time
directly as a "normal" __init / module_init() call.
- Despite the fact that (quite late in the boot process)
vc_init() is called (with correct looking arguments), I think
it should have been called quite some time earlier. With other
(PC based) graphic cards, the machine just switches to FB mode
after the FB driver is initialized. All further output is put
there. But not here...
I haven't yet really understood how FB and console code work together,
so it would be nice to have some hints there :)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-03-09 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 14:39 Jan-Benedict Glaw [this message]
2004-03-10 18:15 ` Framebuffers and VC setup (via fbcon.c) James Simmons
2004-03-10 22:02 ` Jan-Benedict Glaw
2004-03-11 8:46 ` Geert Uytterhoeven
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=20040309143950.GS17857@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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).