This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

CYGNUM_HAL_VIRTUAL_VECTOR_AUX_CHANNELS


Hi,

I am currently writing an ecos HAL for our hardware. The board has
a communication interface not yet supported by ecos that I want to
make available for use by RedBoot. In order to do so I have to
allocate another slot in the COMMS table, so I came across the
CYGNUM_HAL_VIRTUAL_VECTOR_AUX_CHANNELS option. I
found that in spite of its name, which would suggest that it is intended
for general use, it is firmly tied to RedBoot networking support, so if I
enable CYGPKG_REDBOOT_NETWORKING, then I cannot use
CYGNUM_HAL_VIRTUAL_VECTOR_AUX_CHANNELS to extend the
COMMS table size. I think I can cope with this by adding
'requires   !CYGPKG_REDBOOT_NETWORKING' to my cdl file.
However, this is a sub-optimum solution, as it precludes the use of
networking in RedBoot (this is not currently a problem for me, though).

I feel that CYGNUM_HAL_VIRTUAL_VECTOR_AUX_CHANNELS should
better be a user-configurable option in its own right, although this would
make it
difficult to check if a sufficient number of slots has been allocated for a
given
configuration. Or, better yet, CYGNUM_HAL_VIRTUAL_VECTOR_AUX_CHANNELS
should act as a counter that other options cann add to. I am, however,
completly ignorant of Tcl, so I don't know how to achieve this.

Any comments?

tk
----------------------------------------------- 
Thomas Koeller, Software Development 

Basler Vision Technologies 
An der Strusbek 60-62 
22926 Ahrensburg 
Germany 

Tel +49 (4102) 463-390 
Fax +49 (4102) 463-46390

mailto:Thomas.Koeller@baslerweb.com 
http://www.baslerweb.com 




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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]