public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Les Miklosy PE <les@softwaretospec.com>
Cc: <ecos-maintainers@sourceware.org>
Subject: Re: Contacting John Dallaway
Date: Sat, 29 Nov 2014 13:48:00 -0000	[thread overview]
Message-ID: <355f4d8e9aeda9dc195f5ec60582ea83@localhost> (raw)
In-Reply-To: <546CF5A3.1050800@softwaretospec.com>

Les

On Wed, 19 Nov 2014 11:55:15 -0800, Les Miklosy PE
<les@softwaretospec.com>
wrote:

> Ten days ago I posted the results of an eCos port for the Sparc 
> Leon2/3/FT processors to the eCos Group at Linked-In 
>
<https://www.linkedin.com/groups?home=&gid=1882065&trk=my_groups-tile-grp> 
> where John Dallaway is host. Since the post drew no interest from anyone

> I decided perhaps contacting John through the maintainers list would be 
> productive.
> 
> The eCos supported hardware list 
> <http://ecos.sourceware.org/hardware.html> shows Sparc Leon was 
> contributed by Gaisler Research (now Aeroflex) but with an interface  
> through a proprietary ROM monitor. The eCos build I propose is a 
> stand-alone Redboot boot-strap with a ROM monitor stub for a direct 
> connection to gdb for debugging.
> 
> Perhaps John Dallaway or someone else can explain the lack of interest 
> in my Linked-In post and comment on the value of my contribution with
eCos.
> 
> Thank you for reading.

You are welcome to contact me directly, but I have no exposure to the ESA
and its specific requirements and it seems that this is what you are
looking for. You might have more success in contacting ESA engineers via a
more generic forum or an ESA forum.

Regards

John Dallaway

      reply	other threads:[~2014-11-29 13:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <546BF20E.6020309@softwaretospec.com>
2014-11-19 20:02 ` Les Miklosy PE
2014-11-29 13:48   ` John Dallaway [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=355f4d8e9aeda9dc195f5ec60582ea83@localhost \
    --to=john@dallaway.org.uk \
    --cc=ecos-maintainers@sourceware.org \
    --cc=les@softwaretospec.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).