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 1001606] Enable the cache on Kinetis in RAM startup mode Date: Sat, 27 Oct 2012 07:56:00 -0000 [thread overview] Message-ID: <20121027075633.21ED02FB082C@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001606-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=1001606 Bernd Edlinger <bernd.edlinger@hotmail.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernd.edlinger@hotmail.de --- Comment #30 from Bernd Edlinger <bernd.edlinger@hotmail.de> 2012-10-27 08:56:30 BST --- Hi Ilija, just one or two things: In macro CYGHWR_HAL_KINETIS_CACHE_WAIT if the priorities do not need to be swapped, the delay loop seems to be missing. and generally the macro parameters should be used in brackets: example: #define CYGHWR_HAL_KINETIS_AXBS_CRS_PCTL(_x_) ((_x_ << CYGHWR_HAL_KINETIS_AXBS_CRS_PCTL_S)... here _x_ could be an expression and the macro should be written this way: #define CYGHWR_HAL_KINETIS_AXBS_CRS_PCTL(_x_) (((_x_) << CYGHWR_HAL_KINETIS_AXBS_CRS_PCTL_S)... same for CYGHWR_HAL_KINETIS_AXBS_PRS_MASTER_S, CYGHWR_HAL_KINETIS_AXBS_PRS_MASTER_PRIO, CYGHWR_HAL_KINETIS_AXBS_CRS_ARB, CYGHWR_HAL_KINETIS_CACHE_WAIT: parameter lmem_p used wwithout brackets. Regards, Bernd Edlinger. -- 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-10-27 7:56 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-02 16:03 [Bug 1001606] New: " bugzilla-daemon 2012-06-03 4:03 ` [Bug 1001606] " bugzilla-daemon 2012-06-03 20:10 ` bugzilla-daemon 2012-06-06 19:31 ` bugzilla-daemon 2012-06-10 0:05 ` bugzilla-daemon 2012-06-10 0:08 ` bugzilla-daemon 2012-06-10 20:35 ` bugzilla-daemon 2012-06-11 22:38 ` bugzilla-daemon 2012-06-11 22:43 ` bugzilla-daemon 2012-06-14 12:32 ` bugzilla-daemon 2012-06-16 1:14 ` bugzilla-daemon 2012-06-18 21:16 ` bugzilla-daemon 2012-06-23 5:58 ` bugzilla-daemon 2012-06-23 22:27 ` bugzilla-daemon 2012-06-26 20:54 ` bugzilla-daemon 2012-09-04 20:36 ` bugzilla-daemon 2012-09-04 21:19 ` bugzilla-daemon 2012-09-30 15:04 ` bugzilla-daemon 2012-10-03 20:21 ` bugzilla-daemon 2012-10-03 20:27 ` bugzilla-daemon 2012-10-07 17:24 ` bugzilla-daemon 2012-10-08 19:11 ` bugzilla-daemon 2012-10-08 19:15 ` bugzilla-daemon 2012-10-13 9:28 ` bugzilla-daemon 2012-10-16 20:53 ` bugzilla-daemon 2012-10-26 10:57 ` bugzilla-daemon 2012-10-26 11:01 ` bugzilla-daemon 2012-10-26 11:03 ` bugzilla-daemon 2012-10-27 7:56 ` bugzilla-daemon [this message] 2012-10-27 11:48 ` bugzilla-daemon 2012-10-27 11:58 ` bugzilla-daemon 2012-10-27 12:15 ` bugzilla-daemon 2012-10-27 12:58 ` bugzilla-daemon 2012-11-03 6:43 ` bugzilla-daemon 2012-11-03 15:31 ` bugzilla-daemon 2013-03-12 22:37 ` bugzilla-daemon -- strict thread matches above, loose matches on Subject: below -- 2012-06-02 16:03 [Bug 1001606] New: " bugzilla-daemon 2012-06-03 4:03 ` [Bug 1001606] " bugzilla-daemon 2012-06-03 20:10 ` bugzilla-daemon 2012-06-06 19:31 ` bugzilla-daemon 2012-06-09 9:35 ` bugzilla-daemon 2012-06-10 0:05 ` 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=20121027075633.21ED02FB082C@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).