Module: xenomai-2.4
Branch: master
Commit: 6fa28d0ae010b657588d0db3b8d33e80d2128e43
URL:    
http://git.xenomai.org/?p=xenomai-2.4.git;a=commit;h=6fa28d0ae010b657588d0db3b8d33e80d2128e43

Author: Philippe Gerum <r...@xenomai.org>
Date:   Fri May 29 00:23:07 2009 +0200

Remove misleading comment

---

 ksrc/nucleus/pod.c |   12 +++++-------
 1 files changed, 5 insertions(+), 7 deletions(-)

diff --git a/ksrc/nucleus/pod.c b/ksrc/nucleus/pod.c
index 113c9bf..5eef706 100644
--- a/ksrc/nucleus/pod.c
+++ b/ksrc/nucleus/pod.c
@@ -320,13 +320,11 @@ int xnpod_init(void)
         * because on some architectures, vmalloc memory may not be
         * accessed while running in physical addressing mode
         * (e.g. exception trampoline code on powerpc with standard
-        * MMU support - CONFIG_PPC_STD_MMU). Meanwhile, since we want
-        * to allow the system heap to be larger than 128Kb in
-        * contiguous memory, we can't restrict to using kmalloc()
-        * memory for it either.  Therefore, we manage a private stack
-        * pool for kernel-based threads which will be populated with
-        * the kind of memory the underlying arch requires, still
-        * allowing the system heap to rely on a vmalloc'ed segment.
+        * MMU support - CONFIG_PPC_STD_MMU).  Therefore, we manage a
+        * private stack pool for kernel-based threads which will be
+        * populated with the kind of memory the underlying arch
+        * requires, still allowing the system heap to rely on a
+        * vmalloc'ed segment.
         */
        heapaddr = xnarch_alloc_stack_mem(CONFIG_XENO_OPT_SYS_STACKPOOLSZ * 
1024);
 


_______________________________________________
Xenomai-git mailing list
Xenomai-git@gna.org
https://mail.gna.org/listinfo/xenomai-git

Reply via email to