This is the mail archive of the
ecos-devel@sources.redhat.com
mailing list for the eCos project.
Re: Is the eCos Open Source development model at risk?
- From: Thomas BINDER <Thomas dot Binder at frequentis dot com>
- To: Jonathan Larmour <jifl at eCosCentric dot com>
- Cc: Michael Checky <Michael_Checky at Thermoking dot com>, ecos-devel at sources dot redhat dot com, rjessich at frequentis dot com, bhaindl at frequentis dot com
- Date: Thu, 03 Jul 2003 09:29:17 +0200
- Subject: Re: Is the eCos Open Source development model at risk?
- Organization: Frequentis
- References: <OFF45F0625.B128C226-ON86256D48.00543788@ingerrand.com> <3EF03487.D7042A6D@frequentis.com> <3F025916.2020505@eCosCentric.com>
Jonathan Larmour wrote:
> <snip>
> >
> > However, the lack of response from the maintainers (the original mail
> > was sent ~ 2 months ago) is an indication that either, (a) nobody seems
> > to be interested, or (b) the maintainers are simply too busy to
> > respond.
> >
> > If (a),
>
> It isn't (a). We're always interested. That's not to say we'll accept your
> patch ;), but you know what I mean. Memory protection is an important
> feature although a generic design can be tricky.
I agree, it is not easy.
As we actually need the memory protection on two platforms (PowerPC, i586) we tried to be as generic as possible. Many internal discussions were necessary to get to the design that was finally implemented for the Power architecture.
As for the patch, we still don't know if one of the maintainers is willing to at least throw a glance at it. As I wrote earlier, we really benefit when the changes get (at least) partly integrated into the main ecos branch. In the long term we are not interested in maintaining our private eCos branch.
Tom
--