Thank David for clarifying this! MMU and !MMU support definitely makes everything easy for software and maintainability. I will definitely love to make doc and if possible, make contribution to uClinux through bug fixes or any patches if I encounter during my work.
Regards, Tom --- On Fri, 9/4/09, David McCullough <david_mccullo...@securecomputing.com> wrote: > From: David McCullough <david_mccullo...@securecomputing.com> > Subject: Re: [uClinux-dev] multiple arch with MMU/noMMU > To: "uClinux development list" <uclinux-dev@uclinux.org> > Date: Friday, September 4, 2009, 3:17 AM > > Jivin tom gogh lays it down ... > > Hello everyone, > > I am facing classic dilemma of > which distribution to go for. > > I have powerpc with mmu, MIPS, may be in future some > other processor like ARM and I want to keep my code portable > to multiple arch. > > Which means, if I use MMU/noMMU in > both cases, I need to do less rework or no rework and easy > software maintanability. > > My favorite is uclinux > considering many ports and arch available on it and good > developer base. > > > > Some options I was guessing by doing some little > search on internet: > > > > 1) penguinppc for powerpc but won't be useful for > other arch. > > 2) use kernel.org vanilla with uclinux but not sure if > I can find web resources/guide to do porting easily or any > help in software maintainability. > > 3) Add MMU support in uClinux > > > > What do you folks do in such case? > > > > It will be easier to decide if uClinux supports MMU. > > from link, > > http://www.ucdot.org/article.pl?sid=03/03/24/2353251 > > I think MMU is supported but I am still not sure. > > Can you pls confirm and if there is any web resources > on it? > > uClinux-dist supports anything (MMU and !MMU). > > The kernel in the latest uClinux-dist's is as close to the > kernel.org > releases as possible. > > uClinux-dist even lets you add your own kernel > easily. For example, > take the "penguinppc" kernel, extract it to a directory at > in the dists top > level dir called something like linux-2.6.ppc, and do > a "make config", it > will let you chose the new kernel for building. > > You will need to create a vendors/config/ppc directory, use > the i386/arm > versions as a template, probably just change the > compiler names and you be > close. > > You will need to check how well the uClibc version in the > dist supports ppc > as well, and you can always bring in a new version of > uClibc (much like the > kernel) if needed. > > We run arm, mips, x86, SH4, m68knommu and more out of the > tree on a regular > basis ;-) > > There's not really any "doc" on all this, but just > ask here when you get > stuck and someone will help you out, perhaps then you can > write some doc > for us ;-) ;-) > > Cheers, > Davidm > > -- > David McCullough, david_mccullo...@securecomputing.com, > Ph:+61 734352815 > McAfee - SnapGear http://www.snapgear.com > http://www.uCdot.org > _______________________________________________ > uClinux-dev mailing list > uClinux-dev@uclinux.org > http://mailman.uclinux.org/mailman/listinfo/uclinux-dev > This message was resent by uclinux-dev@uclinux.org > To unsubscribe see: > http://mailman.uclinux.org/mailman/options/uclinux-dev > _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
