public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Richard Rauch" <rrauch@itrgmbh.de>
To: "'Mikhail Matusov'" <matusov@squarepeg.ca>,
	<ecos-discuss@sourceware.org>
Subject: AW: [ECOS] Re: is eCos dying?
Date: Wed, 07 Oct 2015 09:59:00 -0000	[thread overview]
Message-ID: <003601d100e5$9f300450$dd900cf0$@itrgmbh.de> (raw)
In-Reply-To: <53B3B42F298B4F0DAF3729F09E4B839A@SPCI055>

Hi Mikhail,

in which port you are interested? For Xilinx we have made eCos 3.0 port to
Microblaze and to Zynq.



> Von: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-
> owner@ecos.sourceware.org] Im Auftrag von Mikhail Matusov
> Gesendet: Dienstag, 6. Oktober 2015 14:59
> An: Richard Rauch; ecos-discuss@sourceware.org
> Betreff: Re: [ECOS] Re: is eCos dying?
> 
> Hi Richard,
> 
> Could you tell more about your Xilinx port?
> 
> Thanks,
> /Mikhail
> 
> 
> 
> -----Original Message-----
> From: Richard Rauch
> Sent: Tuesday, October 06, 2015 3:51 AM
> To: ecos-discuss@sourceware.org
> Subject: Re: [ECOS] Re: is eCos dying?
> 
> Hi,
> 
> my opinion is quite differently:
> You do not see a lot of activities in the eCos community because of
politics
> and commercial interests.
> 
> My company was very active in eCos projects (specially porting projects
and
> development toolchain) within several years.
> Beside several application projects based on eCos we have made a couple of
> portings to different processor platforms for microcontroller vendors
(Atmel,
> Xilinx) and OEMs.
> 
> We tried to commit all this ports to the community! Specially one of the
> OEMs (Softing AG, Munich) was very active by himself in this commitment
> activity as well.
> But from eCos maintainer side there is no interest to overtake such ports.
> This is just a guess, but in my opinion the reason for this is, that the
> maintainers of public eCos are as well strongly commercial oriented.
> It seems, they will not put any port to official open source repository if
it
> could disturb commercial interests (eCosCentric/eCosPro...).
> 
> I will give just one example when we tried to make a port public:
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001649
> further activities, if you search for in detail:
> http://bugs.ecos.sourceware.org/buglist.cgi?quicksearch=at91sam9G45
> beside this there was email traffic as well with the maintainers, but
finally
> there was no success!
> 
> Additionally I need to say, that you will be thwarted, if you try to offer
> commercial activities as well. If you are not absolutely carefully about
usage
> of eCos name and logo, you will get some letters from eCosCentric's
lawyer!
> 
> In consideration of our experiences I do not wonder, that the audience is
> losing interest in eCos and is searching for alternatives.
> We have already customers, who decided against eCos specially because the
> fact, that there is dramatically decreasing activity in the community!
> 
> Richard
> 
>
----------------------------------------------------------------------------
> --------------------------------
> > Von: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-
> > owner@ecos.sourceware.org] Im Auftrag von Grant Edwards
> > Gesendet: Sonntag, 4. Oktober 2015 17:00
> > An: ecos-discuss@ecos.sourceware.org
> > Betreff: [ECOS] Re: is eCos dying?
> >
> > On 2015-10-04, Stanislav Meduna <stano@meduna.org> wrote:
> > > On 03.10.2015 10:15, John Dallaway wrote:
> > >
> > > Hi Abhishek,
> > >
> > >>> Would it be worth to start learning on eCos or is it dying ?I have
> > >>> seen enough activity in 2007 but now it is minimal this year.
> > >>> Is it getting outdated?
> > >
> > >> eCos is not dying, but I would have to agree that there has been
> > >> less activity on the mailing lists recently.
> > >
> > > Well the last commit in http://hg-pub.ecoscentric.com/ecos/ is 5
> > > months old one-liner, followed by a 12 and 15 month old ones, so
> > > this is not only on mailing lists. I'd say that while it is still a
> > > good OS with clean and easy to use architecture, the open source
> > > version basically died and there are parts hopelessly outdated
> > > (TCP/IP from
> > > ~2000 if I remember correctly etc).
> > >
> > > I cannot comment on eCosPro, but then you are in a price segment
> > > where there are more alternatives to explore.
> > >
> > >>> should i begin to work using eCos or should i look for other
> alternative?
> > >
> > > It depends on what your short and long-term plans are. Definitely
> > > also take a look at FreeRTOS.
> >
> > I also am commenting strictly on the open-source version, not on
> eCosPro...
> >
> > I've been using eCos since the Cygnus days (around 1999 or so).  I've
> > been pretty happy with it, but the open-source version is getting pretty
> stale.
> I'm
> > particularly worried about the ancient FreeBSD network stack -- but it
> still
> > seems to be working OK, knock on wood.
> >
> > I'm also concerned about what's going to happen when my customers
> > starting actually using IPv6 in anger.
> >
> > Getting the two BSD networks stacks integrated into eCos was an
> > impressive feat of engineering. But, a square peg in a round hole is
> > still a square
> peg in a
> > round hole no matter how much you admire the craftsmanship of the
> shims.
> >
> > I've often wished I had a few spare weeks to experiment with LWIP.  I
> > have the impression that it's a better fit for eCos and would be
> > easier to keep current.
> >
> > If I were starting from scratch these days, I'd probably look first at
> something
> > other than eCos. I've never needed the full-up POSIX or uItron
> > adaptation layers, so for my smaller projects I'd probably lean
> > towards something a
> little
> > lighter-weight like uCos-II/III (not free) or XMK (which also seems to
> > be languishing a bit).  FreeRTOS would also be at the top of my list
> > of
> candidates
> > -- even though I find the web-site a bit off-putting.  I'd probably
> > use
> Linux for
> > bigger, more complex projects that are "not quite as real-time" and
> > could benefit from the Unix memory protection and process models.
> >
> > --
> > Grant
> >
> >
> > --
> > Before posting, please read the FAQ:
> > http://ecos.sourceware.org/fom/ecos
> > and search the list archive:
> > http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 
> 
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2015.0.6140 / Virus Database: 4435/10768 - Release Date: 10/06/15
> 
> 
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2015-10-07  9:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06  7:51 Richard Rauch
2015-10-06 12:59 ` Mikhail Matusov
2015-10-07  9:59   ` Richard Rauch [this message]
2015-10-12 23:57 ` Jonathan Larmour
2015-10-13 12:31   ` David Fernandez
2015-10-14  0:57     ` Frank Pagliughi
2015-10-13 17:20   ` Grant Edwards
2015-10-13 19:38 ` Alex Schuilenburg
2015-10-14 23:05 ` Sergei Gavrikov

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='003601d100e5$9f300450$dd900cf0$@itrgmbh.de' \
    --to=rrauch@itrgmbh.de \
    --cc=ecos-discuss@sourceware.org \
    --cc=matusov@squarepeg.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).