linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Brian Kuschak <bkuschak@yahoo.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: virt_to_phys() on 440
Date: Mon, 8 Sep 2003 15:14:59 -0700	[thread overview]
Message-ID: <20030908151459.A16761@home.com> (raw)
In-Reply-To: <20030908213638.4000.qmail@web40910.mail.yahoo.com>; from bkuschak@yahoo.com on Mon, Sep 08, 2003 at 02:36:38PM -0700


On Mon, Sep 08, 2003 at 02:36:38PM -0700, Brian Kuschak wrote:
>
> I think the virt_to_phys() function is incorrect for
> PPC440.  It should call iopa for all 4xx, not only the
> 405.  By chance, it happens to work currently if the
> address is in SDRAM, but is always incorrect for
> ioremapped addresses.  virt_to_bus() does the right
> thing.
>
> Also, to be correct, shouldn't this function return a
> phys_addr_t rather than an unsigned long, as the
> physical address is >32 bits on 44x?

Read IO-mapping.txt and DMA-mapping.txt

PPC40x is incorrect.  These APIs are valid only for system
memory kernel addresses that are staticly mapped.

Anything wanting a generic translation from virt->phys should
call iopa() directly until somebody drives a generic translation
API into the kernel.

-Matt

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2003-09-08 22:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08 21:36 virt_to_phys() on 440 Brian Kuschak
2003-09-08 22:03 ` Dan Malek
2003-09-08 22:08 ` Eugene Surovegin
2003-09-08 22:14 ` Matt Porter [this message]
2003-09-08 22:36   ` Brian Kuschak
2003-09-08 23:26     ` Matt Porter

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=20030908151459.A16761@home.com \
    --to=mporter@kernel.crashing.org \
    --cc=bkuschak@yahoo.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).