[Bug 1001116] Instruct lwIP to use special section for buffers andheap.

[bugzilla-daemon at bugs dot ecos dot sourceware dot org]

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001116

--- Comment #14 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2011-01-29 19:32:20 GMT ---
Ilija, at the least I would stop on this

- lwip_net.cdl:

    cdl_option CYGSEM_LWIP_MEM_SECTION {
        ...
        flavor         bool
        default_value  0
        active_if      CYGDAT_LWIP_MEM_SECTION_NAME
    ...
    }

- lwipopts.h:

#if CYGSEM_LWIP_MEM_SECTION
#include <cyg/infra/cyg_type.h>
#define MEM_SECTION CYGBLD_ATTRIB_SECTION(CYGDAT_LWIP_MEM_SECTION_NAME)
#else
#define MEM_SECTION
#endif

- mem.c, memp.c: your Attachment 1094 

My comments on lwiP config:

- cdl option-semaphore CYGSEM_LWIP_MEM_SECTION is active if other package
  provides CYGDAT_LWIP_MEM_SECTION_NAME (string) *and* if user select it.
  (It will be "grayed" for the most eCos targets in `configtool' and this
  is okay).

- above is quite enough to expand the lwIP package by applying your patch
  for lwiP sources and to *close* this bug.

- if you want to force CYGSEM_LWIP_MEM_SECTION, you can distribute one
  ECM file to import, for example, `lwip_net.ecm' under your HAL `misc'
  directory which will do it (enable the option), and users will import
  all proper settings for your target in cases if they need lwIP stack.

My thoughts about HAL config:

It seems to me you can enter some generic CDL component, for example,
component CYG{MEM, or HWR}_HAL_..._SECTION where you can manage also
generic data option (HAL, !LWIP) CYGDAT_HAL_..._SECTION_NAME. Why is
it? I think your idea to utilize all memory can be useful for other
applications too (not only lwIP package). - Right?

Now, back to our distressful CYGDAT_LWIP_NET_SECTION_NAME data option.
This option in fact should be equal CYGDAT_HAL_..._SECTION_NAME data,
if lwIP package has been added (active_if CYGPKG_NET_LWIP).

Just now I would not refer to Bug 1001114 here again if we just want to
get new lwIP option to manage the placement of memory pools, in fact, to
have a way for new definition, MEM_SECTION. Let's apply it and go ahead.

What do you/others think?

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.