Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: peter fuerst <pf@pfrst.de>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Kumba <kumba@gentoo.org>,
	linux-mips@linux-mips.org
Subject: Re: [UPDATED PATCH] IP28 support
Date: Thu, 6 Dec 2007 11:41:03 +0000	[thread overview]
Message-ID: <20071206114103.GA6498@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0712051841520.1354@Opal.Peter>

On Wed, Dec 05, 2007 at 08:49:53PM +0100, peter fuerst wrote:

> > there seems to be a missing understanding, why the cache
> > barriers are needed. I guess the patch could be improved
> > by pointing directly to the errata section of the R10k
> > user manual. Or even better copy the text out of the user
> > manual. That should make clear why this patch is needed.
> 
> Better copy, i guess. (Assuming copying whole paragraphs is still proper
> citation ;-) Along with the initial patch (.../2006-03.msg00090.html) as
> well as in the last letter so far (.../2006-05/msg01446.html) i pointed
> to the corresponding chapter in the R10k User's Manual and to the entry
> in the NetBSD eMail archive. In the last letter i tried to augment these
> by a summarizing explanation, but it seems i'm not very good at that...

I'm not sure how far "fair use" of the R10000 manual text can be stretched.
But afair Bill Earl (wje@sgi.com) posted a reasonable explanation which
also for the purposes of the gcc manual is much easier to understand.

  Ralf

  parent reply	other threads:[~2007-12-06 11:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29  9:54 [UPDATED PATCH] IP28 support Thomas Bogendoerfer
2007-11-29 13:01 ` Ralf Baechle
2007-12-05  6:16   ` Kumba
2007-12-05  9:39     ` Thomas Bogendoerfer
2007-12-05 19:49       ` peter fuerst
2007-12-05 20:37         ` David Daney
2007-12-06 11:44           ` Ralf Baechle
2007-12-06 11:41         ` Ralf Baechle [this message]
2007-12-08 17:52       ` Richard Sandiford
2007-12-08 17:52         ` Richard Sandiford
2007-12-08 19:24         ` Ralf Baechle
2007-12-08 20:09           ` Richard Sandiford
2007-12-08 21:25             ` peter fuerst
2007-12-08 23:24               ` Richard Sandiford
2007-12-09  4:38             ` Ralf Baechle
2007-12-10 11:00               ` Richard Sandiford
2007-12-12 15:26                 ` peter fuerst
2007-12-12 18:09                   ` Richard Sandiford
2007-12-12 18:22                     ` Richard Sandiford
  -- strict thread matches above, loose matches on Subject: below --
2007-12-02 12:00 Thomas Bogendoerfer
2007-12-23  1:44 peter fuerst
2007-12-23  9:39 ` Richard Sandiford
2007-12-24  0:39   ` post
2008-01-16 19:32   ` peter fuerst
2008-01-19 14:14     ` Richard Sandiford
2008-01-19 23:56       ` post

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=20071206114103.GA6498@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=kumba@gentoo.org \
    --cc=linux-mips@linux-mips.org \
    --cc=pf@pfrst.de \
    --cc=tsbogend@alpha.franken.de \
    /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