From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bart Veer To: Nick.Barnes@pobox.com Cc: ecos-discuss@sourceware.cygnus.com Subject: Re: [ECOS] Notes on static configuration of an eCos network interface Date: Mon, 17 Jul 2000 06:59:00 -0000 Message-id: <200007171359.OAA06167@sheesh.cygnus.co.uk> References: <25482.963837944@raven.ravenbrook.com> X-SW-Source: 2000-07/msg00150.html I am not qualified to answer most of these points, but: >>>>> "Nick" == Nick Barnes writes: Nick> Notes on static configuration of an eCos network interface Nick> 5.4. multiple static routes Nick> The config tool, build_bootp_record() and init_net() should Nick> be extended to allow the specification of multiple static Nick> routes, through TAG_IP_STATIC_ROUTES. The current implementation of CDL does not allow for multiple instantiations of something, e.g. you cannot have a configuration option that says I want n routes, and then configuration options are created on the fly to support the new routes (or existing configuration options are removed). Instead you could have an upper bound on the number of such routes and have the appropriate number of config options. Or you could put multiple routes into one configuration value, although extracting all the information at compile-time can then prove tricky. Alternatively the configury would support only the most common situation of a single route, with an opt-out to defer the whole thing to application code. I am not sure which of these approaches would be most appropriate in this case. Bart