From: Jeff Garzik <jgarzik@pobox.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-arch@vger.kernel.org
Subject: Re: Add skeleton "generic IO mapping" infrastructure.
Date: Tue, 14 Sep 2004 11:08:02 -0400 [thread overview]
Message-ID: <41470952.5080108@pobox.com> (raw)
In-Reply-To: <1095173761.24547.203.camel@hades.cambridge.redhat.com>
David Woodhouse wrote:
> No, seriously, let's not introduce a new API which is _already_
> insufficient to disambiguate between the various things the caller might
> want. A 'void *' is not sufficient to give both bus and address. Use a
> tuple of { bus, addr } or { dev, addr } instead.
The existing setup is perfectly sufficient.
You pass (dev,addr) to an arch-specific function which creates the
cookie in an arch-specific manner.
Jeff
prev parent reply other threads:[~2004-09-14 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200409132206.i8DM6dSC030620@hera.kernel.org>
[not found] ` <1095152147.9144.254.camel@imladris.demon.co.uk>
[not found] ` <41470074.9010900@pobox.com>
2004-09-14 14:56 ` Add skeleton "generic IO mapping" infrastructure David Woodhouse
2004-09-14 15:08 ` Jeff Garzik [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=41470952.5080108@pobox.com \
--to=jgarzik@pobox.com \
--cc=dwmw2@infradead.org \
--cc=linux-arch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).