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 18:43:00 -0000 [thread overview] Message-ID: <20110130184333.0396C2F80003@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 #25 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2011-01-30 18:43:30 GMT --- (In reply to comment #24) > (In reply to comment #22) > > Maybe this will be obsolete comment, but > > > > (In reply to comment #18) > > > (In reply to comment #17) > > > Therefore i would prefer something that will not depend on ECM. One way > > > is: > > > > > > cdl_option CYGOPT_LWIP_MEM_SECTION { > > > ... > > > default_value 1 > > > ... > > > } > > > > I disagreed with above, as for the most targets we will see *grayed* and > > *checked* box in CT: > > > > [x] Use additional memory section > > > > To reduse mouse traffic you can use such a trick: > > > > cdl_option CYGOPT_LWIP_MEM_SECTION { > > ... > > default_value { is_substr(CYGDAT_LWIP_MEM_SECTION_NAME, ".") } > > active_if CYGDAT_LWIP_MEM_SECTION_NAME > > > > The box will be unchecked until booldata in your HAL (CYGDAT_.*_NAME) is > > not proper section name. However, this was quickly tested only. > > I have noticed it, but I allowed to occur it since I have seen similar > behavior in some other CDLs. Ilija, I have managed this with: cdl_component CYGOPT_LWIP_MEM_PLF_SPEC { display "Platform specific memory setting" flavor none no_define cdl_option CYGOPT_LWIP_MEM_SECTION { display "Use additional memory section" flavor bool calculated { CYGDAT_LWIP_MEM_SECTION_NAME && \ is_substr(CYGDAT_LWIP_MEM_SECTION_NAME, ".") } active_if CYGDAT_LWIP_MEM_SECTION_NAME ... But the difficulty to read/understand came back :-) However, it checks that NAME is string and at the least it looks like section name. > Actually I tried something similar > > cdl_option CYGOPT_LWIP_MEM_SECTION { > ... > default_value is_active(CYGDAT_LWIP_MEM_SECTION_NAME) > active_if CYGDAT_LWIP_MEM_SECTION_NAME I will try it in CT. > But I'm not sure if it depends on the order the packages are processed/ > applied. FYI it worked for my test case (select default template then add > lwip). Ilija, I tested builds/configure for the below lwip_net.cdl: ---- cdl_component CYGOPT_LWIP_MEM_PLF_SPEC { display "Platform specific memory setting" flavor none no_define cdl_option CYGOPT_LWIP_MEM_SECTION { display "Use additional memory section" flavor bool calculated { CYGDAT_LWIP_MEM_SECTION_NAME && \ is_substr(CYGDAT_LWIP_MEM_SECTION_NAME, ".") } active_if CYGDAT_LWIP_MEM_SECTION_NAME ### ... ### } } hal_..._foo.cdl ---- ### For test purposes ### cdl_option CYGHWR_HAL_MEM_SECTION_NAME { flavor data # FIXME: default_value { "\".2ram.foo\"" } legal_values { "\".2ram.foo\"" "\".2ram.bar\"" } ### ... ### } ### For test purposes ### cdl_option CYGDAT_LWIP_MEM_SECTION_NAME { display "Memory section attribute name" parent CYGOPT_LWIP_MEM_PLF_SPEC active_if CYGPKG_NET_LWIP flavor booldata default_value { CYGHWR_HAL_MEM_SECTION_NAME } ### ... ### } But I myself have argued for simplicity. Can you try it on your target? -- 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 18:43 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 [this message] 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 -- 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=20110130184333.0396C2F80003@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).