From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001117] Cortex-M architecture fixes.
Date: Sun, 16 Jan 2011 14:06:00 -0000 [thread overview]
Message-ID: <20110116140611.32DA72F78004@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001117-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=1001117
--- Comment #2 from Ilija Kocho <ilijak@siva.com.mk> 2011-01-16 14:06:08 GMT ---
Hi Christophe
You seem to be right on both points. #1 should not be here and #2 is simply
swapped sources, shame on me :( .
Since you already have the Bug 1001090 let's continue discussion on SysTick
there. Also, considering that you are working on a yet another platform,
Stellaris,we could share some info on eventual similar Cortex-M architecture
issues and try to synchronize action.
Regarding this bug, I am going to put a patch that covers VTOR only.
Ilija
(In reply to comment #1)
> Hi Ilija,
>
> I made a patch for the system tick clock source some time ago: Bug 1001090 .
>
> Your patch seems to change the default behavior of the cortex M HAL:
>
> #1 CSR is initialised with CYGARC_REG_SYSTICK_CSR_TICKINT so you are enabling
> the interrupt.
>
> #2 Definition of CYGARC_REG_SYSTICK_CSR_CLK_EXT and
> CYGARC_REG_SYSTICK_CSR_CLK_INT was originally correct, your new definition is
> more difficult to understand. When CYGARC_REG_SYSTICK_CSR_CLK_SRC is not
> defined in CDLs, the clock source equal CYGARC_REG_SYSTICK_CSR_CLK_INT which
> actually makes the processor use external clock while by reading the code one
> might think that the processor should use internal clock.
>
> +#if !defined CYGARC_REG_SYSTICK_CSR_CLK_SRC
> +#define CYGARC_REG_SYSTICK_CSR_CLK_SRC CYGARC_REG_SYSTICK_CSR_CLK_INT
> +#endif
>
> Christophe
--
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-16 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-1001117-104@http.bugs.ecos.sourceware.org/>
2011-01-16 8:54 ` bugzilla-daemon
2011-01-16 10:21 ` bugzilla-daemon
2011-01-16 14:06 ` bugzilla-daemon [this message]
2011-01-16 14:15 ` bugzilla-daemon
2011-01-17 8:30 ` [Bug 1001117] Cortex-M arch. Provision for overriding of VTOR setting bugzilla-daemon
2011-01-17 21:32 ` bugzilla-daemon
2011-01-18 2:00 ` bugzilla-daemon
2011-01-19 19:00 ` bugzilla-daemon
2011-01-19 19: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=20110116140611.32DA72F78004@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).