public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Evgeny Belyanco <esp1@kbkcc.ru>
To: "C. Adam Lamb" <alamb@ilxlightwave.com>
Cc: ecos-devel@sourceware.org
Subject: Re: Intention to Port eCos to STR9
Date: Sun, 27 Aug 2006 15:51:00 -0000	[thread overview]
Message-ID: <486172047.20060827195111@kbkcc.ru> (raw)
In-Reply-To: <00c001c68fef$94598bd0$63000a0a@corp.ilxlightwave.com>

Thursday, June 15, 2006, 12:17:37 AM, you wrote:

CAL> I’m currently looking into porting eCos to the STR912 processor.  The
CAL> processor is on the bleeding edge (it just came out), so I’m still waiting
CAL> for my eval board.
...

CAL> By the time I am finished with the port (the complete port might take 6
CAL> months or more depending on my employers priorities), I hope to have drivers
CAL> for USB, Ethernet, Flash, SPI, …, and possibly GPIB.  I’m not sure my
CAL> employer will allow me to contribute the GPIB portion, but we’ll see…  I
CAL> intend to contribute everything else back that I can.

Are you plans actual? Is it possible to hope on eCos STR91x port near
Dec'06?

Evgeny Belyanko
**********************************
* E-mail: ea@kbkcc.ru
**********************************

      parent reply	other threads:[~2006-08-27 15:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14 20:17 C. Adam Lamb
2006-06-14 21:09 ` Andrew Lunn
2006-06-14 21:15   ` Re[2]: " Evgeny Belyanco
2006-06-14 21:33     ` Andrew Lunn
2006-06-15  8:54   ` Ilija Koco
2006-06-15 14:55     ` C. Adam Lamb
2006-06-15 15:12       ` Andrew Lunn
2006-06-15 21:56         ` Joakim Langlet
2006-06-15 22:11           ` C. Adam Lamb
2006-08-28 10:29           ` fabio
2008-07-28  6:48             ` Mohd_Arif
2006-06-16  9:44       ` Ilija Koco
2006-06-16 14:47         ` Porting " C. Adam Lamb
2006-06-17  9:47           ` Ilija Koco
2006-06-17  9:59             ` Ilija Koco
2006-08-27 15:51 ` Evgeny Belyanco [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=486172047.20060827195111@kbkcc.ru \
    --to=esp1@kbkcc.ru \
    --cc=alamb@ilxlightwave.com \
    --cc=ecos-devel@sourceware.org \
    /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).