Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: "Houten K.H.C. van (Karel)" <vhouten@kpn.com>, linux-mips@oss.sgi.com
Subject: Re: DECStation: Support for PMAZ-AA TC SCSI card?
Date: Mon, 22 Jul 2002 15:44:05 +0200	[thread overview]
Message-ID: <20020722154405.A29300@dea.linux-mips.net> (raw)
In-Reply-To: <Pine.GSO.3.96.1020722132706.2373A-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Mon, Jul 22, 2002 at 02:21:13PM +0200

On Mon, Jul 22, 2002 at 02:21:13PM +0200, Maciej W. Rozycki wrote:

>  I hope so.  I'm begging Ralf for about half a year, sigh...  The subject
> was beaten to death at the list and the feedback looked positive to me
> (after a few doubts were resolved), but Ralf seems to be unhappy with the
> changes due to some ia64 interactions (I'm still not sure which ones,
> though).  Ralf, could you please elaborate? 
> 
>  Otherwise, your case convinces me I should not care about purity or
> cross-platform consistency of code in this area, anymore.  I've been
> observing problems with interrupts due to the lack of iomem access
> synchronization already, but unlike for your PMAZ-A problem, their result
> was more of annoyance than instability.  Since stability is a priority,
> although reluctantly, I will rework the changes to apply to the DECstation
> code only, to keep others happy.  The interface won't change, apart from
> resolving namespace clashes.

We had some discussion with the IA64 guys at SGI on how to handle this
kind of I/O ordering issues.  We never came to a final conclusion but
the proposal was the introduction of separate memory barriers macros for
I/O stuff.  Anyway, I think for the moment we should go with your proposal.

  Ralf

  reply	other threads:[~2002-07-22 13:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-15  9:40 DECStation: Support for PMAZ-AA TC SCSI card? Houten K.H.C. van (Karel)
2002-07-16 13:41 ` Maciej W. Rozycki
2002-07-16 16:59   ` Karel van Houten
2002-07-16 16:59     ` Karel van Houten
2002-07-17  9:05     ` Maciej W. Rozycki
2002-07-17 12:16       ` Houten K.H.C. van (Karel)
2002-07-17 13:35         ` Maciej W. Rozycki
2002-07-17 18:30           ` Houten K.H.C. van (Karel)
2002-07-18 14:27             ` Maciej W. Rozycki
2002-07-18 15:19               ` Karel van Houten
2002-07-18 15:19                 ` Karel van Houten
2002-07-18 16:39                 ` Maciej W. Rozycki
2002-07-19 17:08                   ` Houten K.H.C. van (Karel)
2002-07-22 12:21                     ` Maciej W. Rozycki
2002-07-22 13:44                       ` Ralf Baechle [this message]
2002-07-22 17:32                         ` Maciej W. Rozycki
2002-07-22 18:42                           ` Ralf Baechle
2002-07-19 10:21               ` Dave Airlie
2002-07-19 10:21                 ` Dave Airlie
2002-07-19 11:40                 ` Maciej W. Rozycki

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=20020722154405.A29300@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    --cc=vhouten@kpn.com \
    /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