n the
kernel config and not integrated into the respective architecture's sources by
default?
Best regards
Arno
> -Ursprüngliche Nachricht-
> Von: ptxdist-boun...@pengutronix.de [mailto:ptxdist-
> boun...@pengutronix.de] Im Auftrag von Arno Euteneuer
> Gesendet: Freitag,
Hi Tim,
> I discovered similar problems on an AM37xx and OMAP35xx with Linux 3.4
> and 3.3.
>
> > Any ideas of what could be wrong will be highly appreciated.
> Did you try to activate all the Kernel Arm-Errata?
> At least for OMAP3503D we figured out that it suffers from more than
> what the Ker
Hi Jürgen,
> [...]
> Is there a correlation between the memory size the kernel gets reported
> and the used memory devices soldered onto the board? ;)
>
> [...]
>
I hope there is a very strong correlation ;-)
We have 256MB DDR2 RAM and 512MB NAND flash and get the following:
root@dlcpro:~ cat
nel and so on. Only the
toolchain was replaced by that from ELDK-5.4
(ftp://ftp.denx.de/pub/eldk/5.4/targets/armv7a/eldk-eglibc-i686-arm-toolchain-gmae-5.4.sh).
I would love to understand what is causing these problems and would highly
appreciate any suggestion.
Arno Euteneuer
--
ptxdist m
> It's a conceptual thing: packets with huge dependencies for system
> libraries like python do a lot of autoprobing (find out if libsomething
> is there, then build the python wrappers for it). So if Python is built
> early, it finds less libraries than when it is built late.
Hmm. But shouldn't t
Hi,
I thought this would be nice to have in the stable release but unfortunately I
don't know how to submit this as a regular ptxdist patch. Maybe my findings can
help nevertheless :
Python on my target did not have the readline functionality in interactive mode
and I found that during crossco
