From: "wangwei" <wangw@start.com.cn>
To: "Joerg Rapka" <joerg.rapka@duagon.com>
Cc: <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] 68302 (or 680x0) port ?
Date: Wed, 25 Jul 2001 17:58:00 -0000 [thread overview]
Message-ID: <007001c1156c$6c7bf9c0$592da8c0@start.com.cn> (raw)
In-Reply-To: <NDBBKEBGMLIMMPMJHHFDEEGGCLAA.joerg.rapka@duagon.com>
Hi,Joerg
As you said , your ecos ported to m68 is ok.
Now I want to do the same thing . So I want to know if you prepare to
contribute this porting to redhat or not .
----- Original Message -----
From: "Joerg Rapka" <joerg.rapka@duagon.com>
To: <leenipper@acm.org>
Cc: <ecos-discuss@sourceware.cygnus.com>
Sent: Monday, January 29, 2001 8:35 PM
Subject: AW: [ECOS] 68302 (or 680x0) port ?
> Hi
>
> I have made a port of eCos to my M68331 based hardware.
> The port is still under development and is not yet contributed
> to Red Hat.
>
> Further interests? - just contact me.
>
> Best regards
>
> Joerg Rapka
>
>
> -----Ursprungliche Nachricht-----
> Von: ecos-discuss-owner@sources.redhat.com
> [ mailto:ecos-discuss-owner@sources.redhat.com]Im Auftrag von Lee Nipper
> Gesendet: Samstag, 27. Januar 2001 05:25
> An: ecos-discuss@sourceware.cygnus.com
> Betreff: [ECOS] 68302 (or 680x0) port ?
>
>
> Does anyone know of a 68302 (or even 680x0) port
> of eCos ?
>
> thanks,
> ln
next prev parent reply other threads:[~2001-07-25 17:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 20:25 Lee Nipper
2001-01-29 4:36 ` AW: " Joerg Rapka
2001-01-31 6:44 ` [ECOS] What happened to feof & ftell? Peter Graf
2001-01-31 9:21 ` Jonathan Larmour
2001-01-31 22:57 ` Martin van Veen
2001-01-31 23:17 ` Jonathan Larmour
2001-02-01 0:48 ` Peter Graf
2001-07-25 17:58 ` wangwei [this message]
2001-08-22 0:20 [ECOS] 68302 (or 680x0) port ? Koh
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='007001c1156c$6c7bf9c0$592da8c0@start.com.cn' \
--to=wangw@start.com.cn \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=joerg.rapka@duagon.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).