From: Zack Smith <fbui@comcast.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: can't access video memory?
Date: Fri, 09 Sep 2005 11:18:46 -0400 [thread overview]
Message-ID: <4321A7D6.9070702@comcast.net> (raw)
Hi all,
As an experiment I tried accessing a part of (shared) video memory
on my system that is not being used for display data, and this caused the
kernel to crash. I have 6 megs of space and the display is using only half,
but accessing above the 3 meg mark causes the problem. Accessing
the lower 3 megs works fine.
Does anyone know what might cause this?
Thanks,
Zack Smith
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next reply other threads:[~2005-09-09 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 15:18 Zack Smith [this message]
2005-09-10 5:46 ` can't access video memory? Antonino A. Daplas
[not found] <091020051443.548.4322F10400014A8E000002242207020653079A0D00@comcast.net>
2005-09-10 15:01 ` Jon Smirl
2005-09-10 20:32 ` Antonino A. Daplas
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=4321A7D6.9070702@comcast.net \
--to=fbui@comcast.net \
--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.