[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] [patch] memory management initialisationcleanup
Hi again,
Matthew Rubenstein wrote:
> Well, given that it's in flux (ie. the activity on this maillist :)...
> I'm talking about the version that John Williams is maintaining. Minimal
> API differences will mean minimal work to port other uCLinux apps to
> uC/MB. Those apps, and the community of their developers, are the
> reasons that uC/MB is interesting beyond the community of academic FPGA
> experimenters.
I am certainly aware (and very happy) that people are doing commercial
development on this platform. Changes that go into CVS are intended to
improve the stability, performance or functionality of the microblaze
port. This is the patch flux that you witness on this list. The API
is the system call interface - and compatibility is the #1 priority there.
The research code isn't part of that. I have a library of patches that
I maintain for my experimental stuff - they certainly don't belong in a
production kernel.
Anyway I appreciate your comments - the future direction of this project
is definitely worthy of discussion.
Cheers,
John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/