public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] framebuffer console
Date: Wed, 24 Oct 2001 11:26:59 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805379@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805378@msgid-missing>

On Wed, Oct 24, 2001 at 11:30:33AM +0100, Richard Hirst wrote:
> 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.

This patch solves the problem.  Still surprised that cached accesses to
the video memory crash the machine though..

Richard


--- drivers/video/fbmem.c-	Wed Oct 24 15:17:36 2001
+++ drivers/video/fbmem.c	Wed Oct 24 14:50:50 2001
@@ -605,6 +605,8 @@
 	vma->vm_flags |= VM_IO;
 #elif defined(__sh__)
 	pgprot_val(vma->vm_page_prot) &= ~_PAGE_CACHABLE;
+#elif defined(__ia64__)
+	vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
 #else
 #warning What do we have to do here??
 #endif


  reply	other threads:[~2001-10-24 11:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-24 10:30 [Linux-ia64] framebuffer console Richard Hirst
2001-10-24 11:26 ` Richard Hirst [this message]
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-105590698805379@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