* Difference between ioremap() and phy_to_virt() Kernel function
@ 2007-10-22 10:03 Misbah khan
2007-10-22 11:04 ` Arnd Bergmann
0 siblings, 1 reply; 4+ messages in thread
From: Misbah khan @ 2007-10-22 10:03 UTC (permalink / raw)
To: linuxppc-embedded
Hi all
Could you Please let me know what is the difference between ioremap() and
phy_to_virt() function being provided by the Kernel.
--Misbah
--
View this message in context: http://www.nabble.com/Difference-between-ioremap%28%29-and-phy_to_virt%28%29-Kernel-function-tf4669833.html#a13339930
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Difference between ioremap() and phy_to_virt() Kernel function
2007-10-22 10:03 Difference between ioremap() and phy_to_virt() Kernel function Misbah khan
@ 2007-10-22 11:04 ` Arnd Bergmann
2007-10-23 4:08 ` Misbah khan
0 siblings, 1 reply; 4+ messages in thread
From: Arnd Bergmann @ 2007-10-22 11:04 UTC (permalink / raw)
To: linuxppc-embedded; +Cc: Misbah khan
On Monday 22 October 2007, Misbah khan wrote:
> Could you Please let me know what is the difference between ioremap() and
> phy_to_virt() function being provided by the Kernel.
ioremap gives you a new mapping for I/O addresses that you can access
with functions like in_be32 and the like.
phy_to_virt() is rarely used at all, it only serves to convert a physical
address for main memory (RAM) into the address used inside of the kernel.
Arnd <><
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Difference between ioremap() and phy_to_virt() Kernel function
2007-10-22 11:04 ` Arnd Bergmann
@ 2007-10-23 4:08 ` Misbah khan
2007-10-23 9:11 ` Arnd Bergmann
0 siblings, 1 reply; 4+ messages in thread
From: Misbah khan @ 2007-10-23 4:08 UTC (permalink / raw)
To: linuxppc-embedded
Thanks Arnd
But i wish to know that could i use phy_to_virt() function in place io
ioremap() ????? And could you give me an example where we could use
phy_to_virt(). ioremap() implementation i have already done.
---Misbah
Arnd Bergmann wrote:
>
> On Monday 22 October 2007, Misbah khan wrote:
>> Could you Please let me know what is the difference between ioremap() and
>> phy_to_virt() function being provided by the Kernel.
>
> ioremap gives you a new mapping for I/O addresses that you can access
> with functions like in_be32 and the like.
>
> phy_to_virt() is rarely used at all, it only serves to convert a physical
> address for main memory (RAM) into the address used inside of the kernel.
>
> Arnd <><
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
--
View this message in context: http://www.nabble.com/Difference-between-ioremap%28%29-and-phy_to_virt%28%29-Kernel-function-tf4669833.html#a13357088
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Difference between ioremap() and phy_to_virt() Kernel function
2007-10-23 4:08 ` Misbah khan
@ 2007-10-23 9:11 ` Arnd Bergmann
0 siblings, 0 replies; 4+ messages in thread
From: Arnd Bergmann @ 2007-10-23 9:11 UTC (permalink / raw)
To: linuxppc-embedded; +Cc: Misbah khan
On Tuesday 23 October 2007, Misbah khan wrote:
> But i wish to know that could i use phy_to_virt() function in place io
> ioremap() ?????
Sorry to disappoint you there, but you can't.
> And could you give me an example where we could use phy_to_virt().
Not really, I can't think of any correct use of phys_to_virt on powerpc.
Arnd <><
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-10-23 9:17 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-22 10:03 Difference between ioremap() and phy_to_virt() Kernel function Misbah khan
2007-10-22 11:04 ` Arnd Bergmann
2007-10-23 4:08 ` Misbah khan
2007-10-23 9:11 ` Arnd Bergmann
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).