linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: linux-sh@vger.kernel.org
Subject: Re: SH Core Linux 20110317
Date: Thu, 17 Mar 2011 06:56:36 +0000	[thread overview]
Message-ID: <201103170256.37388.vapier@gentoo.org> (raw)
In-Reply-To: <AANLkTikhuHy8iZO+K6OOARG7fAt90hXbcEFE91dirMOX@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 2344 bytes --]

On Thursday, March 17, 2011 02:40:01 Magnus Damm wrote:
> This is the first public release of SH Core Linux, version 20110317.
> 
> SH Core Linux brings the Linux to the SH core included in sh7372 -
> running in parallel with the ARM core.
> 
> Many modern SoCs contain multiple CPU cores in asymmetric
> multiprocessing configurations. These asymmetric CPU configurations
> often run multiple operating system instances; sometimes multiple
> instances of Linux and sometimes Linux on the main CPU and some
> customized software on the other CPU cores. Asymmetric CPU
> configurations are different from symmetric multiprocessing
> configurations which make use of a single Linux kernel together with
> SMP to support multiple processor cores. To make things even more
> complicated, come SoCs are configured to have some CPU cores operating
> in SMP mode, and others in AMP.

interesting.  we've been banging on similar issues with multiple Blackfins.  
we've got an ICC (inter core communication) driver going atm.  but the 
protocol isnt limited to Blackfins ... we've made sure to design it so that 
any other processor type can work, as well as any operating system.

> This SH Core Linux prototype is written for the sh7372 SoC from
> Renesas. The sh7372 contains one ARM Cortex-A8 and one SH4AL-DSP core.
> This release includes all that is needed to run two instances of
> Linux; one on the ARM core and one on the SH core. The ARM core is the
> main SoC processor which runs a user space program to control the SH
> core. The SH core does not make use of any special hardware except a
> mailbox interface where Virtio serves as a communication link.

so this implementation isnt limited to Linux right ?

i think TI has been doing their own thing too ?  but they dont usually try 
hard to push back to mainline ...

and then there's MCAPI ...

i wonder if there's some way we can centralize/focus efforts on the Linux side 
so each SoC vendor doesnt keep coming up with its own magic sauce to glue 
worlds together.  i really dont see this as being a useful area for everyone 
to "innovate" on their own.  the advantage to being the first one into 
mainline is that everyone else will have to migrate to it :).

perhaps start a list on vger.kernel.org and a wiki on wiki.kernel.org ?
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-03-17  6:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17  6:40 SH Core Linux 20110317 Magnus Damm
2011-03-17  6:56 ` Mike Frysinger [this message]
2011-03-17  7:10 ` Magnus Damm
2011-03-17  7:55 ` Mike Frysinger
2011-03-17 11:21 ` Magnus Damm

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=201103170256.37388.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=linux-sh@vger.kernel.org \
    /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).