From: Wu Zhangjin <wuzhangjin@gmail.com>
To: loongson-dev@googlegroups.com
Cc: yanh@lemote.com, zhangfx@lemote.com, penglj@lemote.com,
huhb@lemote.com, taohl@lemote.com, linux-mips@linux-mips.org,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [loongson-dev] Re: a pre-release of merging loongson patchs to linux-2.6.29.1
Date: Fri, 24 Apr 2009 09:09:03 +0800 [thread overview]
Message-ID: <1240535343.25824.14.camel@falcon> (raw)
In-Reply-To: <49F0AFA3.6080408@thiscow.com>
On Thu, 2009-04-23 at 20:12 +0200, Erwan Lerale wrote:
> Wu Zhangjin wrote:
> > hi, all
> >
> > these days, I am working on merging loongson patchs to linux-2.6.29.1,
> > the fuloong(2f) & yeeloong source code have been completely merged to an
> > 2f directory, most of the 2e & 2f source code have been merged except
> > the irq.c & reset.c, fixup-loongson2e.c & fixup-loongson2f.c.
> >
>
> Cool ! :)
>
> [...]
>
> > a current version is released to git://dev.lemote.com/rt4ls.git,
> > (for avoid creating another git repository for it, i just use my
> > RT_PREEMPT git tree instead, so, it may be very big :-( )
> >
> > $ git clone git://dev.lemote.com/rt4ls.git
> > $ git checkout linux-2.6.29-stable-loongson --track
> > origin/linux-2.6.29-stable-loongson
> >
>
> You meant :
>
> git checkout -b linux-2.6.29-stable-loongson --track
> origin/linux-2.6.29-stable-loongson
>
> don't you ?
>
Yes, thanks for correcting this error, forget to add the -b option.
>
> I can not compile it :
>
> CC arch/mips/loongson/common/bonito-irq.o
> CC arch/mips/loongson/common/mem.o
> CC arch/mips/loongson/common/dbg_io.o
> cc1: warnings being treated as errors
> arch/mips/loongson/common/dbg_io.c: In function �prom_printf
> arch/mips/loongson/common/dbg_io.c:178: error: the frame size of 1040
> bytes is larger than 1024 bytes
> make[1]: *** [arch/mips/loongson/common/dbg_io.o] Error 1
> make: *** [arch/mips/loongson/common] Error 2
>
which gcc compiler do you use? gcc 4.4? i just try to compile it in gcc
4.4, get the same error. but i only test it in gcc 4.3(cross-compiler)
before, only a few "trivial" warnings.
a new branch for gcc 4.4 will be created as quickly as i can.
> I have used the config file from here :
> arch/mips/configs/yeeloong2f_defconfig
>
> Cheers and thanks for your work !
>
really thanks for your encouragement, welcome to take part in, lots of
source code lines need to be cleaned up.
> Erwan
>
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups "loongson-dev" group.
> To post to this group, send email to loongson-dev@googlegroups.com
> To unsubscribe from this group, send email to loongson-dev+unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/loongson-dev?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
next prev parent reply other threads:[~2009-04-24 1:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 15:42 a pre-release of merging loongson patchs to linux-2.6.29.1 Wu Zhangjin
2009-04-23 18:12 ` [loongson-dev] " Erwan Lerale
2009-04-24 1:09 ` Wu Zhangjin [this message]
2009-04-24 6:46 ` [loongson-dev] " Erwan Lerale
2009-04-24 7:03 ` Wu Zhangjin
2009-04-24 19:49 ` Erwan Lerale
2009-04-25 6:17 ` Wu Zhangjin
2009-04-26 17:20 ` Erwan Lerale
2009-05-19 12:14 ` Erwan Lerale
2009-05-19 14:36 ` 胡洪兵
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1240535343.25824.14.camel@falcon \
--to=wuzhangjin@gmail.com \
--cc=huhb@lemote.com \
--cc=linux-mips@linux-mips.org \
--cc=loongson-dev@googlegroups.com \
--cc=penglj@lemote.com \
--cc=ralf@linux-mips.org \
--cc=taohl@lemote.com \
--cc=yanh@lemote.com \
--cc=zhangfx@lemote.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.