Gary Thomas gthomas@redhat.com
Thu May 30 02:16:00 GMT 2002

On Thu, 2002-05-30 at 09:54, Koeller, T. wrote:
> 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
> 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
> 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).

Indeed this should be named better, indicating it's true use as an 
anonymous channel (currently only used by RedBoot for networking).

> 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?

I think you should just add your other new & exciting channels like 
we've already done on platforms which support such things.  A good place
to look would be the iPAQ (hal/arm/sa11x0/ipaq) which supports not only
serial but an LCD/touchscreen combo, or the Intel PC (hal/i386/pc) which
supports serial and the VGA/keybord combinations.

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

More information about the Ecos-discuss mailing list