On 12/20/06, Franck Bui-Huu <[email protected]> wrote:
- when mmaping your frame buffer , be sure that the virtual
address returned by mmap() to the application shares the
same cache lines than the ones the kernel
is using.
Well thinking more about it, this wouldn't work for all cache types.
For example, if your cache is not a direct maped one, this workaround
won't work. So this is definitely not a portable solution.
--
Franck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [RFC 2.6.19 1/1] fbdev,mm: hecuba/E-Ink fbdev driver v2
- From: "Jaya Kumar" <[email protected]>
- Re: [RFC 2.6.19 1/1] fbdev,mm: hecuba/E-Ink fbdev driver v2
- References:
- [RFC 2.6.19 1/1] fbdev,mm: hecuba/E-Ink fbdev driver v2
- From: [email protected]
- Re: [RFC 2.6.19 1/1] fbdev,mm: hecuba/E-Ink fbdev driver v2
- From: Franck Bui-Huu <[email protected]>
- Re: [RFC 2.6.19 1/1] fbdev,mm: hecuba/E-Ink fbdev driver v2
- From: "Jaya Kumar" <[email protected]>
- Re: [RFC 2.6.19 1/1] fbdev,mm: hecuba/E-Ink fbdev driver v2
- From: "Franck Bui-Huu" <[email protected]>
- Re: [RFC 2.6.19 1/1] fbdev,mm: hecuba/E-Ink fbdev driver v2
- From: "Jaya Kumar" <[email protected]>
- Re: [RFC 2.6.19 1/1] fbdev,mm: hecuba/E-Ink fbdev driver v2
- From: "Franck Bui-Huu" <[email protected]>
- [RFC 2.6.19 1/1] fbdev,mm: hecuba/E-Ink fbdev driver v2
- Prev by Date: Re: Binary Drivers
- Next by Date: Re: [PATCH] mm: fix page_mkclean_one (was: 2.6.19 file content corruption on ext3)
- Previous by thread: Re: [RFC 2.6.19 1/1] fbdev,mm: hecuba/E-Ink fbdev driver v2
- Next by thread: Re: [RFC 2.6.19 1/1] fbdev,mm: hecuba/E-Ink fbdev driver v2
- Index(es):
 |