From: Richard Hirst <rhirst@linuxcare.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] framebuffer console
Date: Sun, 04 Nov 2001 22:06:37 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805440@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805378@msgid-missing>
On Wed, Oct 24, 2001 at 04:21:08PM -0700, David Mosberger wrote:
> >>>>> On Wed, 24 Oct 2001 12:26:59 +0100, Richard Hirst <rhirst@linuxcare.com> said:
>
> Richard> This patch solves the problem. Still surprised that cached
> Richard> accesses to the video memory crash the machine though..
>
> My understanding is that Merced doesn't handle cache line sized
> transactions to the PCI bus. Instead of going uncached, you might be
> able to use write-combining (for the video framebuffer, not for memory
> mapped control registers). That can give you noticably better
> performance.
Yes, write combining works. Could you include this in your tree
please, (patch is from a 2.4.9 tree)
Thanks,
Richard
--- linux/drivers/video/fbmem.c.ori Mon Nov 5 01:53:01 2001
+++ linux/drivers/video/fbmem.c Mon Nov 5 01:53:05 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_writecombine(vma->vm_page_prot);
#else
#warning What do we have to do here??
#endif
next prev parent reply other threads:[~2001-11-04 22:06 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
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 [this message]
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-105590698805440@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