From: Michal Simek <monstr@monstr.eu>
To: Michael Schnell <mschnell@lumino.de>
Cc: microblaze-uclinux@itee.uq.edu.au,
LKML <linux-kernel@vger.kernel.org>,
John Williams <john.williams@petalogix.com>,
John Linn <John.Linn@xilinx.com>,
Stefan Asserhall <stefan.asserhall@xilinx.com>,
Goran Bilski <goran@xilinx.com>,
"Steven J. Magnani" <steve@digidescorp.com>,
Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
akpm@linux-foundation.org, Ingo Molnar <mingo@elte.hu>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Grant Likely <grant.likely@secretlab.ca>,
sam@ravnborg.org, stephenn@xilinx.com,
Karen Whelan <karen.whelan@petalogix.com>,
Wendy Liang <wendy.liang@petalogix.com>
Subject: Re: Microblaze - The fist year
Date: Tue, 13 Apr 2010 15:27:27 +0200 [thread overview]
Message-ID: <4BC4713F.6030702@monstr.eu> (raw)
In-Reply-To: <4BC46DC6.5050309@lumino.de>
Michael Schnell wrote:
> Does Microblaze MMU Linux support Futex ?
yes, futex is there. You can check it in
arch/microblaze/include/asm/futex.h
> Does Microblaze MMU Linux support SMP ?
It is possible to connect several MicroBlazes but the problem is missing
cache coherency modul. I hope that Xilinx will release any version which
will support it.
We haven't done any significant work to support it but it is expected
solution which will happen.
Thanks for input,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2010-04-13 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 12:21 Microblaze - The fist year Michal Simek
2010-04-13 13:12 ` Michael Schnell
2010-04-13 13:27 ` Michal Simek [this message]
2010-04-14 7:53 ` Michael Schnell
2010-05-09 16:49 ` Bill Davidsen
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=4BC4713F.6030702@monstr.eu \
--to=monstr@monstr.eu \
--cc=John.Linn@xilinx.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=edgar.iglesias@gmail.com \
--cc=goran@xilinx.com \
--cc=grant.likely@secretlab.ca \
--cc=john.williams@petalogix.com \
--cc=karen.whelan@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=mingo@elte.hu \
--cc=mschnell@lumino.de \
--cc=sam@ravnborg.org \
--cc=stefan.asserhall@xilinx.com \
--cc=stephenn@xilinx.com \
--cc=steve@digidescorp.com \
--cc=torvalds@linux-foundation.org \
--cc=wendy.liang@petalogix.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