Re: [RFC PATCH 14/19] powerpc: allow ioremap within reserved fake ram regions

2009-11-26 Thread Benjamin Herrenschmidt
On Thu, 2009-11-26 at 16:35 +0100, Albert Herranz wrote: > Benjamin Herrenschmidt wrote: > > On Tue, 2009-11-24 at 18:09 +0100, Albert Herranz wrote: > >> I could use ppc_md.ioremap to duplicate ioremap except for the ioremap > >> ram check. > >> But calling the stock ioremap without modifying it i

Re: [RFC PATCH 14/19] powerpc: allow ioremap within reserved fake ram regions

2009-11-26 Thread Albert Herranz
Benjamin Herrenschmidt wrote: > On Tue, 2009-11-24 at 18:09 +0100, Albert Herranz wrote: >> I could use ppc_md.ioremap to duplicate ioremap except for the ioremap >> ram check. >> But calling the stock ioremap without modifying it is not possible >> because it checks and bails out when ioremapping

Re: [RFC PATCH 14/19] powerpc: allow ioremap within reserved fake ram regions

2009-11-25 Thread Benjamin Herrenschmidt
On Tue, 2009-11-24 at 18:09 +0100, Albert Herranz wrote: > I could use ppc_md.ioremap to duplicate ioremap except for the ioremap > ram check. > But calling the stock ioremap without modifying it is not possible > because it checks and bails out when ioremapping a region marked as > ram (even if it

Re: [RFC PATCH 14/19] powerpc: allow ioremap within reserved fake ram regions

2009-11-24 Thread Michael Ellerman
On Tue, 2009-11-24 at 18:09 +0100, Albert Herranz wrote: > Michael Ellerman wrote: > >> Would it be acceptable to create a global var __allow_ioremap_normal_ram > >> that by default would have a value of 0 and would be set _only_ for those > >> platforms needing it? > >> > >> The other solutions

Re: [RFC PATCH 14/19] powerpc: allow ioremap within reserved fake ram regions

2009-11-24 Thread Albert Herranz
Michael Ellerman wrote: >> Would it be acceptable to create a global var __allow_ioremap_normal_ram >> that by default would have a value of 0 and would be set _only_ for those >> platforms needing it? >> >> The other solutions I see is: >> - add support for discontiguous memory to powerpc 32-bit

Re: [RFC PATCH 14/19] powerpc: allow ioremap within reserved fake ram regions

2009-11-23 Thread Michael Ellerman
On Mon, 2009-11-23 at 21:16 +0100, Albert Herranz wrote: > >> arch/powerpc/mm/pgtable_32.c | 19 --- > >> 1 files changed, 16 insertions(+), 3 deletions(-) > >> > >> diff --git a/arch/powerpc/mm/pgtable_32.c b/arch/powerpc/mm/pgtable_32.c > >> index cb96cb2..ba00cb1 100644 > >> -

Re: [RFC PATCH 14/19] powerpc: allow ioremap within reserved fake ram regions

2009-11-23 Thread Grant Likely
On Mon, Nov 23, 2009 at 1:16 PM, Albert Herranz wrote: > Grant Likely wrote: >> On Sun, Nov 22, 2009 at 3:01 PM, Albert Herranz >> wrote: >>> The Nintendo Wii has two discontiguous RAM memory areas called >>> MEM1 and MEM2. >>> MEM1 starts at 0x and contains 24MB of 1T-SRAM. >>> MEM2 sta

Re: [RFC PATCH 14/19] powerpc: allow ioremap within reserved fake ram regions

2009-11-23 Thread Albert Herranz
Grant Likely wrote: > On Sun, Nov 22, 2009 at 3:01 PM, Albert Herranz > wrote: >> The Nintendo Wii has two discontiguous RAM memory areas called >> MEM1 and MEM2. >> MEM1 starts at 0x and contains 24MB of 1T-SRAM. >> MEM2 starts at 0x1000 and contains 64MB of DDR2 RAM. >> Between both

Re: [RFC PATCH 14/19] powerpc: allow ioremap within reserved fake ram regions

2009-11-22 Thread Grant Likely
On Sun, Nov 22, 2009 at 3:01 PM, Albert Herranz wrote: > The Nintendo Wii has two discontiguous RAM memory areas called > MEM1 and MEM2. > MEM1 starts at 0x and contains 24MB of 1T-SRAM. > MEM2 starts at 0x1000 and contains 64MB of DDR2 RAM. > Between both memory address ranges there i

[RFC PATCH 14/19] powerpc: allow ioremap within reserved fake ram regions

2009-11-22 Thread Albert Herranz
The Nintendo Wii has two discontiguous RAM memory areas called MEM1 and MEM2. MEM1 starts at 0x and contains 24MB of 1T-SRAM. MEM2 starts at 0x1000 and contains 64MB of DDR2 RAM. Between both memory address ranges there is an address space where memory-mapped I/O registers are found. C