public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: jerzy dyrda <jerzy.dyrda@kontron.pl>
To: ecos-discuss@ecos.sourceware.org,  ecos-devel@ecos.sourceware.org
Subject: Re: [ECOS] eCos on STR9 ?
Date: Tue, 16 Jun 2009 16:38:00 -0000	[thread overview]
Message-ID: <200906161838.35631.jerzy.dyrda@kontron.pl> (raw)
In-Reply-To: <48A1755F.3000400@jaeger.mine.nu>

Hello Folks, 

On Tuesday 12 August 2008 13:34:55 Christian Jaeger wrote:
> My interest is in running an OS on STR9 (STR9xFA, STR911/STR912). There
> is no mention of these chips whatsoever in the CVS sources, and the only
> information regarding running eCos on the STR9 has been the following
> posts by a few people interested in this, but it seems there has still
> nothing come out of this.
As I see after some serching of eCos mailing list I'm next one who is looking 
for any port eCos on this platform and would like to contribute community 
thus at start I have dummy question :
What is a status of this port? 

I apologize for asking questions of such sort but I like to known whether I 
start from zero or maybe someting is done according to common part of each  
BSP i.e.
1. HAL layer with configuration interrupt controller, memory controller, AHB 
bridge and so on -  
2. Serial driver
3. Ethernet driver
4. SPI driver

BTW.
What's wrong with ST processors that they aren't so widely supported compering 
to Atmel product? Situation in other "small" OS like FreeRTOS is only a bit 
better.   
-- 
Miłego dnia / Best regards
Jerzy 

       reply	other threads:[~2009-06-16 16:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48A1755F.3000400@jaeger.mine.nu>
2009-06-16 16:38 ` jerzy dyrda [this message]
2009-06-17  5:13   ` Andrew Lunn

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=200906161838.35631.jerzy.dyrda@kontron.pl \
    --to=jerzy.dyrda@kontron.pl \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=ecos-discuss@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).