to increase size. # of-flash f0000000.bootflash: Failed to ioremap() flash = region # of-flash: probe of f0000000.bootflash failed with error -12 It seems ioremap call during mtd initialization is failing. The flash partitions are created through the device tree as follows, ranges =3D <0 0 0xf0000000 0x10000000 >; // 256MB Boot = flash =20 bootflash@0,0 { compatible =3D "cfi-flash"; reg =3D <0 0 0x10000000>; bank-width =3D <4>; device-width =3D <2>; #address-cells =3D <1>; #size-cells =3D <1>; partition@0 { label =3D "dtb"; reg =3D <0x00000000 0x00100000>; read-only; }; partition@300000 { label =3D "kernel"; reg =3D <0x00100000 0x00400000>; read-only; }; partition@400000 { label =3D "fs"; reg =3D <0x00500000 0x00a00000>; }; partition@700000 { label =3D "firmware"; reg =3D <0x00f00000 0x00100000>; read-only; }; }; =20 Kindly provide us suggestions regarding this issue whether any kernel = configuration changes need to be done or if any additional = implementations required in flash memory mapping Regards, Divya =20 ------=_NextPart_000_000A_01CA6385.6E14FD70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,

We are working on MPC8640D based = processor board=20 with,

Boot Loader=20 version : u-boot-2009-06 =

Kernel version &nb= sp; =20 : linux-2.6.30 (Downloaded from kernel.org)

RAM size = =20 : 1=20 GB

Flash memory size =20 : 256 MB

When we are booting the linux kernel, = during mtd=20 subsystem initialization the following error message is=20 obtained

       =20    # vmap allocation for size 268439552 failed: use=20 vmalloc=3D<size> to increase=20 size.
          &nbs= p;#=20 of-flash f0000000.bootflash: Failed to ioremap() flash=20 region
           # = of-flash:=20 probe of f0000000.bootflash failed with error -12

It seems ioremap call during mtd initialization=20 is failing.

The flash partitions are created through the device tree as = follows,

ra= nges =3D=20 <0 0 0xf0000000 0x10000000 >; // 256MB Boot = flash
&nbs= p; = ;

           &n= bsp;   =20 bootflash@0,0=20 {
           &n= bsp;           =20 compatible =3D=20 "cfi-flash";
         &nb= sp;           &nbs= p; =20 reg =3D <0 0=20 0x10000000>;
         =             &= nbsp; =20 bank-width =3D=20 <4>;
          = ;            = =20 device-width =3D=20 <2>;
          = ;            = =20 #address-cells =3D=20 <1>;
          = ;            = =20 #size-cells =3D=20 <1>;
          = ;            = =20 partition@0=20 {
           &n= bsp;           &nb= sp;       =20 label =3D=20 "dtb";
          &nb= sp;           &nbs= p;        =20 reg =3D <0x00000000=20 0x00100000>;
         =             &= nbsp;         =20 read-only;
          = ;            = =20 };
           &= nbsp;           =20 partition@300000=20 {
           &n= bsp;           &nb= sp;       =20 label =3D=20 "kernel";
          =             &= nbsp;        =20 reg =3D <0x00100000=20 0x00400000>;
         =             &= nbsp;         =20 read-only;
          = ;            = =20 };
           &= nbsp;           =20 partition@400000=20 {
           &n= bsp;           &nb= sp;       =20 label =3D=20 "fs";
          &nbs= p;            = ;        =20 reg =3D <0x00500000=20 0x00a00000>;
         =             &= nbsp; =20 };
           &= nbsp;           =20 partition@700000=20 {
           &n= bsp;           &nb= sp;       =20 label =3D=20 "firmware";
         &nbs= p;            = ;         =20 reg =3D <0x00f00000=20 0x00100000>;
         =             &= nbsp;         =20 read-only;
          = ;            = =20 };
           &= nbsp;   =20 };

Kindly provide us suggestions regarding = this issue=20 whether any kernel configuration changes need to be done or if any = additional=20 implementations required in flash memory mapping

Regards,

Divya

------=_NextPart_000_000A_01CA6385.6E14FD70--