the concept of "remap" is to map again, thus, if u call ioremap()
multiple times, u will just remove the previous mapping setup. This
is implied in the source for ioremap() - delved down all the way to
where the PTE is setup. the reason for this is because the MMU
translation process is hardwar
On Sat, May 28, 2011 at 00:48, anish singh wrote:
>
>
> On Fri, May 27, 2011 at 10:54 PM, Mulyadi Santosa
> wrote:
>>
>> Hi...
>>
>> On Fri, May 27, 2011 at 17:49, sandeep kumar
>> wrote:
>> > Now the question is can we memory map a one device resource(say some
>> > iomemory) to two different me
On Fri, May 27, 2011 at 10:54 PM, Mulyadi Santosa wrote:
> Hi...
>
> On Fri, May 27, 2011 at 17:49, sandeep kumar
> wrote:
> > Now the question is can we memory map a one device resource(say some
> > iomemory) to two different memory locations?
> > the other way of seeing at this question is,
>
Hi...
On Fri, May 27, 2011 at 17:49, sandeep kumar wrote:
> Now the question is can we memory map a one device resource(say some
> iomemory) to two different memory locations?
> the other way of seeing at this question is,
> Will ioremap() gives different 'virtual addresses' when called multiple
On Fri, May 27, 2011 at 1:49 PM, sandeep kumar
wrote:
> Hi all,
> Memory mapping is done so that CPU can access the devices, which it cant
> unless.
>
> Now the question is can we memory map a one device resource(say some
> iomemory) to two different memory locations?
> the other way of seeing at
Hi all,
Memory mapping is done so that CPU can access the devices, which it cant
unless.
Now the question is can we memory map a one device resource(say some
iomemory) to two different memory locations?
the other way of seeing at this question is,
Will ioremap() gives different 'virtual addresses'
