All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Patard <apatard@mandriva.com>
To: wuzhangjin@gmail.com
Cc: linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>,
	loongson-dev@googlegroups.com, zhangfx@lemote.com,
	yanh@lemote.com, Philippe Vachon <philippe@cowpig.ca>,
	Erwan Lerale <erwan@thiscow.com>, Zhang Le <r0bertz@gentoo.org>
Subject: Re: [GIT repo] loongson: Merge and Clean up fuloong(2e), fuloong(2f) and yeeloong(2f) support
Date: Fri, 15 May 2009 10:25:22 +0200	[thread overview]
Message-ID: <m3iqk2rcwd.fsf@anduin.mandriva.com> (raw)
In-Reply-To: <1242357553.30339.66.camel@falcon> (Wu Zhangjin's message of "Fri, 15 May 2009 11:19:13 +0800")

Wu Zhangjin <wuzhangjin@gmail.com> writes:

Hi,

> Dear all,
>
> I have cleaned up the source code of loongson-based machines support and
> updated it to linux-2.6.29.3, the result is put to the following git
> repository:
>
>    git://dev.lemote.com/rt4ls.git linux-2.6.29-stable-loongson-to-ralf
>
> this job is based on the to-mips branch of Yanhua's
> git://dev.lemote.com/linux_loongson.git and the lm2e-fixes branch of
> Philippe's git://git.linux-cisco.org/linux-mips.git. thanks goes to
> them.

I'd like to look at your patches but getting a git url prevents me to do
this because replying/commenting is not possible. Can you please send
patches to the list instead ?

>
> I have tested it with gcc 4.3 on fuloong(2e), fuloong(2f), yeeloong(2f),
> both 32bit and 64bit kernel works well, if you want to try it with gcc
> 4.4, please use the patch from attachment.

I have some questions/comments :

- Why this patch is not merged in your patchset ?
- even if it should not affect the kernel, compiling with
  -march=loongson2f even for 2e (you're matching on loongson2 so 2e and
  2f) looks weird.
- you're using the -mfix-ls2f-kernel binutils flag but afaik upstream
  binutils doesn't know it. I really don't know how such a thing should
  be handled but it seems strange to use this flag before binutils has
  been patched for it. (the previous comment about -march=loongson2f
  applies here too)

>
> * the current source code architecture

fwiw, I like this new organisation. thanks.

>
> $ tree arch/mips/loongson/
> arch/mips/loongson/
> |-- Kconfig
> |-- Makefile
> |-- common
> |   |-- Makefile
> |   |-- bonito-irq.c
> |   |-- clock.c
> |   |-- cmdline.c
> |   |-- cs5536_vsm.c
> |   |-- early_printk.c
> |   |-- init.c
> |   |-- irq.c
> |   |-- mem.c
> |   |-- mfgpt.c
> |   |-- mipsdha.c

hm.. I thought that the mipsdha stuff was refused when submitting 2e
support. Can someone check ?

Arnaud

  reply	other threads:[~2009-05-15  8:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15  3:19 [GIT repo] loongson: Merge and Clean up fuloong(2e), fuloong(2f) and yeeloong(2f) support Wu Zhangjin
2009-05-15  8:25 ` Arnaud Patard [this message]
2009-05-15 10:38   ` Wu Zhangjin
2009-05-15 17:09     ` Zhang Le
2009-05-15 18:00       ` Wu Zhangjin

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=m3iqk2rcwd.fsf@anduin.mandriva.com \
    --to=apatard@mandriva.com \
    --cc=erwan@thiscow.com \
    --cc=linux-mips@linux-mips.org \
    --cc=loongson-dev@googlegroups.com \
    --cc=philippe@cowpig.ca \
    --cc=r0bertz@gentoo.org \
    --cc=ralf@linux-mips.org \
    --cc=wuzhangjin@gmail.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.