From: Ralf Baechle <ralf@linux-mips.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Vivien Chappelier <vivienc@nerim.net>,
linux-mips@linux-mips.org, Ilya Volynets <ilya@theIlya.com>
Subject: Re: [PATCH 2.5] SGI O2 framebuffer driver
Date: Thu, 12 Dec 2002 03:33:07 +0100 [thread overview]
Message-ID: <20021212033307.C22987@linux-mips.org> (raw)
In-Reply-To: <1039656676.18587.63.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Thu, Dec 12, 2002 at 01:31:16AM +0000
On Thu, Dec 12, 2002 at 01:31:16AM +0000, Alan Cox wrote:
> On Wed, 2002-12-11 at 23:41, Vivien Chappelier wrote:
> > linear framebuffer (up to 8MB with 64kB granularity). I'm then remapping
> > all those pages to one virtual region obtained from get_vm_area so that
> > 1. caching attributes can be set to cacheable write-through no WA
>
> Ick. The framebuffer can't handle cached and write barriers ?
The O2 is non-cache coherent. So with the fairly large write-back second
level caches enabled frame buffer write could potencially be delayed
indefinately but in any case quite long. Frame buffers are usually only
written to, so the cache mode "uncached accelerated" seems preferable
but only the R10000 provides this mode, so for the R5000 write-though no
write allocation is the next best solution.
Ralf
next prev parent reply other threads:[~2002-12-12 2:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020903205816.A25897@linux-mips.org>
2002-12-11 22:25 ` [PATCH 2.5] SGI O2 framebuffer driver Vivien Chappelier
2002-12-11 23:15 ` Alan Cox
2002-12-11 23:41 ` Vivien Chappelier
2002-12-12 1:31 ` Alan Cox
2002-12-12 2:33 ` Ralf Baechle [this message]
2002-12-12 12:44 ` Alan Cox
2002-12-12 12:20 ` Ralf Baechle
2002-12-12 12:52 ` Dominic Sweetman
2002-12-12 14:07 ` Ralf Baechle
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=20021212033307.C22987@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ilya@theIlya.com \
--cc=linux-mips@linux-mips.org \
--cc=vivienc@nerim.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.