public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Michael Stilmant <michael.stilmant@adtech.be>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Porting on TMS320VC5472, eCos or uLinux ?
Date: Wed, 18 Apr 2001 12:10:00 -0000	[thread overview]
Message-ID: <3ADDE69B.EB2F8BB4@redhat.com> (raw)
In-Reply-To: <000701c0c831$afc945d0$10142d03@adtech>

Michael Stilmant wrote:
> 
> Hello
> 
> Following an mail sended last week but not answer, but it's certainly
> because no port yet.
> 
> No problem with this. But actually I have an other fundamental question is
> eCos correct chose for my need or uClinux is a better choice. I read some
> where eCos include uClinux

If you know where it would be good because we keep hearing things like
that, and we would like to correct them.

>, but on RedHat site they keep a distinction
> between them.

eCos is unrelated to Linux. The only link between them is the EL/IX
compatibility levels ( http://sources.redhat.com/elix/ ) to allow *API*
level compatiblity between full-blown Linux and smaller operating systems,
e.g. eCos, uClinux, etc. by subsetting the API.
 
> And finaaly I have this big question : What is the difference, which OS I
> could better use ?
> 
> Is somebody have some answers to this ?

It very much depends on the application you want to use. ucLinux is closer
to the Linux API, although a lot of that depends on the C library used.
eCos is more flexible, and configurable and has the potential to be much
smaller. There's probably more device driver support for ucLinux than is in
eCos. I'm not a uclinux expert though :-).

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

  reply	other threads:[~2001-04-18 12:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 11:02 Michael Stilmant
2001-04-18 12:10 ` Jonathan Larmour [this message]
2001-04-18 13:31 Michael Stilmant

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=3ADDE69B.EB2F8BB4@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=michael.stilmant@adtech.be \
    /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).