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, 23 Jun 2012 05:58:00 -0000	[thread overview]
Message-ID: <20120623055835.414102F78007@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

--- Comment #13 from Jonathan Larmour <jifl@ecoscentric.com> 2012-06-23 06:58:21 BST ---
(In reply to comment #12)
> I want to preserve also integral functionality of the part builder
> CYGHWR_HAL_CORTEXM_KINETIS, including FPU option.
> CYGHWR_HAL_CORTEXM_KINETIS_FPU selects FPU as Kinetis option and
> CYGHWR_HAL_CORTEXM_FPU enables/disables FPU function so they aren't identical.

Okay, I see what you're getting at - so the part can match what the user has,
even if they're not actually using the FPU. That's fine.

> But it's true that they look alike so below is CYGHWR_HAL_CORTEXM_KINETIS_FPU
> reshaped to resemble the other entries of the part builder
> (CYGHWR_HAL_CORTEXM_KINETIS_FLEXNVM can be reshaped likewise).
> 
>         cdl_option CYGHWR_HAL_CORTEXM_KINETIS_FPU {
>             display          "Floating Point Unit part name option"
>             flavor           data
>             no_define
>             legal_values  { "D" "F" }
>             default_value { "D" }
>             requires      { CYGHWR_HAL_CORTEXM_FPU implies
>                             CYGHWR_HAL_CORTEXM_KINETIS_FPU == "F" }

You also need to have the converse:
             requires      { !CYGHWR_HAL_CORTEXM_FPU implies
                             CYGHWR_HAL_CORTEXM_KINETIS_FPU == "D" }

But other than that, that's fine by me.

>             description "Select/indicate whether the part has Floating Point
> Unit. \"F\" - stands for 
>             parts with FPU, while \"D\" for ones without."

Just say "Select".

Thanks!

Jifl

-- 
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.


  parent reply	other threads:[~2012-06-23  5:58 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 [this message]
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
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=20120623055835.414102F78007@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: 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).