From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Need help !
Date: Tue, 15 Jun 2004 08:02:04 +0200 [thread overview]
Message-ID: <20040615060204.GU20632@lug-owl.de> (raw)
In-Reply-To: <40CDFABF.2020503@integrated-devices.com>
[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]
On Mon, 2004-06-14 12:21:35 -0700, Srinivasa Deevi <sdeevi%integrated-devices.com@integrated-devices.com>
wrote in message <40CDFABF.2020503@integrated-devices.com>:
> do I need to add any fonts in fonts directory to see the any console
> output through fbcon ? Right now I am able to see the blinking cursor
> but any data from it .
No, you don't need to add fonts, but make sure you've choosen at least
one of them:)
> can somebody help me what should I do to see the cosole output on a
> frame buffer device ? The frame buffer driver is working in graphics
> mode . I have trouble in console mode .
I've seen that, too, when I wrote a FB driver. My bug was that I was
missing
#ifdef CONFIG_VT
#ifdef CONFIG_DUMMY_CONSOLE
/*
* We need a dummy console up at cons_init time, otherwise there'll
* be no VTs allocated for the real fbdev console to later take over.
*/
conswitchp = &dummy_con;
#endif
#endif
in arch-dependand code (for me, adding it to ./arch/vax/kernel/setup.c
did the job).
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 --]
prev parent reply other threads:[~2004-06-15 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 19:21 Need help ! Srinivasa Deevi
2004-06-14 21:51 ` David Eger
2004-06-15 6:02 ` Jan-Benedict Glaw [this message]
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=20040615060204.GU20632@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).