lkml.org 
[lkml]   [2000]   [Jul]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: phys-to-virt kernel mapping and ioremap()
From
Date
>>>>> "Timur" == Timur Tabi <ttabi@interactivesi.com> writes:

Timur> ** Reply to message from Jes Sorensen <jes@linuxcare.com> on 20
Timur> Jul 2000 20:41:51 +0200


Timur> 1) Doesn't this mapping break the phys_to_virt and virt_to_phys
Timur> macros?
>> Those two macros are not defined on ioremap'ed regions so it is
>> irrelevant.

Timur> In that case, how do I do virt-to-phys and phys-to-virt
Timur> translations on the memory addresses for ioremap'ed regions?

The answer is that you don't because you don't need to. You use
ioremap to mape it and you usae real/writel to access the space. You
are not allowed to treat PCI shared memory as regular memory.

Jes

PS: Please fix your mailer, it eats the References lines which is
really broken.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:57    [W:0.038 / U:0.416 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site