Thanks for your reply. Plz see inline<br><br><div class="gmail_quote">On Tue, Jul 10, 2012 at 11:50 AM, Dave Hylands <span dir="ltr"><<a href="mailto:dhylands@gmail.com" target="_blank">dhylands@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Prabhu,<br>
<div class="im"><br>
On Mon, Jul 9, 2012 at 9:56 PM, Prabhu nath <<a href="mailto:gprabhunath@gmail.com">gprabhunath@gmail.com</a>> wrote:<br>
> Dear All,<br>
><br>
> Is it possible to map a physical address of a device to a<br>
> known Kernel virtual address. I know about ioremap_xxx (...).<br>
> which will map a physical address of a device to a kernel virtual address<br>
> allocated by ioremap_xxx(...).<br>
><br>
> For E.g. I have a device whose physical address range is 0x80008000 to<br>
> 0x80008FFF.<br>
> Is it possible to map this device physical address to a known<br>
> virtual address range 0xF0008000 to 0xF0008FFF.<br>
<br>
</div>About the only way to do this is to use static mappings. I was under<br>
the impression that static mappings are on the way out, and that<br>
dynamic mappings are required when using device tree.<br>
<br>
An example of using static mappings can be found here:<br>
<a href="http://lxr.linux.no/linux+v3.4.4/arch/arm/mach-integrator/integrator_ap.c#L88" target="_blank">http://lxr.linux.no/linux+v3.4.4/arch/arm/mach-integrator/integrator_ap.c#L88</a></blockquote><div> </div><div> In this file, how did they mark IO_BASE. Is the allocator not aware of this region in the kernel virtual address space. ?</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<div class="im"><br>
> My hardware configuration has 128 MB of system RAM which will have been<br>
> MAPPED to the Kernel virtual address from 0xC0000000 to 0xC7FFFFFF<br>
><br>
> Also is it possible to configure the vmalloc kernel virtual address region<br>
> to a fixed range of 128 MB from 0xC8000000 to 0xCFFFFFFF<br>
<br>
</div>I believe that you can only control the vmalloc start by controlling<br>
the amount of SDRAM that you have.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Dave Hylands<br>
Shuswap, BC, Canada<br>
<a href="http://www.davehylands.com" target="_blank">http://www.davehylands.com</a><br>
</font></span></blockquote></div><br>