linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: [PATCH] More radeonfb fixes
Date: 11 Apr 2003 14:03:13 +0200	[thread overview]
Message-ID: <1050062592.562.14.camel@zion.wanadoo.fr> (raw)

Here's a new patch against 2.4.20 and 2.4.21-pre7 which brings more
fixes to radeonfb:

- Fix the M6 video RAM workaround
- Some bits in the PM code were flipped, fix that.
- RB2D_DSTCACHE_MODE shouldn't be cleared on r300 (and
  maybe not on others according to a comment in XFree, but
  we keep working code for now).
- Re-change the pitch workaround. We now align the pitch
  when accel is enabled for a given mode, and we don't when
  accel is disabled. That should properly deal with all cases
  and allows us to remove the "special case" accel code
- Bring in XFree workaround to not write the same value to
  the PLL (can cause blanking of some panels)
- Bring in some of Peter Horton fixes (accel reset, cleanups)
  still some more to get in though...
- Properly reset accel engine on each console switch so
  we work around switching from XFree leaving it in a weird
  state. Also extend the comparison of values causing us to
  reload the mode on console switch.

NOTE: The 2.4.20 patch no longer mess with non related entries
in pci_ids.h, however the 2.4.21 patch still adds a couple of
new ones not related to radeons, but that should be harmless.

Patches available at:

http://www.penguinppc.org/~benh/radeonfb-041103-2.4.20.diff
http://www.penguinppc.org/~benh/radeonfb-041103-2.4.21-pre7.diff

Ben.

             reply	other threads:[~2003-04-11 12:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 12:03 Benjamin Herrenschmidt [this message]
2003-05-01  1:19 ` [HINTS] Re: More radeonfb fixes Petr Baudis
2003-05-01 10:23   ` Benjamin Herrenschmidt

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=1050062592.562.14.camel@zion.wanadoo.fr \
    --to=benh@kernel.crashing.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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;
as well as URLs for NNTP newsgroup(s).