public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	"David S. Miller" <davem@davemloft.net>,
	matthew@wil.cx, SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: iomapping a big endian area
Date: Mon, 04 Apr 2005 09:25:05 -0500	[thread overview]
Message-ID: <1112624705.5813.19.camel@mulgrave> (raw)
In-Reply-To: <20050404141616.GA10384@infradead.org>

On Mon, 2005-04-04 at 15:16 +0100, Christoph Hellwig wrote:
> The IOC4 device that provides IDE, serial ports and external interrupts
> on Altix systems has a big endian register layour, and the PCI-X bridge
> in those Altix systems can do the swapping if a special bit is set.
> 
> In older kernels that bit was set from the driver through a special API,
> but it seems the firmware does that automatically now.

We already have some unusual code in drivers to support other altix
design ... features ... do you regard this as something that's likely to
be replicated on other platforms, or is it more in the category of a one
off mistake that can be corrected in firmware?

James



  reply	other threads:[~2005-04-04 14:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-02 20:52 [PATCH] finally fix 53c700 to use the generic iomem infrastructure James Bottomley
2005-04-03  1:37 ` iomapping a big endian area Matthew Wilcox
2005-04-03  2:38   ` David S. Miller
2005-04-03  3:10     ` Matthew Wilcox
2005-04-03  3:40       ` James Bottomley
2005-04-03  4:08         ` David S. Miller
2005-04-03  4:27           ` James Bottomley
2005-04-04  7:50             ` Benjamin Herrenschmidt
2005-04-04 13:59               ` James Bottomley
2005-04-04 14:16                 ` Christoph Hellwig
2005-04-04 14:25                   ` James Bottomley [this message]
2005-04-07 23:57                     ` Jesse Barnes
2005-04-04 14:22                 ` Randy.Dunlap
2005-04-04 23:41                   ` Benjamin Herrenschmidt
2005-04-04 23:43                 ` Benjamin Herrenschmidt
2005-04-04  7:49         ` Benjamin Herrenschmidt
2005-04-05  7:42         ` Russell King
2005-04-05 14:05           ` James Bottomley
2005-04-05 18:55             ` Russell King
2005-04-05 20:02               ` Maciej W. Rozycki
2005-04-04 21:17   ` James Bottomley
2005-04-05  7:21     ` Christoph Hellwig
2005-04-05 14:05       ` James Bottomley

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=1112624705.5813.19.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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