From: Jesper Skov <jskov@redhat.com>
To: Mike Friedrichs <mike_fr1@lcc.net>
Cc: eCos Discuss <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] i386 questions
Date: Sat, 03 Jun 2000 00:19:00 -0000 [thread overview]
Message-ID: <otsnuv5izu.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <39386B6E.6B9354A1@lcc.net>
>>>>> "Mike" == Mike Friedrichs <mike_fr1@lcc.net> writes:
Mike> anyone, i'm confused about ecos and porting to i386. on the ecos
Mike> home page they make reference to i386 as a supported target, but
Mike> upon viewing posts, it appears that people are building the port
Mike> to i386. which is it.
Both. The synthetic support has been there for a while, but
(relatively) recently Patrick O'Grady contributed a port for x86 PCs.
Mike> i have found the words 'synthetic x86 linux' and synthetic i386'
Mike> for targets; what do these phrases mean.
That you run (eCos) applications on the host platform (i.e., the
synthetic platform HAL provides bindings to the host OS). Only Linux
has a synthetic target support at the moment.
Mike> assuming ecos has not been ported to i386, why has ecos been
Mike> ported to the 'Intel StrongArm family' and not the 'i386
Mike> family'.
Basically because the StrongARM work was funded, whereas nobody has
been interested in funding x86 porting. Presumably because the x86 is
not what you would call a (traditional, low-powered) embedded CPU.
Jesper
next prev parent reply other threads:[~2000-06-03 0:19 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 [this message]
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
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=otsnuv5izu.fsf@thinktwice.zoftcorp.dk \
--to=jskov@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=mike_fr1@lcc.net \
/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).