public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Ling Su" <lingsu@palmmicro.com>
To: <ecos-discuss@sources.redhat.com>,
	"Alfredo Knecht" <aknecht@cimsi.cim.ch>
Cc: "Jonathan Larmour" <jlarmour@redhat.com>
Subject: Re: [ECOS] Re: eCos PCI problem and NEC vrc4373 build option.
Date: Wed, 30 Aug 2000 17:42:00 -0000	[thread overview]
Message-ID: <003201c012e4$bf965dc0$1201a8c0@crusoe> (raw)
In-Reply-To: <3.0.5.32.20000831013839.00ace4c0@mailhost>

> Jonathan, do you really mean that redhat is actually maintaining two
> separate threads of gdd/gdb/ecos, and that the one we're sweating on (I
> myself for one) is just some sort of bait?
> And all this in the name of the sacred open source, the plan being to get
> us hooked on the light and buggy weed, then sell us the harder stuff for
> real cash?
> This is an interesting business model indeed, and reminds me of another
one.
> So, if I understand it right, the purpose of the open-source part
including
> this list is to bring us to the point where we say "now that the project
is
> late, we went this far, and invested all this time on that ecos thing,
> there is no alternative left" ...as to plunk down a lot of good money to
> get what was there all the time in the first place, namely the various
> shrink-wrapped products like VxWorks, Psos, QNX, and the like?
>


If opensource operates in this way, I don't think this is the freedom we
advocate.  But this message that the toolchain I use is different from eCos
maintainer make me sad. :(

I remember one thing, last year, I pay $400 to buy a CodeFusion from Cygnus,
actually it is not important for me, I  just want to take a look at what the
opensource IDE developement status. Of course, I think it is ok, but didn't
play with it a lot. Last month, the Source Navigator is open sourced, I
don't know what I pay the $400 for now. :-)

Last time, I talked with NEC, they said they pay a lot to Cygnus for the
toolchain on NEC MIPS, I don't know why I can not get a proper toolchain
works properly. I really follow the instruction on the eCos website
carefully.

Regards,
-Ling

Regards,
-Ling

  parent reply	other threads:[~2000-08-30 17:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-29 11:37 [ECOS] eCos tools binary installation under Cygwin Grant Edwards
2000-08-29 11:57 ` Jonathan Larmour
2000-08-29 12:28   ` Ling Su
2000-08-29 12:43     ` Jonathan Larmour
     [not found]       ` <39AC12F4.9C2F7678@redhat.co.uk>
2000-08-29 17:18         ` [ECOS] eCos PCI problem and NEC vrc4373 build option Ling Su
2000-08-30 15:25           ` [ECOS] " Jonathan Larmour
2000-08-30 15:51             ` Ling Su
2000-08-30 15:58               ` Jonathan Larmour
2000-08-30 16:38                 ` Alfredo Knecht
2000-08-30 17:20                   ` Jonathan Larmour
2000-08-30 18:10                     ` Alfredo Knecht
2000-08-30 18:22                       ` Jonathan Larmour
2000-08-30 17:42                   ` Ling Su [this message]
2000-08-30 18:02                     ` Jonathan Larmour
2000-08-30 18:28                       ` Ling Su
2000-08-30 18:57                         ` Jonathan Larmour
2000-08-31  3:34                           ` Nick Garnett
2000-08-31 10:57                           ` Ling Su

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='003201c012e4$bf965dc0$1201a8c0@crusoe' \
    --to=lingsu@palmmicro.com \
    --cc=aknecht@cimsi.cim.ch \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@redhat.com \
    /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).