public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001116] Instruct lwIP to use special section for buffers and heap. Date: Sat, 29 Jan 2011 19:32:00 -0000 [thread overview] Message-ID: <20110129193224.CEA172F80003@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001116-777@http.bugs.ecos.sourceware.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.
next prev parent reply other threads:[~2011-01-29 19:32 UTC|newest] Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-15 19:01 [Bug 1001116] New: " bugzilla-daemon 2011-01-16 8:53 ` [Bug 1001116] " bugzilla-daemon 2011-01-16 19:53 ` bugzilla-daemon 2011-01-16 21:11 ` bugzilla-daemon 2011-01-17 10:08 ` bugzilla-daemon 2011-01-18 1:43 ` bugzilla-daemon 2011-01-18 2:00 ` bugzilla-daemon 2011-01-22 18:15 ` bugzilla-daemon 2011-01-22 18:21 ` bugzilla-daemon 2011-01-22 22:06 ` bugzilla-daemon 2011-01-24 12:46 ` bugzilla-daemon 2011-01-26 20:15 ` bugzilla-daemon 2011-01-27 18:54 ` bugzilla-daemon 2011-01-28 12:26 ` bugzilla-daemon 2011-01-28 17:52 ` bugzilla-daemon 2011-01-29 12:51 ` bugzilla-daemon 2011-01-29 14:54 ` bugzilla-daemon 2011-01-29 19:32 ` bugzilla-daemon [this message] 2011-01-29 19:49 ` bugzilla-daemon 2011-01-29 20:15 ` bugzilla-daemon 2011-01-30 10:37 ` bugzilla-daemon 2011-01-30 11:50 ` bugzilla-daemon 2011-01-30 13:00 ` bugzilla-daemon 2011-01-30 13:53 ` bugzilla-daemon 2011-01-30 14:57 ` bugzilla-daemon 2011-01-30 16:01 ` bugzilla-daemon 2011-01-30 17:15 ` bugzilla-daemon 2011-01-30 17:39 ` bugzilla-daemon 2011-01-30 18:43 ` bugzilla-daemon 2011-01-30 19:22 ` bugzilla-daemon 2011-01-30 20:12 ` bugzilla-daemon 2011-01-30 20:54 ` bugzilla-daemon 2011-01-30 21:37 ` bugzilla-daemon 2011-01-30 21:38 ` bugzilla-daemon 2011-01-30 21:42 ` bugzilla-daemon 2011-01-30 21:53 ` bugzilla-daemon 2011-01-30 22:12 ` bugzilla-daemon 2011-01-30 22:26 ` bugzilla-daemon 2011-01-30 22:37 ` bugzilla-daemon 2011-01-31 8:52 ` bugzilla-daemon 2011-01-31 9:10 ` bugzilla-daemon 2011-01-31 9:56 ` bugzilla-daemon 2011-01-31 10:00 ` bugzilla-daemon 2011-01-31 11:07 ` bugzilla-daemon 2011-01-31 12:00 ` bugzilla-daemon 2011-01-31 17:06 ` bugzilla-daemon 2011-01-15 19:01 [Bug 1001116] New: " bugzilla-daemon 2011-01-16 8:53 ` [Bug 1001116] " bugzilla-daemon 2011-01-16 19:53 ` bugzilla-daemon 2011-01-16 21:11 ` bugzilla-daemon 2011-01-17 10:08 ` bugzilla-daemon 2011-01-18 1:43 ` bugzilla-daemon 2011-01-18 2:15 ` bugzilla-daemon 2011-01-22 18:15 ` bugzilla-daemon 2011-01-22 18:21 ` bugzilla-daemon 2011-01-22 22:06 ` bugzilla-daemon 2011-01-24 12:46 ` bugzilla-daemon 2011-01-26 20:15 ` bugzilla-daemon 2011-01-27 18:54 ` bugzilla-daemon 2011-01-28 12:26 ` bugzilla-daemon 2011-01-28 17:52 ` bugzilla-daemon 2011-01-29 12:51 ` bugzilla-daemon 2011-01-29 14:54 ` bugzilla-daemon 2011-01-29 19:32 ` bugzilla-daemon 2011-01-29 19:49 ` bugzilla-daemon 2011-01-29 20:15 ` bugzilla-daemon 2011-01-30 10:37 ` bugzilla-daemon 2011-01-30 11:50 ` bugzilla-daemon 2011-01-30 13:00 ` bugzilla-daemon 2011-01-30 13:53 ` bugzilla-daemon 2011-01-30 14:57 ` bugzilla-daemon 2011-01-30 16:01 ` bugzilla-daemon 2011-01-30 17:15 ` bugzilla-daemon 2011-01-30 17:39 ` bugzilla-daemon 2011-01-30 18:43 ` bugzilla-daemon 2011-01-30 19:22 ` bugzilla-daemon 2011-01-30 20:12 ` bugzilla-daemon 2011-01-30 20:54 ` bugzilla-daemon 2011-01-30 21:37 ` bugzilla-daemon 2011-01-30 21:38 ` bugzilla-daemon 2011-01-30 21:42 ` bugzilla-daemon 2011-01-30 21:53 ` bugzilla-daemon 2011-01-30 22:12 ` bugzilla-daemon 2011-01-30 22:26 ` bugzilla-daemon 2011-01-30 22:37 ` bugzilla-daemon 2011-01-31 8:52 ` bugzilla-daemon 2011-01-31 9:10 ` bugzilla-daemon 2011-01-31 9:56 ` bugzilla-daemon 2011-01-31 10:00 ` bugzilla-daemon 2011-01-31 11:07 ` bugzilla-daemon 2011-01-31 12:00 ` bugzilla-daemon 2011-01-31 17:06 ` bugzilla-daemon 2011-01-31 17:39 ` bugzilla-daemon 2011-01-31 18:16 ` bugzilla-daemon 2011-01-31 18:32 ` bugzilla-daemon 2011-01-31 18:34 ` bugzilla-daemon 2011-01-31 18:34 ` bugzilla-daemon 2011-01-31 18:59 ` bugzilla-daemon 2011-01-31 20:14 ` bugzilla-daemon 2011-01-31 21:55 ` bugzilla-daemon 2011-01-31 21:57 ` bugzilla-daemon 2011-01-31 22:02 ` bugzilla-daemon
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=20110129193224.CEA172F80003@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@bugs.ecos.sourceware.org \ /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: linkBe 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).