public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: radeonfb broken
Date: Fri, 16 Apr 2004 11:56:03 -0400	[thread overview]
Message-ID: <40800213.8010106@techsource.com> (raw)
In-Reply-To: <20040415152507.3a0b014d.akpm@osdl.org>


Andrew Morton asked me to repost the patch for the Radeon FB off-by-one 
bug.  I'll see about making a proper patch when I get home, but if you 
want to fix it quicker, I'll just tell you what to change.


In the druvers/video/radeonfb.c, there is a function called 
fbcon_radeon_bmove.  In there, you'll see this code:

	if (srcy < dsty) {
                 srcy += height;
                 dsty += height;
         } else
                 dp_cntl |= DST_Y_TOP_TO_BOTTOM;

         if (srcx < dstx) {
                 srcx += width;
                 dstx += width;
         } else
                 dp_cntl |= DST_X_LEFT_TO_RIGHT;


Those adds need to be reduced by one.  The code should look like this:


	if (srcy < dsty) {
                 srcy += height - 1;
                 dsty += height - 1;
         } else
                 dp_cntl |= DST_Y_TOP_TO_BOTTOM;

         if (srcx < dstx) {
                 srcx += width - 1;
                 dstx += width - 1;
         } else
                 dp_cntl |= DST_X_LEFT_TO_RIGHT;



This bug is in the mainline kernel, and since I have direct experience 
programming for the Radeon, I knew how to fix it, but I also noticed 
that the Red Hat kernel "2.4.18-27.7.x" has the proper fix in it.


Whenever I download a new 2.4 kernel for gentoo, I have to manually make 
that fix.  I'm also disappointed that acceleration for Radeon has 
disappeared completely from 2.6.


  parent reply	other threads:[~2004-04-16 15:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15 20:25 radeonfb broken Felix von Leitner
2004-04-15 21:13 ` Timothy Miller
2004-04-16  1:43   ` Benjamin Herrenschmidt
2004-04-16 15:58     ` Timothy Miller
2004-04-17  0:22       ` Benjamin Herrenschmidt
2004-04-19 14:18         ` Timothy Miller
2004-04-19 22:36           ` Benjamin Herrenschmidt
2004-04-16 16:06     ` Timothy Miller
2004-04-16 16:40       ` Randy.Dunlap
     [not found]   ` <20040415152507.3a0b014d.akpm@osdl.org>
2004-04-16 15:56     ` Timothy Miller [this message]
2004-04-16 20:34       ` James Simmons
2004-04-16 21:05         ` Timothy Miller
2004-04-19  2:18   ` David Eger
2004-04-16  1:46 ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2004-04-20 21:09 David Eger

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=40800213.8010106@techsource.com \
    --to=miller@techsource.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@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