From: Wolfgang Denk <wd@denx.de>
To: Jan Damborsky <jan.damborsky@devcom.cz>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Console on frame buffer for mpc823
Date: Wed, 06 Aug 2003 12:50:31 +0200 [thread overview]
Message-ID: <20030806105036.D6EDEC59E4@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 06 Aug 2003 12:17:32 +0200." <3F30D5BC.9070400@devcom.cz>
Dear Jan,
in message <3F30D5BC.9070400@devcom.cz> you wrote:
>
> primarily thank you for your help. But I have not
> been lucky to solve my problem. May be I have
> old kernel version - 2.4.3.
We did most of the framebuffer related work with our 2.4.4 kernel
tree; I don't know if older kernel versions have problems in that
area, but it's easily possible.
> I have set all this CONFIGS_xxx except for CONFIG_CONSOLE_NOBLANK and
> CONFIG_CONSOLE_NOCUR which are not supported in this kernel version.
These are extensions in our kernel tree to avoid a blinking cursor
and the default screen blank which is not what you want on most
embedded systems.
> How to test that frame buffer is assigned to text console ?
Do you see the penguin logo when booting?
> [1] CONFIG_SERIAL_CONSOLE is set - it is hardwired
> to CONFIG_8xx - may be it is problem - isn't it ?
This is OK.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
All men should freely use those seven words which have the power to
make any marriage run smoothly: You know dear, you may be right.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-08-06 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 8:40 Console on frame buffer for mpc823 Jan Damborsky
2003-08-06 9:00 ` Wolfgang Denk
2003-08-06 10:17 ` Jan Damborsky
2003-08-06 10:50 ` Wolfgang Denk [this message]
2003-08-06 11:14 ` Jan Damborsky
2003-08-06 10:55 ` Wolfgang Grandegger
2003-08-06 11:03 ` Jan Damborsky
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=20030806105036.D6EDEC59E4@atlas.denx.de \
--to=wd@denx.de \
--cc=jan.damborsky@devcom.cz \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).