Jamie Lokier ja...@shareable.org wrote:
On uClinux with no MMU, you have to use FLT format (all architectures
support this I think) or FDPIC-ELF (just a few architectures support
this, the advantage is proper shared libraries and loadable modules).
FRV does not support FLAT format, only
Hi all,
During compiling of kernel 2.6, the directory romfs is created into
home/user/uClinux-dist/.
In the directory romfs/dev, all device file names begin with @ .
Does it mean that I'm using a wrong genromfs?
Thanks in advance.
Regards.
___
KJ,
Did you find any solution to this problem? It seems we are hitting
the same problem now. It would be nice if you can share your findings
here.
It appears softfloat library is coming from libgcc. Few routines in
softfloat library, including long long division, would refer to external
On Thu, 5 Feb 2009, Lennart Sorensen wrote:
On Wed, Feb 04, 2009 at 10:00:58PM +0100, Geert Uytterhoeven wrote:
On Wed, 4 Feb 2009, Lennart Sorensen wrote:
Perhaps CCing linux-m...@lists.linux-m68k.org would be a good idea.
Thanks, but this is a uClinux driver.
This is a patch
On Thu, 5 Feb 2009, Lennart Sorensen wrote:
On Thu, Feb 05, 2009 at 04:53:50PM +0100, Geert Uytterhoeven wrote:
linux-m...@lists.linux-m68k.org handles m68k (with MMU) only.
uclinux-dev@uclinux.org handles m68knommu.
Oh. I think I got confused by the fact the same arch/m68k/include is
Robert Wessels wrote:
Just a bit more background on this. As we all know, applications
running in a nommu environment have a static stack size. although the
maximum stack size is determined by this, the stack usage grows and
shrinks. One can imagine that in a certain condition the given
Geert Uytterhoeven wrote:
On Thu, 5 Feb 2009, Lennart Sorensen wrote:
On Thu, Feb 05, 2009 at 04:53:50PM +0100, Geert Uytterhoeven wrote:
linux-m...@lists.linux-m68k.org handles m68k (with MMU) only.
uclinux-dev@uclinux.org handles m68knommu.
Oh. I think I got confused by the fact the same
It turns the fix is rather simple. One just needs to add
-fpic -msingle-pic-base to the TARGET_LIBGCC2_CFLAGS
in the gcc/config/arm/t-linux file.
Cheers.
Jun
On Thu, Feb 05, 2009 at 07:49:21AM -0800, Jun Sun wrote:
KJ,
Did you find any solution to this problem? It seems we are hitting
