We're looking at putting a microblaze toolchain on git.xilinx.com, which will be slightly easier than grabbing all of petalinux, if people just want to compile test it.
At the moment, we would very much like to push the microblaze architecture code to the gcc mainline. I believe the main barrier is that we don't have someone with the bandwidth to interact with the gcc community at the moment, although hiring someone to work on it may be in the works. (Anyone interested?) Steve > -----Original Message----- > From: Adrian Bunk [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 26, 2008 12:43 PM > To: Michal Simek > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Stephen Neuendorffer; > John Linn; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED]; [EMAIL PROTECTED]; linuxppc-dev@ozlabs.org; > [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Microblaze init port v4 > > On Thu, Jun 26, 2008 at 08:50:37PM +0200, Michal Simek wrote: > > Hi Adrian, > > > > > On Thu, Jun 26, 2008 at 02:29:29PM +0200, [EMAIL PROTECTED] wrote: > > >> Hi everybody, > > >> > > >> current linux version is 2.6.26-rc8 and I think this is the right time > > >> to send latest patches againts rc8 for Microblaze CPU. > > >> ... > > > > > > Thanks for your work on getting the architecture included. > > > > > > I have two questions: > > > > > > Where can I find a toolchain for compiling a Microblaze kernel? > > I personally use petalogix toolchain from www.petalogix.com. > > > > > What is the status of Microblaze support in upstream binutils and gcc? > > > > I don't have any information about. We will discuss with John Williams and guys > > from Xilinx > > what we can do for it. > > Thanks! > > > M > > cu > Adrian > > -- > > "Is there not promise of rain?" Ling Tan asked suddenly out > of the darkness. There had been need of rain for many days. > "Only a promise," Lao Er said. > Pearl S. Buck - Dragon Seed > This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
