Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: peter fuerst <pf@pfrst.de>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Kumba <kumba@gentoo.org>, Ralf Baechle <ralf@linux-mips.org>,
	linux-mips@linux-mips.org
Subject: Re: [UPDATED PATCH] IP28 support
Date: Wed, 05 Dec 2007 12:37:59 -0800	[thread overview]
Message-ID: <47570C27.9050901@avtrex.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0712051841520.1354@Opal.Peter>

peter fuerst wrote:
> 
> On Wed, 5 Dec 2007, Thomas Bogendoerfer wrote:
> 
>> Date: Wed, 5 Dec 2007 10:39:38 +0100
>> From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
>> To: Kumba <kumba@gentoo.org>
>> Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
>> Subject: Re: [UPDATED PATCH] IP28 support
>>
>> On Wed, Dec 05, 2007 at 01:16:13AM -0500, Kumba wrote:
>>> I've been out of it lately -- did the gcc side of things ever make it in,
>>> or do we need to go push on that some more?
>> We need push on that. ...
> 
> There was no answer to .../2006-05/msg01446.html. Perhaps i should just
> put together an updated patch,

That would be helpful.  It would have to be against GCC's svn trunk. 
Currently 4.3 is in regression fix only mode.  The earliest the patch 
could appear in an official GCC release would probably be version 4.4


> that incorporates the changes proposed in
> msg01446.html, and submit it (with the longer "Cc:" line and a hint to
> the increasing demand for it ;-) to revive at least the discussion at
> gcc-patches.

Just sent it to gcc-patches@   I think it will be noticed.


> What could be changed beyond the proposed changes without either omitting
> necessary cache-barriers or crippling the R10k, i can't see yet.
> 
>> We need push on that. Looking at
>>
>> http://gcc.gnu.org/ml/gcc-patches/2006-04/msg00291.html
>>
>> 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...
> 
>> Peter did you do the copyright assigment ? That's probably
>> the second part, which needs to be done.
> 
> Yes, the assignment process became complete on May 22 2006
> (though apparently i missed to notify Richard Sandiford about it)
> 

Good.  Richard is generally quite responsive to patches.  Perhaps CC him 
on your patch.

David Daney

  reply	other threads:[~2007-12-05 20:38 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 [this message]
2007-12-06 11:44           ` Ralf Baechle
2007-12-06 11:41         ` Ralf Baechle
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=47570C27.9050901@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=kumba@gentoo.org \
    --cc=linux-mips@linux-mips.org \
    --cc=pf@pfrst.de \
    --cc=ralf@linux-mips.org \
    --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