From: "Michael Stilmant" <michael.stilmant@adtech.be>
To: <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] Porting on TMS320VC5472, eCos or uLinux ?
Date: Wed, 18 Apr 2001 13:31:00 -0000 [thread overview]
Message-ID: <001001c0c846$8951f6d0$10142d03@adtech> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
> -----Message d'origine-----
> De : Jonathan Larmour [ mailto:jlarmour@redhat.com ]
> Envoyé : mercredi 18 avril 2001 21:10
> À : Michael Stilmant
> Cc : ecos-discuss@sourceware.cygnus.com
> Objet : Re: [ECOS] Porting on TMS320VC5472, eCos or uLinux ?
>
>
> If you know where it would be good because we keep hearing things like
> that, and we would like to correct them.
mmmm, sorry but I can't find this now.
finally perhaps I've never read something like this directly.
Reading Redhat web site on ecos, I've never seen 'ecos is not linux' so when
I read doc on eCos I understand it's based somewhere on Linux. And Seeing
it's support ARM7 I understand it's implement uCLinux ....
The possibility to make mistake is big for me (perhaps because I'm note
english born) when I read this:
NetSilicon has partnered with Red Hat to integrate uClinux and Internet
application software with the NET+ARMT family of Ethernet microprocessors to
create a comprehensive solution for embedded Linux development.
So after read RedHat implement ecos and help NetSilicon to integrate uClinux
..... I finally perhaps understand Netsilicon help redhat to integrate
uClinux in ecos. :-)
Sorry , but thanks you for your answer.
I have a better view now.
next reply other threads:[~2001-04-18 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 13:31 Michael Stilmant [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-18 11:02 Michael Stilmant
2001-04-18 12:10 ` Jonathan Larmour
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='001001c0c846$8951f6d0$10142d03@adtech' \
--to=michael.stilmant@adtech.be \
--cc=ecos-discuss@sourceware.cygnus.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).