public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: John Mills <johnmills@speakeasy.net>
To: ecos-discuss@ecos.sourceware.org
Cc: Andrew Lunn <andrew@lunn.ch>
Subject: Re: [ECOS] General Q: Calling RedBoot CLI function from eCos app
Date: Wed, 30 May 2007 21:06:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0705301555220.18257-100000@otter.localdomain> (raw)
In-Reply-To: <20070530202206.GG32489@lunn.ch>

Andrew -

Thanks for the reply.

On Wed, 30 May 2007, Andrew Lunn wrote:

> On Wed, May 30, 2007 at 02:11:43PM -0500, John Mills wrote:
> > Andrew -
> > 
> > Thanks for the lead, but in my eCos app that macro just expands to NULL.  
> > The same code line works perfectly in RedBoot's 'main.c', however.
> 
> What is the value of CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_VERSION in you
> application? See hal/common/current/src/hal_if.c

I find in my package configuration:

/home/jmills/depot/trapeze/ECOSBUILD/dist/install/include/pkgconf/hal.h:
 #define CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_VERSION 1

If I understand your track here, that would activate the following lines
in 'hal_if.c':

#ifdef CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_VERSION
    CYGACC_CALL_IF_MONITOR_VERSION_SET(0);
#endif

which, I suppose, would in turn cause
    CYGACC_CALL_IF_MONITOR_VERSION() to resolve as '0', or NULL.

Hence my <null> print string.

Is that sensible?

 - John


-- 
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-05-30 21:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 17:02 John Mills
2007-05-30 17:12 ` Gary Thomas
2007-05-30 17:16   ` Andrew Lunn
2007-05-30 17:20     ` Andrew Lunn
2007-05-30 17:58       ` John Mills
2007-05-30 19:18       ` John Mills
2007-05-30 21:00         ` Andrew Lunn
2007-05-30 21:06           ` John Mills [this message]
2007-05-30 21:41             ` Andrew Lunn
2007-05-31 15:01               ` [ECOS] eCos configuration question (was Re: [ECOS] General Q ...) John Mills
2007-05-31 15:19                 ` Gary Thomas
2007-05-31 15:21                   ` John Mills
2007-05-31 15:21                 ` [ECOS] " Andrew Lunn
2007-05-31 16:41                   ` Grant Edwards
2007-05-31 17:09                     ` [ECOS] Re: eCos configuration question Sergei Organov
2007-05-31 17:24                     ` [ECOS] Re: eCos configuration question (was Re: [ECOS] General Q ...) Paul D. DeRocco
2007-05-31 17:30                       ` Gary Thomas
2007-05-31 17:35                         ` Grant Edwards
2007-05-31 19:01                       ` Andrew Lunn
2007-05-31 17:18                 ` [ECOS] " Sergei Gavrikov
2007-06-01  8:10                   ` [ECOS] Re: eCos configuration question Daniel Néri
2007-06-01  9:04                     ` Sergei Gavrikov
2007-06-01 14:23                       ` Grant Edwards
2007-06-01 14:30                         ` Gary Thomas
2007-06-01 14:37                           ` Grant Edwards

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=Pine.LNX.4.44.0705301555220.18257-100000@otter.localdomain \
    --to=johnmills@speakeasy.net \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=john.m.mills@alum.mit.edu \
    /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).