public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Ian Campbell <icampbell@arcom.com>
To: bardozs@esiee.fr
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: porting on Arcom Viper board
Date: Mon, 31 Jan 2005 10:39:00 -0000	[thread overview]
Message-ID: <1107167930.14895.38.camel@icampbell-debian> (raw)

Hi Sébastien,

I seem to have become unsubscribed from ecos-devel so I am quoting from
the web archive.

> I'm student and I'm working on project to control some stuffs.
> In this aim, I'm looking for a port for the Arcom Viper board based on
> Intel Xscale PXA255. 
> Is there anyone who began or finished the porting?
> I'm new in this field, so I would like to know how it works, and
> probably how to do this port. Could you help me please?

If you have purchased a VIPER development kit then you should have the
source to our ecos port in /host/RedBoot/ on the CD. 

Note however that Arcom only develop/support RedBoot on the VIPER,
rather than the complete eCos OS. That said, it is possible to build
eCos applications and we will do what we can to help out so long as you
are reasonably self sufficient (or have high volumes ;-))

Regards,
Ian
-- 
Ian Campbell, Senior Design Engineer
                                        Web: http://www.arcom.com
Arcom, Clifton Road,                    Direct: +44 (0)1223 403 465
Cambridge CB1 7EA, United Kingdom       Phone:  +44 (0)1223 411 200

             reply	other threads:[~2005-01-31 10:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-31 10:39 Ian Campbell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-31 10:08 bardozs

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=1107167930.14895.38.camel@icampbell-debian \
    --to=icampbell@arcom.com \
    --cc=bardozs@esiee.fr \
    --cc=ecos-devel@ecos.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).