public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Chris Gray <gray@acunia.com>
Cc: eCos discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Advice for student project
Date: Thu, 02 Aug 2001 10:08:00 -0000	[thread overview]
Message-ID: <3B698866.E59DAF04@redhat.com> (raw)
In-Reply-To: <3B691926.D5774A01@acunia.com>

Chris Gray wrote:
> 
> I have a couple of student interns assigned to work on porting our
> Java((TM)-compatible) VM to eCos.  (It's being done as a student
> project because that's the only way I could get the manpower: no
> one here seems to regard eCos as a ``strategic'' platform).
> 
> I don't want them to get bogged down in getting eCos to run in the
> first place, and we have only limited eCos expertise in-house
> (hi Jeroen), so I'd like them to work on well-supported platforms.
> My idea was to start with the linux synthetic target, and move
> on from that to the iPAQ.  Does that sound like a good plan, or
> does anyone have another kewl pocket-sized device to recommend?

If you don't have any device dependencies (at first), the Linux synth
target is a fine place to start. The iPaq is a sexy looking choice for
demos.

> And before anyone asks: the VM in question is scheduled to be
> released under a BSD-ish licence later this month.

Now that would be interesting :-).

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

  reply	other threads:[~2001-08-02 10:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02  1:54 Chris Gray
2001-08-02 10:08 ` Jonathan Larmour [this message]
2001-08-03  8:57   ` Chris Gray
2001-08-03  9:03     ` Jonathan Larmour
2001-08-14  0:36       ` Chris Gray
2001-08-03  9:05   ` Chris Gray

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=3B698866.E59DAF04@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gray@acunia.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).