From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001116] Instruct lwIP to use special section for buffers and heap.
Date: Fri, 28 Jan 2011 17:52:00 -0000 [thread overview]
Message-ID: <20110128175212.EF2792F80003@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001116-104@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 #11 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2011-01-28 17:52:10 GMT ---
(In reply to comment #10)
> (In reply to comment #9)
> > "Make it as simple as you can, and no simpler" :-) But,
> >
> > I would not use calculated command as you proposed
>
> Why not use calculated?
To be clear. I have only wanted an empty MEM_SECTION definition by default.
> By using calculated value we have a single entry point for section name.
> It can be further enhanced by following:
>
> cdl_component CYGDAT_LWIP_MEM_SECTION_NAME {
> ...
> legal_values { "ahb_bss" "ahb_0" }
> ...
> }
Ah, I missed that you need a choice from the list.
> >
> > cdl_option CYGDAT_LWIP_MEM_SECTION {
> > display "Special memory section for lwIP buffers"
> > default_value 0
> >
> > IMO, you can do it in your CDL (HAL)
> >
> > cdl_option CYGDAT_LWIP_MEM_SECTION_NAME {
> > ...
> > requires { CYGDAT_LWIP_MEM_SECTION == ... }
...so, I enterred a mess when I have been pointed on the 'booldata' above.
> > Comments?
>
> The combination that you are proposing inherently raises a conflict which I
> prefer to avoid.
> However I tried it and the conflict resolution offered by configtool is not
> what we want - it offers CYGDAT_LWIP_MEM_SECTION_NAME = 0 ??
Yes, I'm sorry, then that can be
cdl_package CYGPKG_NET_LWIP {
...
cdl_option CYGSEM_LWIP_MEM_SECTION {
display "Relocate memory pools"
flavor bool
calculated is_active(CYGDAT_LWIP_MEM_SECTION_NAME)
...
}
}
cdl_package CYGPKG_HAL_... {
...
cdl_option CYGDAT_LWIP_MEM_SECTION_NAME {
display "Name of section"
flavor data
default_value { "\".foo\"" }
legal_values { "\".foo\"" "\".bar\"" "\".baz\"" }
...
}
}
and the check will be simple
#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
Well, if HAL does not provide CYGDAT_LWIP_MEM_SECTION_NAME, that lwIP's
CYGSEM_LWIP_MEM_SECTION will be not defined and other targets (the most)
will be happy with
#define MEM_SECTION
Your target's CDL will turn on CDL option CYGSEM_LWIP_MEM_SECTION and
memory section name will be specified.
I hope I get it what you looking for.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-01-28 17:52 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-1001116-104@http.bugs.ecos.sourceware.org/>
2011-01-16 8:53 ` bugzilla-daemon
2011-01-16 19:53 ` bugzilla-daemon
2011-01-16 21:11 ` bugzilla-daemon
2011-01-17 9:47 ` 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 [this message]
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:11 ` 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=20110128175212.EF2792F80003@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@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: link
Be 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).