From: Ondrej Zary <linux@rainbow-software.org>
To: Russell King <linux@arm.linux.org.uk>
Cc: linux-fbdev@vger.kernel.org,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: cyber2000fb - 24bpp and 32bpp modes not working
Date: Wed, 28 Jul 2010 19:59:16 +0000 [thread overview]
Message-ID: <201007282159.19583.linux@rainbow-software.org> (raw)
Hello,
some more CyberPro 2000 testing shows that 24bpp and 32bpp modes don't work.
8bpp and 16bpp modes work fine.
The mode appears to be set correctly (monitor OSD shows correct resolution and
frequency) but console remains blank (even no cursor).
Xorg with fbdev in 24bpp mode displays mouse cursor, then gdm background and
gdm login window and immediately segfaults. Xorg with fbdev in 32bpp mode
works.
So the framebuffer works (24bpp crash might be Xorg bug) but maybe the console
output is not written to the correct place?
--
Ondrej Zary
next reply other threads:[~2010-07-28 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 19:59 Ondrej Zary [this message]
2010-07-29 20:40 ` [PATCH] cyber2000fb: fix console in truecolor modes Ondrej Zary
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=201007282159.19583.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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).