public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: microblaze-uclinux@itee.uq.edu.au, LKML <linux-kernel@vger.kernel.org>
Cc: 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, "Steven J. Magnani" <steve@digidescorp.com>,
	stephenn@xilinx.com, Karen Whelan <karen.whelan@petalogix.com>,
	Wendy Liang <wendy.liang@petalogix.com>
Subject: Microblaze - The fist year
Date: Tue, 13 Apr 2010 14:21:01 +0200	[thread overview]
Message-ID: <4BC461AD.6090504@monstr.eu> (raw)

Dear Linux community,

The MicroBlaze Linux Kernel has been in mainline for exactly one year. 
It is time to look back and celebrate this year.

First of all I would like to thank Xilinx and PetaLogix for their 
committed support and everybody who has helped to improve the MicroBlaze 
Linux kernel namely to Andrew Morton, Arnd Bergmann, Edgar E. Iglesias, 
Grant Likely, Ingo Molnar, John Linn, John Williams, Linus Torvalds, Sam 
Ravnborg, Stephen Neuendorffer and Steve Magnani. Goran Bilski and 
Stefan Asserhall (from Xilinx Processing Solutions group) have provided 
valuable assistance too.

Thank you for your work.

MicroBlaze is the first soft-cpu to be merged to the mainline Linux 
kernel and I believe it has proved to be an effective decision to do so. 
With the support of Xilinx and PetaLogix we have dedicated a lot of time 
to improve the MicroBlaze Linux port, adding new features and 
stabilizing the whole kernel. There are still areas for improvement but 
we have set a good direction and we hope with continued support from 
Xilinx and PetaLogix to achieve much more in the future


I would like to ask the whole community if you can point us to new 
features (or weak places) which should be implemented on MicroBlaze. 
Thank you for your continued input.


Let me summarize some MicroBlaze Linux highlights over the last 12 months.

MicroBlaze noMMU - added on April 13, 2009
MicroBlaze QEMU support - April, 2009
MicroBlaze MMU - added on June 12, 2009
First youtube movie with MicroBlaze QEMU by PetaLogix - October 28, 2009
Ftrace support - November 2009
Everyday testing framework - December 2009
and many others

Latest code is available on PetaLogix GIT server.
http://developer.petalogix.com/git/gitweb.cgi (or 
http://git.monstr.eu/git/gitweb.cgi)

Output log from everyday testing
http://www.monstr.eu/wiki/doku.php?id=log:log

I also created a new facebook fan page for MicroBlaze where you can join 
us. http://www.facebook.com/pages/Microblaze-linux/111131818899940

As I announced on Facebook, I decided to open monstr.eu wiki which is 
becoming the microblaze linux wiki.
You can register on 
http://www.monstr.eu/wiki/doku.php?id=user:user&do=register

Thank you.

Best regards,
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

             reply	other threads:[~2010-04-13 12:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13 12:21 Michal Simek [this message]
2010-04-13 13:12 ` Microblaze - The fist year Michael Schnell
2010-04-13 13:27   ` Michal Simek
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=4BC461AD.6090504@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=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