From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Kars de Jong <jongk@linux-m68k.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [SCSI] sun3x_esp: convert to esp_scsi
Date: Mon, 11 Feb 2008 09:18:26 -0600 [thread overview]
Message-ID: <1202743106.3122.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20080211112453.GA7761@alpha.franken.de>
On Mon, 2008-02-11 at 12:24 +0100, Thomas Bogendoerfer wrote:
> On Sun, Feb 10, 2008 at 10:38:15AM +0100, Kars de Jong wrote:
> > Thomas, can't you use ioreadxx() and friends instead of rolling your own
> > memory mapped I/O handlers?
>
> well, at least ioread32be/iowrite32be are looking promising, but a quick
> grep didn't show them for m68k.
Someone could submit a patch ...
> > readxx() and friends are only to be used on PCI-like buses.
>
> hmm, afaik readxx/writexx is not directly related to PCI. It's
> like ioread/iowrite to access iomapped address space. The difference
> to ioread/iowrite is that it doesn't support PCI IO space.
That's correct ... at least that's the meaning we've ascribed on other
architectures I've worked on. Any ioremap'd memory area can be accessed
by readX/writeX. The current list of Buses I know it works on is MCA,
EISA, GSC, Runway ... in addition to PCI.
James
prev parent reply other threads:[~2008-02-11 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200802080259.m182xDkb014716@hera.kernel.org>
[not found] ` <Pine.LNX.4.64.0802080932220.18242@anakin>
2008-02-10 9:38 ` [SCSI] sun3x_esp: convert to esp_scsi Kars de Jong
2008-02-11 11:24 ` Thomas Bogendoerfer
2008-02-11 15:18 ` James Bottomley [this message]
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=1202743106.3122.5.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=jongk@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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