From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: adaplas@pol.net, linux-fbdev-devel@lists.sourceforge.net,
Andrew Walrond <andrew@walrond.org>
Subject: Re: x86_64 64bit kernel rivafb broke between 2.6.8.1 and linus bk as of today
Date: Thu, 18 Nov 2004 06:28:14 +0800 [thread overview]
Message-ID: <200411180628.14510.adaplas@hotpop.com> (raw)
In-Reply-To: <200411180623.28248.adaplas@hotpop.com>
On Thursday 18 November 2004 06:23, Antonino A. Daplas wrote:
> On Wednesday 17 November 2004 19:07, Andrew Walrond wrote:
> > On Wednesday 17 Nov 2004 00:33, Andrew Walrond wrote:
> > > On Wednesday 17 Nov 2004 00:15, Antonino A. Daplas wrote:
> I was suspecting imageblit, I never suspected fillrect. Anyway, can you
> try the 2 patches attached. The first patch reverts io access to the old
> method (direct pointer loading/reading and forced alignment) and the second
> uses __raw_{read|write} but forces alignment. You need to reverse the
> previous patch before applying the other.
Umm, forget about the first patch, just apply the second patch.
Thanks.
Tony
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
next prev parent reply other threads:[~2004-11-17 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 22:44 x86_64 64bit kernel rivafb broke between 2.6.8.1 and linus bk as of today Andrew Walrond
2004-11-16 23:29 ` Andrew Walrond
2004-11-17 0:01 ` Andrew Walrond
2004-11-17 0:15 ` Antonino A. Daplas
2004-11-17 0:33 ` Andrew Walrond
2004-11-17 11:07 ` Andrew Walrond
2004-11-17 11:11 ` Geert Uytterhoeven
2004-11-17 11:34 ` Andrew Walrond
2004-11-17 22:23 ` Antonino A. Daplas
2004-11-17 22:28 ` Antonino A. Daplas [this message]
2004-11-17 22:50 ` Andrew Walrond
2004-11-18 0:02 ` 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=200411180628.14510.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=andrew@walrond.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).