public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001442] LPC17XX bit band macro proposal Date: Fri, 13 Jan 2012 15:45:00 -0000 [thread overview] Message-ID: <20120113154526.97AF82F7800B@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001442-13@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=1001442 --- Comment #4 from Ilija Kocho <ilijak@siva.com.mk> 2012-01-13 15:45:20 GMT --- (In reply to comment #3) > (In reply to comment #2) > > Perhaps the macros (especially for RAM but others could be considered) could > > have generic stem CORTEXM rather than LPC17XX. Could they be applied at > > architecture level? > > I've checked on the ARM site: > > - on Cortex-M3, bit banding is described as a feature always available (the > word 'option' is not used) : > http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0337e/Behcjiic.html > > - on Cortex-M4, bit banding is described as an optional feature: > http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0439c/Behcjiic.html > > eCos uses 'cortex-m' to describe the architecture generally and does not make > difference between M0/M3/M4, etc. Now maybe all chip manufacturers will > implement bit band? > Actually there is info on sub-architecture: CYGHWR_HAL_CORTEXM (in hal_cortexm.cdl). > However if bit banding is provided, it's always at the same place, it seems > that it has been designed mostly for peripherals registers or for peripherals > that maps into RAM, like the GPIO pins in the LPC17XX. > What I mean is: The macros can be used by every Cortex-M member that implements bit banding so they should be generic (within Cortex-M) rather than bonded to a specific product line. Then, they should reside in arch. level header. > > > > Also, could we consider defining a USER_SECTION for bit-band area? Then we > > shall have an easy way to put objects there by just __attribute__ing. > > USER_SECTION can be added to present ldi scripts without breaking > > compatibility. > > This is necessary if one wants to use bit band for RAM, for instance to place > device descriptors or buffers at location that allow bit banding. -- 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:[~2012-01-13 15:45 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-04 9:52 [Bug 1001442] New: " bugzilla-daemon 2012-01-04 9:53 ` [Bug 1001442] " bugzilla-daemon 2012-01-06 12:48 ` bugzilla-daemon 2012-01-10 14:51 ` bugzilla-daemon 2012-01-13 15:45 ` bugzilla-daemon [this message] [not found] <bug-1001442-777@http.bugs.ecos.sourceware.org/> 2012-01-06 12:47 ` bugzilla-daemon 2012-01-13 15:45 ` bugzilla-daemon 2012-01-26 18:32 ` 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=20120113154526.97AF82F7800B@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-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).