From: "Kevin D. Kissell" <kevink@paralogos.com>
To: "Ardelean, Andrei" <Andrei.Ardelean@idt.com>
Cc: linux-mips@linux-mips.org
Subject: Re: What is CONFIG_MIPS_MT_SMTC configuration and when is this recommended to be used?
Date: Wed, 15 Sep 2010 13:56:09 -0700 [thread overview]
Message-ID: <4C9132E9.6060807@paralogos.com> (raw)
In-Reply-To: <AEA634773855ED4CAD999FBB1A66D076010CFA3B@CORPEXCH1.na.ads.idt.com>
SMTC is a kernel for the 34K (and, just maybe, with some mods, 1004K)
that turns TC microthreads into virtual SMP CPUs. See
http://tree.celinuxforum.org/CelfPubWiki/ELC2006Presentations?action=AttachFile&do=view&target=CELF_SMTC_April_2006_v0.3.pdf
/K.
On 09/15/10 12:46, Ardelean, Andrei wrote:
> Hi,
>
> I use Linux on MALTA board. My final goal is to port Linux on new board
> based on MIPS. What is CONFIG_MIPS_MT_SMTC configuration and when is
> this recommended to be used?
>
> Thanks,
> Andrei
>
>
>
next prev parent reply other threads:[~2010-09-15 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 19:46 What is CONFIG_MIPS_MT_SMTC configuration and when is this recommended to be used? Ardelean, Andrei
2010-09-15 19:46 ` Ardelean, Andrei
2010-09-15 20:56 ` Kevin D. Kissell [this message]
2010-09-16 10:34 ` Ralf Baechle
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=4C9132E9.6060807@paralogos.com \
--to=kevink@paralogos.com \
--cc=Andrei.Ardelean@idt.com \
--cc=linux-mips@linux-mips.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