public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001456] HAL misses Interrupt Clear-Pending Registers handling: wasted processing power Date: Wed, 26 Sep 2012 21:44:00 -0000 [thread overview] Message-ID: <20120926214356.8BC4F2F7800C@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001456-777@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=1001456 Jonathan Larmour <jifl@ecoscentric.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED CC| |jifl@ecoscentric.com AssignedTo|unassigned@bugs.ecos.source |nickg@ecoscentric.com |ware.org | Ever Confirmed|0 |1 --- Comment #25 from Jonathan Larmour <jifl@ecoscentric.com> 2012-09-26 22:43:50 BST --- I still think this needs to be commented on by Nick as it involves a significant change to the HAL definition, and he's both the HAL in general and specifically Cortex-M HAL architect. So I'm assigning this to him and see if he grumbles :-). He can always assign it away if he's not interested in commenting on the API change. But I wouldn't overstate the problem, as far I can tell this will only happen with certain designs of devices, and only then if certain situations combine, which therefore makes it uncommon. That's not to say it's irrelevant, but it's not like it happens every interrupt or anything like that. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next prev parent reply other threads:[~2012-09-26 21:44 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-16 14:26 [Bug 1001456] New: " bugzilla-daemon 2012-01-24 16:11 ` [Bug 1001456] " bugzilla-daemon 2012-02-09 9:40 ` bugzilla-daemon 2012-02-09 11:30 ` bugzilla-daemon 2012-02-16 15:30 ` bugzilla-daemon 2012-02-23 9:58 ` bugzilla-daemon 2012-04-02 21:22 ` bugzilla-daemon 2012-09-26 16:15 ` bugzilla-daemon 2012-09-26 21:44 ` bugzilla-daemon [this message] 2012-01-16 14:26 [Bug 1001456] New: " bugzilla-daemon 2012-01-16 16:29 ` [Bug 1001456] " bugzilla-daemon 2012-02-09 14:23 ` bugzilla-daemon 2012-02-15 10:10 ` bugzilla-daemon 2012-02-15 10:48 ` bugzilla-daemon 2012-02-15 11:29 ` bugzilla-daemon 2012-02-16 15:30 ` bugzilla-daemon 2012-02-16 16:46 ` bugzilla-daemon 2012-02-23 9:05 ` bugzilla-daemon 2012-02-23 10:29 ` bugzilla-daemon 2012-04-02 8:10 ` bugzilla-daemon 2012-04-02 17:48 ` bugzilla-daemon 2012-04-02 21:22 ` bugzilla-daemon 2012-09-27 8:52 ` bugzilla-daemon 2012-09-27 12:39 ` bugzilla-daemon 2012-09-27 13:36 ` bugzilla-daemon 2012-09-27 18:09 ` 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=20120926214356.8BC4F2F7800C@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@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).