public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Gregg C Levine <hansolofalcon@worldnet.att.net>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] What prompted the creation of the Linux Synthetic Target
Date: Thu, 20 Nov 2003 23:07:00 -0000	[thread overview]
Message-ID: <20031120230619.GG2130@lunn.ch> (raw)
In-Reply-To: <000601c3afb8$111d9320$0100a8c0@who5>

On Thu, Nov 20, 2003 at 05:45:49PM -0500, Gregg C Levine wrote:
> The explanation behind the creation of Linux Synthetic Target has
> always eluded me.

Its a much faster to use for development work than using real
hardware. You can go through the edit/compile/run/crash cycle much
faster since you don't have to wait for your slow serial link to
download the code before you run it and the debugger is much faster
since its all native.

You can do nearly everything you can do with real hardware using
synth.  There are flash drivers, serial driver, watchdog drivers,
ethernet drivers etc. Its also quite easy to emulate any special
hardware you might have on your target.

You can have many synth targets compared to the limited number of real
hardware targets you may have. The problem i've had in the past is
that the first 5 boards come of the pre-production line and the
management type people regularly steal them away from us software
engineers to show prospective customers, people who are funding you,
etc. It becomes really hard to do any work because you just don't have
the hardware on your desk.

For the must of the stuff i do, its not often i use real
hardware. Synth is just so much more convenient.

          Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

      reply	other threads:[~2003-11-20 23:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20 22:45 Gregg C Levine
2003-11-20 23:07 ` Andrew Lunn [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=20031120230619.GG2130@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=hansolofalcon@worldnet.att.net \
    /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).