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: Sun, 30 Jan 2011 21:53:00 -0000 [thread overview] Message-ID: <20110130215314.00B8F2F80003@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 #32 from Ilija Kocho <ilijak@siva.com.mk> 2011-01-30 21:53:11 GMT --- (In reply to comment #28) > (In reply to comment #27) > > (In reply to comment #26) > > > Well, let's stop on this point of survey. What do you think? > > [snip] > > Something like this? > > > > --- lwip_net.tcl --- > > > > cdl_component CYGOPT_LWIP_MEM_PLF_SPEC { > > display "Platform specific memory setting" > > flavor none > > no_define > > cdl_option CYGSEM_LWIP_MEM_SECTION { > > display "Place lwIP buffers and heap in special memory section." > > flavor bool > > default_value 1 > > active_if CYGDAT_LWIP_MEM_SECTION_NAME > > description "..." > > } > > } > > Ups, as I could understand your latest thing was > > default_value is_active(CYGDAT_LWIP_MEM_SECTION_NAME) > active_if CYGDAT_LWIP_MEM_SECTION_NAME Yes this is it. Sorry :( I pasted wrong snippet. > I'm starting to hate patch-review througout $BROWSER, I am again in a mess. Do > you *tested* this > > cdl_option CYGOPT_LWIP_MEM_SECTION { > default_value 1 > active_if CYGDAT_LWIP_MEM_SECTION_NAME > > or this one > > cdl_option CYGOPT_LWIP_MEM_SECTION { > default_value is_active(CYGDAT_LWIP_MEM_SECTION_NAME) > active_if CYGDAT_LWIP_MEM_SECTION_NAME I tested both, both work but the second one looks more appropriate in configtool. > Ilija, please, attach your latest and *tested* patch for review. > Here it is, this time from editor. I deleted description from CYGSEM_LWIP_MEM_SECTION since in your patch you have better. --- lwip_net.cdl --- cdl_component CYGOPT_LWIP_MEM_PLF_SPEC { flavor none display "Platform/application specific memory settings" description "Platform or application specific settings such as special memory section and memory constrains." cdl_option CYGSEM_LWIP_MEM_SECTION { display "Place lwIP buffers and heap in special memory section." flavor bool default_value is_active(CYGDAT_LWIP_MEM_SECTION_NAME) active_if CYGDAT_LWIP_MEM_SECTION_NAME description "..." } } --- hal...cdl example (this was correct in previous post) --- cdl_option CYGDAT_LWIP_MEM_SECTION_NAME { flavor data active_if CYGPKG_NET_LWIP parent CYGOPT_LWIP_MEM_PLF_SPEC default_value { "\".ahb_bss\"" } legal_values { "\".ahb_bss\"" "\".ahb_0\"" } display "Memory section for lwIP buffers." description " ... Sections are provided by LPC17xx platform HAL." } --- lwipopts.h (just for completness) ---- #if defined(CYGSEM_LWIP_MEM_SECTION) && 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 ----------------------- > I see you prefer "one step" assigned, this is your choice and this for > Bugzilla 1001114. Yes. If we do not need concatenation, let's keep it simple. -- 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-30 21:53 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 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 [this message] 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 -- strict thread matches above, loose matches on Subject: below -- 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=20110130215314.00B8F2F80003@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).