> i'm calling ioremap from
> linux/driver/mtd/maps/physmap.c and int __init
> init_physmap(void)
>
i think i found what the problem is. stupid fault the size was incorrect in the
map_info structure's .size set to 64mb instead of 128mb and that's why i
couldn't work with the upper 64mb.
will t
> The problem is that the kernel needs to ioremap the areas
> you are
i'm calling ioremap from linux/driver/mtd/maps/physmap.c and int __init
init_physmap(void)
> the
> information about the address ranges is the tricky part: it
> comes from
> the device tree, (unless you are building your ker
On Wednesday 27 August 2008, vb wrote:
> > Do I need to reinitialize Peripheral Bank Configuration Registers
> > (EBC0_B0CR-EBC0_B7CR) from the kernel ? I'm quite sure that we don't, but
> > just want to make sure. Because the problem that i'm seeing strongly
> > suggest that something isn't initia
On Tue, Aug 26, 2008 at 8:06 PM, Fundu <[EMAIL PROTECTED]> wrote:
> I have a PPC440GX based board.
>
> Do I need to reinitialize Peripheral Bank Configuration Registers
> (EBC0_B0CR-EBC0_B7CR) from the kernel ?
> I'm quite sure that we don't, but just want to make sure. Because the problem
> that
I have a PPC440GX based board.
Do I need to reinitialize Peripheral Bank Configuration Registers
(EBC0_B0CR-EBC0_B7CR) from the kernel ?
I'm quite sure that we don't, but just want to make sure. Because the problem
that i'm seeing strongly suggest that something isn't initializing.
Here's the p
5 matches
Mail list logo
