From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Miller <davem@davemloft.net>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [PATCH]: radeonfb: Fix copyarea for R300 and later.
Date: Thu, 7 Aug 2008 13:22:42 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0808071322080.23641@anakin> (raw)
In-Reply-To: <1218088369.24157.268.camel@pasglop>
Hi Ben,
On Thu, 7 Aug 2008, Benjamin Herrenschmidt wrote:
> > + /* Ensure the dst cache is flushed and the engine idle before
> > + * issuing the operation.
> > + *
> > + * This works around engine lockups on some cards
> > + */
> > + OUTREG(DSTCACHE_CTLSTAT, RB2D_DC_FLUSH_ALL);
> > + OUTREG(WAIT_UNTIL, (WAIT_2D_IDLECLEAN | WAIT_DMA_GUI_IDLE));
> > +
> > radeon_fifo_wait(2);
>
> Typo in the patch, missing radeon_fifo_wait before the cache flush.
>
> Fixed version on it's way, sorry.
Can we please get a CC: linux-fbdev-devel on the fixed version?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2008-08-07 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 7:35 David Miller
2008-08-06 15:43 ` Andrew Morton
2008-08-06 21:19 ` David Miller
2008-08-06 22:08 ` Benjamin Herrenschmidt
2008-08-07 2:06 ` Benjamin Herrenschmidt
2008-08-07 5:52 ` Benjamin Herrenschmidt
2008-08-07 11:22 ` Geert Uytterhoeven [this message]
2008-08-07 21:24 ` Benjamin Herrenschmidt
2008-08-07 8:52 ` [PATCH] radeonfb: Fix engine hangs and cache flushing (v2) Benjamin Herrenschmidt
2008-08-06 22:09 ` [PATCH]: radeonfb: Fix copyarea for R300 and later 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=Pine.LNX.4.64.0808071322080.23641@anakin \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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
Powered by JetHome