diff options
author | patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3> | 2012-06-06 21:51:03 +0000 |
---|---|---|
committer | patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3> | 2012-06-06 21:51:03 +0000 |
commit | c3b4e1492850517906a96c57fefff332614aad4d (patch) | |
tree | 478dc6f3a755c7a69ecbaefac4311d32243a9d9b /nuttx/TODO | |
parent | 92fb15bdfedc185a9749f8cfae846ded9a729da5 (diff) | |
download | px4-nuttx-c3b4e1492850517906a96c57fefff332614aad4d.tar.gz px4-nuttx-c3b4e1492850517906a96c57fefff332614aad4d.tar.bz2 px4-nuttx-c3b4e1492850517906a96c57fefff332614aad4d.zip |
NFS update
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4808 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'nuttx/TODO')
-rw-r--r-- | nuttx/TODO | 21 |
1 files changed, 20 insertions, 1 deletions
diff --git a/nuttx/TODO b/nuttx/TODO index 5c2be8d81..2fe2b3807 100644 --- a/nuttx/TODO +++ b/nuttx/TODO @@ -35,7 +35,7 @@ nuttx/ (3) AVR (arch/avr) (0) Intel x86 (arch/x86) (4) 8051 / MCS51 (arch/8051/) - (2) MIPS/PIC32 (arch/mips) + (3) MIPS/PIC32 (arch/mips) (1) Hitachi/Renesas SH-1 (arch/sh/src/sh1) (4) Renesas M16C/26 (arch/sh/src/m16c) (10) z80/z8/ez80 (arch/z80/) @@ -1487,6 +1487,25 @@ o MIPS/PIC32(arch/mips) Status: Open Priority: Medium + Title: POSSIBLE INTERRUPT CONTROL ISSUE + Description: There is a kludge in the file arch/mips/src/common/up_idle.c. + Basically, if there is nothing else going on in the IDLE loop, + you have to disable then re-enable interrupts. Logically nothing + changes, but if you don't do this interrupts will be be disabled + in the IDLE loop which is a very bad thing to happen. + + Some odd behavior in the interrupt setup on the IDLE loop is + not really a big concern, but what I do not understand is if + this behavior is occurring on all threads after all context + switches: Are interrupts always disabled until re-enabled? + This requires some further investigation at some point; it + may be nothing but may also be a symptom of some changes + required to the interrupt return logic (perhaps some CP0 + status hazard?) + Status: Open + Priority: Low. Puzzling and needs some investigation, but there there + is no known misbehavior. + o Hitachi/Renesas SH-1 (arch/sh/src/sh1) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |