[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian on Fuloong

Might be you have to be aware that you are using 2E box. Recent work are mainly done on 2F boxes,although 2E should be ok too but there might be some config difference.

Andreas Barth wrote:
* Daniel Clark (dclark@pobox.com) [100207 17:04]:
On Sun, Feb 7, 2010 at 10:17 AM, Andreas Barth <aba@not.so.argh.org> wrote:
I'm now trying with an heavily patched with the full set of
options (only the -Wa-part didn't help to run it stable). If that
doesn't work either, I have no idea myself anymore.
You need to use Lemote's git repo for 2.6.32
-http://dev.lemote.com/code/rt4ls - I believe as of 2.6.33 all the
(important at least) changes have made it into mainline.

I have tried it with an 2.6.33-rc7-kernel with these configs:

This kernel ends at the moment where it displays the registers at the
vga screen. I boot it with:

ifaddr rtl0 ...
load tftp://... no_auto_cmd
g console=tty root=/dev/hda1 no_auto_cmd

(I think at least in the first kernel I missed something obvious,
namely the console. Could be the same issue with the second.)

The machine works with the heavily patched 2.6.31 kernel (which has a
few patches from lemote). However, with that kernel (built with both
new binutils options, used as -Wa,.. and -Wl,...) the machine stops
at always the same step while building binutils in a standard debian
unstable chroot:
make[3]: Entering directory `/build/buildd-binutils_2.20-5~mipselaba.1-mipsel-1AL2Gb/binutils-2.20/builddir-single/libiberty'
if [ x"-fPIC" != x ] && [ ! -d pic ]; then \
          mkdir pic; \
        else true; fi
touch stamp-picdir
if [ x"-fPIC" != x ]; then \
          gcc -c -DHAVE_CONFIG_H -g -O2  -I. -I../../libiberty/../include  -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic  -fPIC ../../libiberty/regex.c -o pic/regex.o; \
        else true; fi

(please see http://buildd.debian.org/ for a full "normal" build log -
this is basically the first time gcc is called for real and not only
to create config.*)

For building any of the kernels, I used -mfix-loongson2f-nop and
-mfix-loongson2f-jump, built with binutils patched with
http://sourceware.org/ml/binutils/2009-11/msg00387.html .

Do I need to use -mfix-ls2f-kernel from
as well? I understood it as that patch is already included in the
newer binutils patch.

BTW, If I have to choose, I'd prefer in getting some variant of 2.6.33
running on the machine - the nearer to the linus tree the better. :)


Reply to: