All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: John David Anglin <dave.anglin@bell.net>
Cc: Alex Ivanov <gnidorah@p0n4ik.tk>,
	Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: parisc debian kernel - missing  modules for C8000 - linux-image-3.10-2-parisc64-smp
Date: Thu, 05 Sep 2013 22:58:25 +0200	[thread overview]
Message-ID: <5228F071.4040000@gmx.de> (raw)
In-Reply-To: <BLU0-SMTP36B9C5CB7AF69063DE0EBD97320@phx.gbl>

On 09/05/2013 01:58 AM, John David Anglin wrote:
> Should have just given link:=20
> http://developer.amd.com/resources/documentation-articles/developer-g=
uides-manuals/
> It is listed near bottom as "R5xx Family 3D Programming Guide".

I found this "older" one:
http://www.x.org/docs/AMD/R5xx_Acceleration_v1.1.pdf

Maybe section 4.5 (Chips et Coherency Issues) is relevant too: ?
The Rage128 product revealed a weakness in some motherboard chipsets in=
 that there is no mechanism to guarantee
that data written by the CPU to memory is actually in a readable state =
before the Graphics Controller receives an
update to its copy of the Write Pointer. In an effort to alleviate this=
 problem, we=E2=80=9Fve introduced a mechanism into the
Graphics Controller that will delay the actual write to the Write Point=
er for some programmable amount of time, in
order to give the chipset time to flush its internal write buffers to m=
emory.
There are two register fields that control this mechanism: PRE_WRITE_TI=
MER and PRE_WRITE_LIMIT.[...]

In the radeon DRM codebase I didn't found anyone using/setting those re=
gisters.
Maybe PA-RISC has some problem here?...

Just a thought.

Helge
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
 in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-09-05 20:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <521A7589.5000503@gmx.de>
2013-08-31 17:13 ` parisc debian kernel - missing modules for C8000 - linux-image-3.10-2-parisc64-smp John David Anglin
2013-08-31 17:41   ` John David Anglin
     [not found]     ` <108451378018002@web28j.yandex.ru>
     [not found]       ` <BLU0-SMTP1273DDE4A968FD3A43C55D97370@phx.gbl>
2013-09-02  6:43         ` gnidorah
2013-09-02 14:10           ` John David Anglin
2013-09-04 18:34             ` Alex Ivanov
2013-09-04 18:36               ` Alex Ivanov
     [not found]               ` <52278FBD.2010304@bell.net>
2013-09-04 23:58                 ` John David Anglin
2013-09-05 20:58                   ` Helge Deller [this message]
2013-09-06  8:52                     ` Thomas Bogendoerfer
2013-09-06 14:12                       ` Alex Ivanov
2013-09-06 14:53                         ` Thomas Bogendoerfer
2013-09-06 14:50                       ` James Bottomley
2013-09-06 16:11                         ` Thomas Bogendoerfer
2013-09-06 17:14                           ` James Bottomley
2013-09-07 21:08                             ` John David Anglin
2013-09-17  7:23                               ` Alex Ivanov
2013-09-05  9:23                 ` Alex Ivanov
     [not found]                   ` <BLU0-SMTP629706DAEF1E3714BE163097330@phx.gbl>
2013-09-05 21:15                     ` Alex Ivanov
2013-09-05 21:35                       ` John David Anglin

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=5228F071.4040000@gmx.de \
    --to=deller@gmx.de \
    --cc=dave.anglin@bell.net \
    --cc=gnidorah@p0n4ik.tk \
    --cc=linux-parisc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.