public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@cygnus.co.uk>
To: pnorton@ccnusa.com
Cc: ecos-discuss@cygnus.com
Subject: [ECOS] Re: Motorola MBX860 board support, drivers
Date: Sun, 14 Feb 1999 12:09:00 -0000	[thread overview]
Message-ID: <199902141800.SAA11048@sheesh.cygnus.co.uk> (raw)
In-Reply-To: < 14015.7675.916805.979493@grumpy.ccnusa.com > (message from PaulNorton on Mon, 8 Feb 1999 09:41:40 -0800 (PST))

>>>>> "Paul" == Paul Norton <pnorton@ccnusa.com> writes:

    Paul> Has anyone announced any plans to port eCos to the Motorola
    Paul> MBX860 platform? We have several of these boards in our
    Paul> embedded systems lab running VxWorks and would like the
    Paul> option of using eCos instead.

In the last week I have received an offer from somebody who plans to
look into such a port. If you are interested in helping out, let me
know and I can put the two of you in touch.

    Paul> Also, it appears the Motorola 860 port has no serial driver,
    Paul> nor an ethernet driver, and eCos itself has no IP stack as
    Paul> of yet. Are these in development?

eCos device driver support is still very limited, unfortunately. The
Cogent HAL package does contain some basic serial I/O facilities,
mainly for diagnostics and debugging purposes.

There has been one third party port of a TCP/IP stack to eCos. This
was done by EBS Inc, http://www.etcbin.com , and it is not an open
source product. I am sure that ports of other stacks will follow, but
I do not have any more details yet.

Bart Veer // eCos net maintainer

      parent reply	other threads:[~1999-02-14 12:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-08 13:08 [ECOS] " Paul Norton
     [not found] ` < 14015.7675.916805.979493@grumpy.ccnusa.com >
1999-02-14 12:09   ` Bart Veer [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=199902141800.SAA11048@sheesh.cygnus.co.uk \
    --to=bartv@cygnus.co.uk \
    --cc=ecos-discuss@cygnus.com \
    --cc=pnorton@ccnusa.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).