From: Richard Hirst <rhirst@linuxcare.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] framebuffer console
Date: Wed, 24 Oct 2001 10:30:33 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805378@msgid-missing> (raw)
Hi,
I've been trying to use the framebuffer console to display simple
graphics with only partial success. I'm using an nVidia Quadro2 card,
and a 2.4.9 kernel.
Would be nice to use CONFIG_FB_VESA so I was graphics card independent,
but there is some x86 assembler in that source, and I believe it relies
on video mode switching being done before the kernel starts as well.
So, I've compiled with CONFIG_FB_RIVA, and am experimenting with fbi, a
simple image viewer for the framebuffer console. This mmaps the framebuffer
memory, and tries to memcpy() in to it. That reliably causes hard
crashes and spontaneous system reboots. If I hack fbi to do lseek/write
on /dev/fb0 rather than mmap(), it seems to work ok.
When using mmap() I sometimes see parts of my image on the screen before
it crashes, and the pattern of bits that are drawn (or not) indicate
that some small blocks of data (cachelines?) are not written to the
video memory while other similar sized blocks are written. As the system
crashes so badly, I guess the missing blocks are written elsewhere.
The other thing that struck me as odd (but unrelated) was that on boot I
get two penguins at the top of the screen, where I'd expected only one..
So, has anyone else played with framebuffer console, and been more
successful than me? Is the problem I'm seeing likely to be specific
to my graphics card, or something more generic?
Thanks,
Richard
next reply other threads:[~2001-10-24 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 10:30 Richard Hirst [this message]
2001-10-24 11:26 ` [Linux-ia64] framebuffer console Richard Hirst
2001-10-24 12:14 ` Roman Hodek
2001-10-24 12:14 ` Roman Hodek
2001-10-24 23:21 ` David Mosberger
2001-11-04 22:06 ` Richard Hirst
2001-11-06 1:12 ` David Mosberger
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=marc-linux-ia64-105590698805378@msgid-missing \
--to=rhirst@linuxcare.com \
--cc=linux-ia64@vger.kernel.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