public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mike Friedrichs <mike_fr1@lcc.net>
To: Gary Thomas <gthomas@redhat.com>
Cc: eCos Discuss <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] i386 questions
Date: Sun, 04 Jun 2000 10:11:00 -0000	[thread overview]
Message-ID: <393A8D16.EDF27F8F@lcc.net> (raw)
In-Reply-To: <XFMail.000603135750.gthomas@redhat.com>

Gary Thomas wrote:
> 
> On 03-Jun-00 Mike Friedrichs wrote:
> > anyone,
> >
> > i'm confused about ecos and porting to i386. on the ecos home page they
> > make reference to i386 as a supported target, but upon viewing posts, it
> > appears that people are building the port to i386. which is it.
> >
> > i have found the words 'synthetic x86 linux' and synthetic i386' for
> > targets; what do these phrases mean.
> >
> 
> Have you checked the latest sources from CVS?  This is the best way to
> keep up with what's available.
> 
> Actually, we have supported ports for both.
>   * Synthetic x86 Linux - A pseudo target where eCos applications run as
>     Linux programs.
>   * x86 "PC" - a target for standard "PC" boxes, running stand alone where
>     the eCos application is the only thing running on the platform.
> 
> > assuming ecos has not been ported to i386, why has ecos been ported to
> > the 'Intel StrongArm family' and not the 'i386 family'.
> 
> Don't forget what eCos stands for: "Embedded Configurable Operating System".
> As such, our primary interest is in commercially used, embedded platforms.
> The ARM/StrongARM family of processors is certainly one of the most popular
> architectures for such devices and becoming more so every day.  While the
> i386 architecture is also very poplular, it is not normally deployed into
> the very deeply embedded systems we concentrate on (think cell phones, etc).
> 
> If you're really interested in the i386 support and find that what's out there
> already isn't sufficient, get the sources and add to them.  This is the heart
> of Open Source projects - everyone has the ability to do whatever they want
> and/or need.  If you find you need help or want even more, just ask us, that's
> part of how we "drive" the development.  Requests can be sent to:
>   ecos-info@cygnus.com

the reason i'm looking at i386 is because we have already built in-house
embedded pc's developed around the i386 with a/d's, serial, and network
support. we built our own in-house real time os using dos and a pharlap
dos-extender. but if i can adapt eCos with the posix syntax to our
present architecture i would be thrilled. the one thing i would like to
add is a shell; like tcsh or similar. then you could add a keyboard and
ascii monitor and be able to run as a network client in the console
mode. 

i've been searching around for cvs, but couldn't find any development
addressing the i386 archititure. could some one point in the right
direction.

i noticed that there is a recent release for using win/nt/98 as a host.
is there any advantage to this approach versus using linux redhat 6.2.

thanks again

      reply	other threads:[~2000-06-04 10:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-02 19:23 Mike Friedrichs
2000-06-03  0:19 ` Jesper Skov
2000-06-03  9:56   ` Mike Friedrichs
2000-06-03 10:23     ` Vishal Kulshrestha
2000-06-03 13:34     ` Gary Thomas
2000-06-06  8:08   ` Liviu Ionescu
2000-06-06  8:17     ` Jesper Skov
2000-06-06  8:27       ` Patrick O'Grady
2000-06-06  8:38       ` Liviu Ionescu
2000-06-06  9:35         ` Mike Friedrichs
2000-06-07  9:49           ` Liviu Ionescu
2000-06-07 18:17             ` [ECOS] IDE/ATAPI/FS info? Brett Hackleman
2000-06-03 12:57 ` [ECOS] i386 questions Gary Thomas
2000-06-04 10:11   ` Mike Friedrichs [this message]

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=393A8D16.EDF27F8F@lcc.net \
    --to=mike_fr1@lcc.net \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=gthomas@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).