---
c/src/lib/libbsp/mips/shared/irq/exception.S |1 -
c/src/lib/libbsp/sparc/shared/irq_asm.S |2 +-
c/src/lib/libcpu/sparc64/shared/score/interrupt.S |1 -
cpukit/sapi/include/confdefs.h| 28 -
Mark POSIX Keys and POSIX Key Value Pairs as supported.
Add list of unsupported object classes.
Add hint to unified work areas.
Add example.
---
doc/user/conf.t | 40
1 Datei geändert, 36 Zeilen hinzugefügt(+), 4 Zeilen entfernt(-)
diff --git
Looks good to me.
On Tue, Apr 29, 2014 at 10:57 AM, Ralf Kirchner
ralf.kirch...@embedded-brains.de wrote:
Mark POSIX Keys and POSIX Key Value Pairs as supported.
Add list of unsupported object classes.
Add hint to unified work areas.
Add example.
---
doc/user/conf.t | 40
+1
One odd thought.. Can we detect when objects which are not unlimited are
configured that way?
On Apr 29, 2014 10:40 AM, Gedare Bloom ged...@rtems.org wrote:
Looks good to me.
On Tue, Apr 29, 2014 at 10:57 AM, Ralf Kirchner
ralf.kirch...@embedded-brains.de wrote:
Mark POSIX Keys and POSIX
I recently tried to compile and run my RTEMS kernel image (
github.com/alanc98/rki ) on the latest git head. I was able to get past
a configuration option change:
#define CONFIGURE_MAXIMUM_TASKS 1024
kept the system from starting, so I changed it to 128 and it comes up.
But now I do not get a
