From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Terence Soh <gopher@singnet.com.sg>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: printk on framebuffer console
Date: Wed, 31 May 2006 19:11:36 +0800 [thread overview]
Message-ID: <447D79E8.3090102@gmail.com> (raw)
In-Reply-To: <447D5134.1090502@singnet.com.sg>
Terence Soh wrote:
>> Remove the console=ttyS0 from your boot parameter (or change it to tty0)
>> and the system messages should go to the framebuffer console.
> You're right, that worked.
>
> Is there any way I can disable the printf/printk once my QT-Embedded
> application starts?
The simplest solution is to write a utility that opens /dev/tty0
for example, then do an ioctl,
ioctl(fd, KDSETMODE, KD_GRAPHICS);
where fd is the file descriptor of /dev/tty0 for instance.
To get back your console, do this:
ioctl(fd, KDSETMODE, KD_TEXT);
Tony
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
next prev parent reply other threads:[~2006-05-31 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <447C03C6.3000805@singnet.com.sg>
2006-05-30 12:17 ` [directfb-dev] printk on framebuffer console Antonino A. Daplas
2006-05-31 0:45 ` Terence Soh
2006-05-31 0:54 ` Antonino A. Daplas
2006-05-31 1:47 ` Terence Soh
2006-05-31 4:16 ` Antonino A. Daplas
2006-05-31 8:17 ` Terence Soh
2006-05-31 11:11 ` Antonino A. Daplas [this message]
2006-05-31 11:32 ` Terence Soh
2006-05-31 14:45 ` Marcin Juszkiewicz
2006-05-31 9:05 ` 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=447D79E8.3090102@gmail.com \
--to=adaplas@gmail.com \
--cc=gopher@singnet.com.sg \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.