mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Will Newton <will.newton@gmail.com>
To: liqin@sunnorth.com.cn
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] score - New architecure port to SunplusCT S+CORE  processor
Date: Tue, 24 Mar 2009 11:00:05 +0000	[thread overview]
Message-ID: <87a5b0800903240400n43c1f0eak15875d8d29a60525@mail.gmail.com> (raw)
In-Reply-To: <OF4CC8EBC2.BDA9C1A9-ON48257583.0014767E-48257583.0014EE2B@sunnorth.com.cn>

On Tue, Mar 24, 2009 at 3:46 AM,  <liqin@sunnorth.com.cn> wrote:
> Hello, Linus and folks,
>
> We have ported Linux to the S+CORE processor, which is a 32-bit RISC
> embedded
> microprocessor of Sunplus Core Technology.
>
> SPG29X, SPG300(score core) processor have been used in game products.
> and score toolchain have commit to gnu in 2006. We have a team to maintain
> score code for linux kernel.
>
> We would like to release a patch for kernel 2.6.29-rc8.
> This patch include score header files, arch files and serial driver for
> spct6600(score core) platform.
>
> For the other driver patches, I'll send them one by one in
> small size latter. Thanks!
>
> Would you merge them to the stock kernel?
>
> Patch information is slightly bigger, so I placed it on our SunplusCT web
> site.
> http://www.sunplusct.com/images/linux-score-patch/linux-score-20090324.patch
>
> Signed off by: Chen Liqin <liqin.chen@sunplusct.com,
> liqin@sunnorth.com.cn>

To allow people to more easily review your patches it is recommended
to spit them up into smaller pieces and submit them to the mailing
list.

Your port looks relatively clean but it looks like it is borrowing
heavily from the mips port and you may have a few leftovers from that
e.g.:

- mentions of o32 (unless S+CORE has an o32 ABI?)
- compatibility syscalls, sys_ipc, old-style signal handling. Are
these really needed for a new arch?
- does SCORE+ have ll/sc instructions or is that another leftover from MIPS?
- does your port support SMP?

  reply	other threads:[~2009-03-24 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24  3:46 liqin
2009-03-24 11:00 ` Will Newton [this message]
2009-03-25  4:11 liqin.chen
2009-03-25 12:01 ` Will Newton

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=87a5b0800903240400n43c1f0eak15875d8d29a60525@mail.gmail.com \
    --to=will.newton@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liqin@sunnorth.com.cn \
    /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

all inboxes | Powered by JetHome®