From: "Roland Schwarz" <roland.schwarz@telecom.at>
To: <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] probably a FAQ, but: how many x86 ports are in motion out there?
Date: Thu, 07 Oct 1999 09:29:00 -0000 [thread overview]
Message-ID: <000b01bf10e1$46f74740$e200a8c0@fledermaus.zoo.at> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
Hi,
the x86, pc104 platform still is not on the list of supported
targets. As the toolchain is hosted on x86 I suppose it will be
straightforward to target to this platform.
Is this true?
Thank you,
Roland
-----Original Message-----
From: Bart Veer <bartv@cygnus.co.uk>
To: utz@serv.net <utz@serv.net>
Cc: ecos-discuss@cygnus.com <ecos-discuss@cygnus.com>
Date: Dienstag, 02. März 1999 23:32
Subject: Re: [ECOS] probably a FAQ, but: how many x86 ports are in motion
out there?
>>>>>> "John" == The Utz Family <utz@serv.net> writes:
>
> John> whats the status on x86? x86/pc103/4? amd-sc400?
>
>Currently there is no port of eCos to embedded x86 platforms, but such
>a port by Cygnus is now under consideration. This would target
>processors from the 386 upwards - support for earlier processors would
>be difficult because of compiler issues.
>
>Please see the section on porting in the sourceware FAQ for more
>details, http://sourceware.cygnus.com/ecos/faq.html
>
>Bart Veer // eCos net maintainer
>
next reply other threads:[~1999-10-07 9:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-07 9:29 Roland Schwarz [this message]
1999-10-07 9:53 ` [ECOS] probably a FAQ, but: how many x86 ports are in motionout there? Patrick O'Grady
1999-10-08 1:45 ` [ECOS] probably a FAQ, but: how many x86 ports are in motion out there? Jesper Skov
1999-10-11 13:03 ` [ECOS] hal/i386/pc Patrick O'Grady
1999-10-12 1:29 ` [ECOS] hal/i386/pc Jesper Skov
-- strict thread matches above, loose matches on Subject: below --
1999-03-03 14:55 [ECOS] probably a FAQ, but: how many x86 ports are in motion out there? alex
1999-02-25 13:49 The Utz Family
1999-03-02 13:56 ` Bart Veer
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='000b01bf10e1$46f74740$e200a8c0@fledermaus.zoo.at' \
--to=roland.schwarz@telecom.at \
--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).