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 is not possible > >> because it checks and bails out when ioremapping a region marked as > >> ram (even if it's not real ram and it's memreserved). > >> > >> Is the list of memreserved areas preserved once the kernel is running? > >> If it is preserved another option would be to unban ioremapping ram if > >> memreserved. > > > > Yes, check lmb's they should still be around. > > > > Good. > So adding a kconfig option to allow ioremapping memreserved memory marked > as ram and adding a proper check (under that kconfig) to unban this case > in ioremap would be an acceptable solution?
Don't even make it Kconfig. Stick it under you GAMECUBE_COMMON for now or CONFIG_WII or whatever. This is temporary until we sort out the whole disctontig mem issue. Cheers, Ben. > > Cheers, > > Ben. > > > > Thanks, > Albert _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
