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: Fri, 03 Aug 2001 09:03:00 -0000	[thread overview]
Message-ID: <3B6ACB5D.4B836CCA@redhat.com> (raw)
In-Reply-To: <3B6A9683.E4878B47@acunia.com>

Chris Gray wrote:
> 
> Jonathan Larmour wrote:
> 
> >
> > 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.
> 
> The iPAQ can also be seen as resembling forthcoming PDAs, 3G mobile
> phones, etc..  Elsewhere in this company there are people wrestling with
> WinCE / Creme in order to demonstrate our telematics framework.  I am
> hoping (nay, I am confident) that we can demonstrate something which
> beats that on every front, using outr own VM and eCos.

And a lot cheaper too (both upfront and royalty), and smaller (resource
footprint) as well as having full control over the sources.
 
> One thing we do need is IP connectivity.  IIRC the synthetic target
> doesn't have that.  I'm assuming that dial-up PPP over a PCMCIA
> modem on the iPAQ will work.

There isn't PPP support in eCos I'm afraid. There _is_ compact flash
ethernet support for the iPAQ however.

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-03  9:03 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
2001-08-03  8:57   ` Chris Gray
2001-08-03  9:03     ` Jonathan Larmour [this message]
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=3B6ACB5D.4B836CCA@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).