From: Dan Malek <dan@mvista•com>
To: mod+linuxppc-embedded@world-f•std.com
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: How does one get physical address for iorempped window?
Date: Mon, 19 Feb 2001 14:53:15 -0500 [thread overview]
Message-ID: <3A9179AB.17D56F36@mvista.com> (raw)
In-Reply-To: 200102191915.OAA29416@world.std.com
mod+linuxppc-embedded@world-f•std.com wrote:
> ..... Being able to refer to something like, say,
> the appropriate pci_bus* when invoking virt_to_bus()
Right, you have to provide enough information to get the
job done correctly, but this could be more generic. Adding
pci_bus* to virt_to_bus is the right concept, but the wrong
implementation as I certainly want to use virt_to_bus() (or
whatever) for devices that are not on a PCI bus.
> ... I'm certainly not a fan of pointlessly
> complex code, but the one-size-fits-all implementation
> of virt_to_bus()....
That's not a one-size-fits-all implementation :-). It (and
virt_to_phys()) worked differently on at least three different
PowerPC implementations. Mainly to eliminate a bunch of nested
#ifdefs and duplicated code, I now use the same implementation
on all PowerPCs, but it is just the first small step to doing
something better.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-19 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-19 19:15 How does one get physical address for iorempped window? mod+linuxppc-embedded
2001-02-19 19:53 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-19 21:12 mod+linuxppc-embedded
2001-02-15 17:58 Subodh Nijsure
2001-02-15 18:10 ` Dan Malek
2001-02-18 16:28 ` Matt Porter
2001-02-19 17:59 ` Dan Malek
2001-02-15 16:05 Subodh Nijsure
2001-02-15 17:03 ` Dan Malek
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=3A9179AB.17D56F36@mvista.com \
--to=dan@mvista$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=mod+linuxppc-embedded@world-f$(echo .)std.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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