public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
* [Issue 1000660] ARM HAL breaks on spurious interrupt [not found] <bug-1000660-13@http.bugzilla.ecoscentric.com/> @ 2010-11-15 2:50 ` bugzilla-daemon 2010-11-15 3:09 ` bugzilla-daemon 1 sibling, 0 replies; 4+ messages in thread From: bugzilla-daemon @ 2010-11-15 2:50 UTC (permalink / raw) To: ecos-bugs Please do not reply to this email. Use the web interface provided at: https://bugzilla.ecoscentric.com/show_bug.cgi?id=1000660 Joe Porthouse <jporthouse@idexcorp.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jporthouse@idexcorp.com --- Comment #2 from Joe Porthouse <jporthouse@idexcorp.com> 2010-11-15 02:49:15 GMT --- Appears to have already been addressed in latest version. Problem was present in eCos v2.0. When a spurious interrupt occurred, interrupt_end() was never called and the scheduler was still locked on return to the application. In eCosPro v3.0.23, there are changes in the arm vectors.S file that specifically address making sure the scheduler is unlocked when dealing with spurious interrupts. In /hal/arm/arc/current/src/vectors.S // For a spurious interrupt, pass a NULL object. interrupt_end() will // handle that and still unlock the scheduler. Status on this issue should be closed. -- Configure issuemail: https://bugzilla.ecoscentric.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the issue. You are on the CC list for the issue. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Issue 1000660] ARM HAL breaks on spurious interrupt [not found] <bug-1000660-13@http.bugzilla.ecoscentric.com/> 2010-11-15 2:50 ` [Issue 1000660] ARM HAL breaks on spurious interrupt bugzilla-daemon @ 2010-11-15 3:09 ` bugzilla-daemon 1 sibling, 0 replies; 4+ messages in thread From: bugzilla-daemon @ 2010-11-15 3:09 UTC (permalink / raw) To: ecos-bugs Please do not reply to this email. Use the web interface provided at: https://bugzilla.ecoscentric.com/show_bug.cgi?id=1000660 --- Comment #3 from Jonathan Larmour <jifl@ecoscentric.com> 2010-11-15 03:08:58 GMT --- The bug must remain open for eCos. eCosPro is not the same as eCos. eCosPro is a commercial distribution supported by eCosCentric - yes it is free software, in the sense the Free Software Foundation applies it. But eCos is both free in that sense and free of cost. While clearly similar and related, they may have different features and bug fixes, and this happens to be one. -- Configure issuemail: https://bugzilla.ecoscentric.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the issue. You are on the CC list for the issue. ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <bug-1000660-776@http.bugzilla.ecoscentric.com/>]
* [Issue 1000660] ARM HAL breaks on spurious interrupt [not found] <bug-1000660-776@http.bugzilla.ecoscentric.com/> @ 2010-11-15 2:50 ` bugzilla-daemon 2010-11-15 3:09 ` bugzilla-daemon 1 sibling, 0 replies; 4+ messages in thread From: bugzilla-daemon @ 2010-11-15 2:50 UTC (permalink / raw) To: backlog Please do not reply to this email. Use the web interface provided at: https://bugzilla.ecoscentric.com/show_bug.cgi?id=1000660 Joe Porthouse <jporthouse@idexcorp.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jporthouse@idexcorp.com --- Comment #2 from Joe Porthouse <jporthouse@idexcorp.com> 2010-11-15 02:49:15 GMT --- Appears to have already been addressed in latest version. Problem was present in eCos v2.0. When a spurious interrupt occurred, interrupt_end() was never called and the scheduler was still locked on return to the application. In eCosPro v3.0.23, there are changes in the arm vectors.S file that specifically address making sure the scheduler is unlocked when dealing with spurious interrupts. In /hal/arm/arc/current/src/vectors.S // For a spurious interrupt, pass a NULL object. interrupt_end() will // handle that and still unlock the scheduler. Status on this issue should be closed. -- Configure issuemail: https://bugzilla.ecoscentric.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the issue. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Issue 1000660] ARM HAL breaks on spurious interrupt [not found] <bug-1000660-776@http.bugzilla.ecoscentric.com/> 2010-11-15 2:50 ` bugzilla-daemon @ 2010-11-15 3:09 ` bugzilla-daemon 1 sibling, 0 replies; 4+ messages in thread From: bugzilla-daemon @ 2010-11-15 3:09 UTC (permalink / raw) To: backlog Please do not reply to this email. Use the web interface provided at: https://bugzilla.ecoscentric.com/show_bug.cgi?id=1000660 --- Comment #3 from Jonathan Larmour <jifl@ecoscentric.com> 2010-11-15 03:08:58 GMT --- The bug must remain open for eCos. eCosPro is not the same as eCos. eCosPro is a commercial distribution supported by eCosCentric - yes it is free software, in the sense the Free Software Foundation applies it. But eCos is both free in that sense and free of cost. While clearly similar and related, they may have different features and bug fixes, and this happens to be one. -- Configure issuemail: https://bugzilla.ecoscentric.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the issue. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-11-15 3:09 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-1000660-13@http.bugzilla.ecoscentric.com/>
2010-11-15 2:50 ` [Issue 1000660] ARM HAL breaks on spurious interrupt bugzilla-daemon
2010-11-15 3:09 ` bugzilla-daemon
[not found] <bug-1000660-776@http.bugzilla.ecoscentric.com/>
2010-11-15 2:50 ` bugzilla-daemon
2010-11-15 3:09 ` bugzilla-daemon
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).