From: Ralf Baechle <ralf@linux-mips.org>
To: Mohamed Bamakhrama <bamakhrama@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Porting SMP kernel into a dual-core MIPS architecture
Date: Wed, 11 Jul 2007 16:42:50 +0100 [thread overview]
Message-ID: <20070711154250.GA25553@linux-mips.org> (raw)
In-Reply-To: <40378e40707110807n2cd32c68tdb8604c5d39e72a6@mail.gmail.com>
On Wed, Jul 11, 2007 at 05:07:19PM +0200, Mohamed Bamakhrama wrote:
> Is there any guidelines/tutorial for porting the SMP kernel into a
> dual core new architecture based on MIPS32?
> AFAIK, in the x86 world we have Intel MPS 1.4 standard. I wonder if
> there exists a similar thing for MIPS. In other words, what are the
> minimum requirements needed to port the SMP kernel into such an
> architecture?
The MIPS Architecture definition defines the behaviour of the processor
in great detail. It doesn't define the system level or firmware. I
suggest you download the architecture manual from www.mips.com and if
that leaves any questions open, post again.
Ralf
prev parent reply other threads:[~2007-07-11 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 15:07 Porting SMP kernel into a dual-core MIPS architecture Mohamed Bamakhrama
2007-07-11 15:42 ` Ralf Baechle [this message]
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=20070711154250.GA25553@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=bamakhrama@gmail.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