public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: John Mills <john.m.mills@alum.mit.edu>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] eCos configuration question (was Re: [ECOS] General Q  ...)
Date: Thu, 31 May 2007 15:19:00 -0000	[thread overview]
Message-ID: <465EE335.7020600@mlbassoc.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0705310930230.28807-100000@otter.localdomain>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Mills wrote:
> Leaving aside my responses to Andrew cut in below:
> 
>  1. How should I set or clear this switch in my *.ecc files? I don't
> recognize the entry in 'configtool'. Should I edit the *.ecc and 
> regenerate the tree? Edit the affected 'hal.h'?

You could edit the .ecc file and rerun 'ecosconfig tree'.  Editing the
hal.h file is useless as it may get regenerated.

More importantly, it would be useful to find out why this is being
set the way it is.  You can figure this out by reading the .ecc file.

> 
>  2. In general, is there a listing in eCos or RedBoot docs about these 
> [fairly obscure] switches?

Probably not much beyond the CDL files themselves.

Of course, if you want to contribute some documentation on the subject,
it would always be welcome :-)

> 
> Thanks for any guidance.
> 
>  - Mills
> 
> On Wed, 30 May 2007, Andrew Lunn wrote:
> 
>>> On Wed, 30 May 2007, Andrew Lunn wrote:
> 
>>>> 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
> 
>> ...  So the next question is why is it set to 1?
> 
>   If it was a clear decision, the reasons are lost in the mists of time!
> 
>>             cdl_option CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_VERSION {
>>                 display       "Claim version virtual vectors"
>>                 default_value { CYGSEM_HAL_VIRTUAL_VECTOR_INIT_WHOLE_TABLE }
>>                 description   "
>>                     This option will cause the version
>>                     virtual vectors to be claimed."
>>             }
> 
> 
>> Is CYGSEM_HAL_VIRTUAL_VECTOR_INIT_WHOLE_TABLE true?
>   Yes:
>   ../trapeze/ECOSBUILD/dist/install/include/pkgconf/hal.h:
>     #define CYGSEM_HAL_VIRTUAL_VECTOR_INIT_WHOLE_TABLE 1
> 
>>             cdl_option CYGSEM_HAL_VIRTUAL_VECTOR_INIT_WHOLE_TABLE {
>>                 display       "Initialize whole of virtual vector table"
>>                 default_value { CYG_HAL_STARTUP != "RAM" ||
>>                                 !CYGSEM_HAL_USE_ROM_MONITOR }
>   
>> do you have a RAM image?
> 
>   Not of RedBoot. Our eCos app is expanded into RAM for execution, but 
>   RedBoot lives in FLASH.
> 
>> Is CYGSEM_HAL_USE_ROM_MONITOR true?
>   Apparently not, if I 'grep'ed right.
> 
>  - John Mills
> 
> 


- --
- ------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGXuM0maKbSsQGV8ARAtdAAJ9hypuhBhuEsph2vLkVuUy3MfyA4gCcDwx9
P6Z0n4Vxz+p3mVG1+A0jL88=
=meV8
-----END PGP SIGNATURE-----

-- 
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-31 15:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 17:02 [ECOS] General Q: Calling RedBoot CLI function from eCos app 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
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 [this message]
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=465EE335.7020600@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --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).