From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Framebuffers and VC setup (via fbcon.c)
Date: Wed, 10 Mar 2004 23:02:22 +0100 [thread overview]
Message-ID: <20040310220222.GG17857@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0403101806460.24760-100000@phoenix.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 2515 bytes --]
On Wed, 2004-03-10 18:15:57 +0000, James Simmons <jsimmons@infradead.org>
wrote in message <Pine.LNX.4.44.0403101806460.24760-100000@phoenix.infradead.org>:
> > - 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 :)
In the meantime, another VAX hacker (who initially worked on the 2.4.x
code base) hinted me: in the arch_setup function, I was missing a
conswitchp = &dummy_con;
After adding these, I got a penguin and a login prompt. However, the
console output (during further boot-up) didn't show up. But I'll get
there:)
> I'm going to have to look at your driver. Normally one of two things
> happen. Some driver have there hardware modes set by firmware and they
> can't be changed. For example VESA fbdev. In this case you lack a
> xxxfb_check_var and xxxfb_set_par function. Then fbcon doesn't attempt to
> change the hardware state but use the current one.
> The other case is that your driver sets the hardware state. You have a
> set_check_var and a set_par function hook in struct fb_info->fbops. So the
> fbcon layer will call set_par directly for you.
Well, as I know today, there are more variants of this hardware, some of
them capable of changing screen resolution. So I think I'd add those two
functions (after I figured out how to actually change modes, or even how
to properly detect the available hardware at all:)
Thanks for these valuable hints! Oh, just another question: the largest
of theses framebuffer devices can handle four CRTs. Just need to
register four framebuffers, then?
After all, I've had my very first local login last night, at 00:42:23
CET with local monitor and keyboard on a VAX. Right, I waited some
seconds to get that nice time on my watch:)
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 prev parent reply other threads:[~2004-03-10 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 14:39 Framebuffers and VC setup (via fbcon.c) Jan-Benedict Glaw
2004-03-10 18:15 ` James Simmons
2004-03-10 22:02 ` Jan-Benedict Glaw [this message]
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=20040310220222.GG17857@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).