From: Richard Zidlicky <rz@linux-m68k.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: davem@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: readsw/writesw readsl/writesl
Date: Thu, 29 Aug 2002 11:17:44 +0200 [thread overview]
Message-ID: <20020829111744.A223@linux-m68k.org> (raw)
In-Reply-To: <20020828161701.22623@192.168.4.1>; from benh@kernel.crashing.org on Wed, Aug 28, 2002 at 06:17:01PM +0200
On Wed, Aug 28, 2002 at 06:17:01PM +0200, Benjamin Herrenschmidt wrote:
> Another possibility (that looks saner to me) would be to define that
> the IO macros take all a parameter which represents the bus (or rather
> the device pointer in the new driver model). Most archs would just
> ignore that macro parameter and so have exactly equivalent code as
> we have today, but that let archs that feel they need it to actually
> use that to go pick the proper access methods for that device.
that would certainly solve all problems.
> In all cases, though, I would keep the distinction between {read,write}*
> and {in,out}* as there are PCI drivers that will need to mix them.
sure, it makes a difference even on m68k ISA buses.
Richard
next prev parent reply other threads:[~2002-08-29 9:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 16:00 readsw/writesw readsl/writesl Richard.Zidlicky
2002-08-27 9:29 ` Benjamin Herrenschmidt
2002-08-28 12:23 ` Richard Zidlicky
2002-08-28 16:17 ` Benjamin Herrenschmidt
2002-08-29 9:17 ` Richard Zidlicky [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-27 6:11 [BKPATCH] Read-Copy Update 2.5 David S. Miller
2002-08-27 6:23 ` readsw/writesw readsl/writesl Andre Hedrick
2002-08-27 6:43 ` David S. Miller
2002-08-27 6:55 ` Andre Hedrick
2002-08-27 7:30 ` David S. Miller
2002-08-27 6:46 ` Benjamin Herrenschmidt
2002-08-27 6:49 ` Benjamin Herrenschmidt
2002-08-27 17:25 ` Alan Cox
2002-08-27 21:31 ` David S. Miller
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=20020829111744.A223@linux-m68k.org \
--to=rz@linux-m68k.org \
--cc=benh@kernel.crashing.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.