On 09:18 Thu 07 Mar , Sascha Hauer wrote:
> Hi Jürgen,
>
> On Tue, Mar 05, 2013 at 02:30:22PM +0100, Jürgen wrote:
> > On 11.02.2013 Sascha Hauer wrote:
> > >On Fri, Feb 08, 2013 at 04:22:09PM +0100, Jan Weitzel wrote:
> > >>Hi,
> > >>with the release v2013.02.0 the MLO gets so bit, that it ea
Hi Jürgen,
On Tue, Mar 05, 2013 at 02:30:22PM +0100, Jürgen wrote:
> On 11.02.2013 Sascha Hauer wrote:
> >On Fri, Feb 08, 2013 at 04:22:09PM +0100, Jan Weitzel wrote:
> >>Hi,
> >>with the release v2013.02.0 the MLO gets so bit, that it eats the boot
> >>information in the SRAM.
> >>
> >>nm --size-
On 11.02.2013 Sascha Hauer wrote:
On Fri, Feb 08, 2013 at 04:22:09PM +0100, Jan Weitzel wrote:
Hi,
with the release v2013.02.0 the MLO gets so bit, that it eats the boot
information in the SRAM.
nm --size-sort
...
0630 D nand_flash_ids
08c0 t mci_probe
0c00 b gpio_desc
1400 b f
On Fri, Feb 08, 2013 at 04:22:09PM +0100, Jan Weitzel wrote:
> Hi,
> with the release v2013.02.0 the MLO gets so bit, that it eats the boot
> information in the SRAM.
>
> nm --size-sort
>
> ...
> 0630 D nand_flash_ids
> 08c0 t mci_probe
> 0c00 b gpio_desc
> 1400 b files
>
> If I
Hi,
with the release v2013.02.0 the MLO gets so bit, that it eats the boot
information in the SRAM.
nm --size-sort
...
0630 D nand_flash_ids
08c0 t mci_probe
0c00 b gpio_desc
1400 b files
If I remove GPIOLIB from MLO it work again. Maybe setting MAX_FILES
down or find a dynamic