public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "wang cui" <iucgnaw@msn.com>
To: andrew@lunn.ch, htalanki@comtechefdata.com
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] In-built shell for Redboot
Date: Thu, 01 Feb 2007 01:56:00 -0000	[thread overview]
Message-ID: <BAY110-F1782860033AF2681DD0F89A5A40@phx.gbl> (raw)
In-Reply-To: <20070130214625.GG22661@lunn.ch>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312; format=flowed, Size: 1955 bytes --]

I think he want to call function by name directly without a warpper of 
"RedBoot_cmd()" macro.

Actually VxWorks provide this function. It strips all symbles from 
application image, then generate a source file contains all symbles, then 
add it into project and rebuild it. Then user can call all functions 
directly from VxWorks shell.
However, I think Redboot style is good enough.

But what I am thinking about is: Can we divide the shell functionality from 
Redboot and create a new package(suppose to be RedShell)?
Because we always need a shell in application, and there are very many 
things have been implemented in Redboot. If so, we can reduce a lot of work 
in writing application shell.

>From: Andrew Lunn <andrew@lunn.ch>
>To: Harish Talanki <htalanki@comtechefdata.com>
>CC: ecos-discuss@ecos.sourceware.org
>Subject: Re: [ECOS] In-built shell for Redboot
>Date: Tue, 30 Jan 2007 22:46:25 +0100
>
>On Tue, Jan 30, 2007 at 02:09:52PM -0700, Harish Talanki wrote:
> > eCos Experts,
> >   Is there a way I can invoke a function call directly from the shell,
> > with Redboot boot loader.
>
> > I want to add bunch of function calls to the code, and be able to
> > directly invoke them from
> > command line. Is there any package or configuration option I need to
> > choose?
> >
> >   Right now I keep adding new Redboot Commands, to get arround this.
>
>What is the difference between adding a redboot command and calling a
>function? All a redboot command does is call a function.
>
>           Andrew
>
>--
>Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
>and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>

_________________________________________________________________
Ãâ·ÑÏÂÔØ MSN Explorer:   http://explorer.msn.com/lccn/  


-- 
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:[~2007-02-01  1:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 21:13 Harish Talanki
2007-01-30 21:46 ` Andrew Lunn
2007-02-01  1:56   ` wang cui [this message]
2007-02-01  7:48     ` Andrew Lunn
2007-02-01 17:23     ` Harish Talanki
2007-02-01 18:51     ` Sergei Gavrikov
2007-02-02  2:46       ` wang cui
2007-02-02 12:41         ` Gary Thomas
2007-02-01 10:08 Chris Zimman
2007-02-01 11:41 ` Andrew Lunn
2007-02-01 11:52 Chris Zimman

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=BAY110-F1782860033AF2681DD0F89A5A40@phx.gbl \
    --to=iucgnaw@msn.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=htalanki@comtechefdata.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).