linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: a pre-release of merging loongson patchs to linux-2.6.29.1
Date: Thu, 23 Apr 2009 23:42:12 +0800	[thread overview]
Message-ID: <1240501332.28136.24.camel@falcon> (raw)

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.

the current directory architecture is as following:

$ tree arch/mips/loongson/
arch/mips/loongson/
|-- 2e
|   |-- Makefile
|   |-- irq.c
|   `-- reset.c
|-- 2f
|   |-- 8250.c
|   |-- Makefile
|   |-- clock.c
|   |-- cs5536.h
|   |-- cs5536_pci.h
|   |-- cs5536_vsm.c
|   |-- irq.c
|   |-- mfgpt.c
|   |-- mipsdha.c
|   |-- pcireg.h
|   `-- reset.c
|-- Kconfig
`-- common
    |-- Makefile
    |-- bonito-irq.c
    |-- dbg_io.c
    |-- mem.c
    |-- pci.c
    |-- prom.c
    `-- setup.c

$ tree arch/mips/include/asm/mach-loongson/
arch/mips/include/asm/mach-loongson/
|-- cpu-feature-overrides.h
|-- dma-coherence.h
|-- mc146818rtc.h
|-- mem.h
|-- pci.h
|-- prom.h
`-- war.h

$ ls arch/mips/pci/*loongson*
arch/mips/pci/fixup-loongson2e.c  arch/mips/pci/fixup-loongson2f.c

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

TODO:

   * clean up some of the commits carefully, especially the following
files:
   arch/mips/pci/fixup-loongson2*
   arch/mips/loongson/2f/cs5536* 
   irq.c, reset.c

   * try to merge the left files if possible.
   * update it to the latest mainline kernel and push it in.

best regards,
Wu Zhangjin

-- 
Wu Zhangjin
DSLab, Lanzhou University, China
www.lemote.com, Jiangsu Province, China

             reply	other threads:[~2009-04-23 15:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 15:42 Wu Zhangjin [this message]
2009-04-23 18:12 ` [loongson-dev] a pre-release of merging loongson patchs to linux-2.6.29.1 Erwan Lerale
2009-04-24  1:09   ` [loongson-dev] " Wu Zhangjin
2009-04-24  6:46     ` 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=1240501332.28136.24.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).