public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Doyle, Patrick" <WPD@dtccom.com>
To: "'Volker Kamp'" <vk@volkerkamp.com>, ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Self extracting target installer
Date: Fri, 09 Jul 2004 15:11:00 -0000	[thread overview]
Message-ID: <F18ED44D2778844592DFB732956B6651B52D97@DTCNT40S4> (raw)

> -----Original Message-----
> From: Volker Kamp [mailto:vk@volkerkamp.com] 
> Sent: Friday, July 09, 2004 11:10 AM
> To: ecos-discuss@sources.redhat.com
> Subject: AW: [ECOS] Self extracting target installer
> 
> What about using a scriptable terminal program like ZOC? You 
> can control all
> the action within a script: typing, downloading, checking 
> replys etc. It
> would save a lot of work.
> Or use "expect" on linux.
> Regards,
> Volker
> 
I thought of that too -- either approach requires a certain amount of
development time (to get the script right, to handle error cases, etc...)
The self extracting installer is more attractive to me because
1) I can give manufacturing a single, revision controlled, file  and know
that everything they produce will be identical (if I've done my job right).
2) Id the intaller does not depend upon a ROM monitor for anything, it could
even upgrade RedBoot from the default one that is preprogrammed in flash.
(Yes, I could write the script to load/download a RAM based RedBoot,
download the new ROM based RedBoot, etc...., but if I write a general
installer, it can do all of that).

--wpd

Patrick Doyle
DSP Design Engineer
(603) 546-2179

 

This communication is from DTC Communications, Inc. and is intended to be
confidential and solely for the use of the persons or entities addressed
above.  If you are not an intended recipient, be aware that the information
contained herein may be protected from unauthorized use by privilege or law,
and any copying, distribution, disclosure, or other use of this information
is prohibited.  If you have received this communication in error, please
contact the sender by return e-mail or telephone the above number
immediately and delete or destroy all copies.  Thank you for your
cooperation.

 



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

             reply	other threads:[~2004-07-09 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-09 15:11 Doyle, Patrick [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-12 13:38 Doyle, Patrick
2004-07-15 13:11 ` Doyle, Patrick
2004-07-09 17:27 agyhoo
2004-07-09 17:50 ` Andrew Lunn
2004-07-09 14:55 Doyle, Patrick
2004-07-09 17:04 ` 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=F18ED44D2778844592DFB732956B6651B52D97@DTCNT40S4 \
    --to=wpd@dtccom.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=vk@volkerkamp.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).