public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001291] New HAL for Cortex-M3 Smartfusion device
Date: Sun, 12 Feb 2012 12:16:00 -0000	[thread overview]
Message-ID: <20120212121600.91FA82F78004@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001291-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=1001291

--- Comment #47 from Ilija Kocho <ilijak@siva.com.mk> 2012-02-12 12:15:56 GMT ---
(In reply to comment #46)
> Hi Ilija,
> 
> I will check again the status of the new disclaimer and revert to you.
> 
> However, I would like to fix Bug 1001449 first. I see in your attachment (Flash
> driver SST25XX SPI tests 120206) from Bug 1001450
> that you have defined CYGNUM_DEVS_FLASH_SPI_SS25XX_MAP_ADDR directly in the
> test case (flash_sst25xx_test.c), instead of spreading 
> CYGNUM_DEVS_FLASH_SPI_SST25XX_DEV0_MAP_ADDR.

Nice catch. Thank you for pointing this out. It is a ghost from old code.

> 
> In my proposal (1001449), I suggested to have a platform specific include in
> the test case C file that provides the configuration of the platform flash:
> 
> #include CYGDAT_DEVS_FLASH_SPI_AT25DFXXX_PLF_CDL
> 
> And CYGDAT_DEVS_FLASH_SPI_AT25DFXXX_PLF_CDL is defined in the platform CDL as
> done other places:
> 
> define_proc {
>         puts $::cdl_system_header "#define
> CYGDAT_DEVS_FLASH_SPI_AT25DFXXX_PLF_CDL
> <pkgconf/devs_flash_cortexm_a2f200_eval.h>"
>     }
> 
> What do you think?

I have defined CYGNUM_DEVS_FLASH_SPI_SST25XX_DEV0_MAP_ADDR in the driver CDL
but you are right. Things like this, I would call them /configurable constants/
should come from the HAL. Every platform can have it's own address space.
I am going to change it, only, I would parent
CYGNUM_DEVS_FLASH_SPI_SST25XX_DEV0_MAP_ADDR (or
CYGDAT_DEVS_FLASH_SPI_AT25DFXXX_PLF_CDL) by their respective FLASH drivers.

Regards
Ilija

P.S.
Speaking of HAL /configurable constants/, you may find interesting to see and
comment (and I hope consider for Smartfusion) my discussion
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001397#c13 with Tomas Frydrych
regarding consolidated /Interrupt Priority Scheme/. I think that it will be of
help to application programmers for tuning real-time system behavior.
You can see this feature implemented implemented in the latest Variant and
Platform (as well as affected driver) attachments in Bug 1001450.

-- 
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-02-12 12:16 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20 21:01 [Bug 1001291] New: " bugzilla-daemon
2011-07-20 21:02 ` [Bug 1001291] " bugzilla-daemon
2011-07-20 21:03 ` bugzilla-daemon
2011-07-20 21:03 ` bugzilla-daemon
2011-07-20 21:04 ` bugzilla-daemon
2011-07-20 21:05 ` bugzilla-daemon
2011-07-20 21:05 ` bugzilla-daemon
2011-07-20 21:06 ` bugzilla-daemon
2011-07-20 21:07 ` bugzilla-daemon
2011-07-20 21:09 ` bugzilla-daemon
2011-07-20 21:11 ` bugzilla-daemon
2011-07-20 21:20 ` bugzilla-daemon
2011-07-23 11:36 ` bugzilla-daemon
2011-07-26 12:47 ` bugzilla-daemon
2011-10-12 22:05 ` bugzilla-daemon
2011-10-13  7:22 ` bugzilla-daemon
2011-10-13 16:37 ` bugzilla-daemon
2011-11-10  4:33 ` bugzilla-daemon
2011-11-11 16:37 ` bugzilla-daemon
2011-11-11 16:40 ` bugzilla-daemon
2011-11-11 17:48 ` bugzilla-daemon
2011-11-14  0:28 ` bugzilla-daemon
2011-11-14  8:33 ` bugzilla-daemon
2011-11-14 22:05 ` bugzilla-daemon
2011-11-14 22:31 ` bugzilla-daemon
2011-11-20 13:35 ` bugzilla-daemon
2011-11-20 13:38 ` bugzilla-daemon
2011-12-03 15:48 ` bugzilla-daemon
2011-12-03 16:50 ` bugzilla-daemon
2011-12-18 16:25 ` bugzilla-daemon
2011-12-18 16:25 ` bugzilla-daemon
2011-12-18 16:26 ` bugzilla-daemon
2011-12-18 16:27 ` bugzilla-daemon
2011-12-18 16:28 ` bugzilla-daemon
2011-12-18 16:28 ` bugzilla-daemon
2011-12-18 16:29 ` bugzilla-daemon
2011-12-18 16:30 ` bugzilla-daemon
2011-12-18 16:33 ` bugzilla-daemon
2012-01-02 18:39 ` bugzilla-daemon
2012-01-07 14:23 ` bugzilla-daemon
2012-01-07 14:37 ` bugzilla-daemon
2012-01-07 22:45 ` bugzilla-daemon
2012-01-07 23:10 ` bugzilla-daemon
2012-01-07 23:22 ` bugzilla-daemon
2012-01-08  8:49 ` bugzilla-daemon
2012-02-10 13:24 ` bugzilla-daemon
2012-02-12 10:16 ` bugzilla-daemon
2012-02-12 12:16 ` bugzilla-daemon [this message]
2012-02-13  1:39 ` bugzilla-daemon
2012-02-26 11:26 ` bugzilla-daemon
2012-02-26 11:26 ` bugzilla-daemon
2012-02-26 11:30 ` bugzilla-daemon
2012-02-26 11:30 ` bugzilla-daemon
2012-02-26 11:31 ` bugzilla-daemon
2012-02-26 11:33 ` bugzilla-daemon
2012-02-28 17:48 ` bugzilla-daemon
2012-02-28 17:49 ` bugzilla-daemon
2012-03-07 21:48 ` bugzilla-daemon
2012-03-07 21:50 ` bugzilla-daemon
2012-03-07 21:51 ` bugzilla-daemon
2012-03-07 21:52 ` bugzilla-daemon
2012-03-07 21:53 ` bugzilla-daemon
2012-03-07 21:55 ` bugzilla-daemon
2012-03-07 22:00 ` bugzilla-daemon
2012-03-12 18:36 ` bugzilla-daemon
2012-03-12 22:10 ` bugzilla-daemon
2012-03-13 19:07 ` bugzilla-daemon
2012-03-13 20:24 ` bugzilla-daemon
2012-03-31 14:38 ` bugzilla-daemon
2012-04-01  8:04 ` bugzilla-daemon
2012-04-01  9:07 ` bugzilla-daemon
2012-04-01 19:37 ` bugzilla-daemon
2013-02-12 20:41 ` bugzilla-daemon
2017-02-15  7:18 ` 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=20120212121600.91FA82F78004@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).