Hello:
In the modules.list there are 2 entires to boot hello demo as following:
entry hello roottask moe --init=rom/hello module l4re module hello
entry hello-cfg roottask moe rom/hello.cfg module l4re module ned module hello.cfg module hello
The booting logs are following separately :
hello
MOE: Hello world MOE: found 117648 KByte free memory MOE: found RAM from 1000 to 75c7000 MOE: allocated 117 KByte for the page array @0x1000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [136d000-1470e6d] [C:503000] l4re BOOTFS: [1471000-153030b] [C:504000] hello MOE: cmdline: /home/cheng/TUDOS/Src/l4re-snapshot-2011062216/obj/l4/x86/bin/x86_586/l4f/moe --init=rom/hello MOE: Starting: rom/hello MOE: loading 'rom/hello' Hello World! Hello World! Hello World!
hello-cfg
MOE: Hello world MOE: found 115604 KByte free memory MOE: found RAM from 1000 to 75c7000 MOE: allocated 117 KByte for the page array @0x1000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [136d000-1470e6d] [C:503000] l4re BOOTFS: [1471000-166e572] [C:504000] ned BOOTFS: [166f000-166f066] [C:505000] hello.cfg BOOTFS: [1670000-172f30b] [C:506000] hello MOE: cmdline: /home/cheng/TUDOS/Src/l4re-snapshot-2011062216/obj/l4/x86/bin/x86_586/l4f/moe rom/hello.cfg MOE: Starting: rom/ned rom/hello.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/hello.cfg' hello | Hello World! hello | Hello World! hello | Hello World! hello | Hello World! hello | Hello World! hello | Hello World! hello | Hello World!
So hello demo could be booted whatever from Ned or Moe directly. In the document Ned is described as this "The main thing to do here is to coordinate the startup of services and applications as well as to provide the communication channels for them". Does it mean "We use Ned just because we need to dynamically create IPC gate (channel) between different applications". If there is no need to use IPC gate we can use Moe directly to boot application. is it correct?
Thanks. Warm regards.
Cheng Guanghui
On Mon Jul 18, 2011 at 13:45:25 +0800, cheng guanghui wrote:
In the modules.list there are 2 entires to boot hello demo as following:entry hello roottask moe --init=rom/hello module l4re module hello
entry hello-cfg roottask moe rom/hello.cfg module l4re module ned module hello.cfg module hello
So hello demo could be booted whatever from Ned or Moedirectly. In the document Ned is described as this "The main thing to do here is to coordinate the startup of services and applications as well as to provide the communication channels for them". Does it mean "We use Ned just because we need to dynamically create IPC gate (channel) between different applications". If there is no need to use IPC gate we can use Moe directly to boot application. is it correct?
Ned launches apps, so if you just have one, you can start it directly without using ned inbetween. Also if you just have one app, there's also no need for any cross task channels obviously.
Adam
thanks a lot. best.
Cheng Guanghui
On Tue, Jul 19, 2011 at 4:31 AM, Adam Lackorzynski adam@os.inf.tu-dresden.de wrote:
On Mon Jul 18, 2011 at 13:45:25 +0800, cheng guanghui wrote:
In the modules.list there are 2 entires to boot hello demo as following:
entry hello roottask moe --init=rom/hello module l4re module hello
entry hello-cfg roottask moe rom/hello.cfg module l4re module ned module hello.cfg module hello
So hello demo could be booted whatever from Ned or Moe directly. In the document Ned is described as this "The main thing to do here is to coordinate the startup of services and applications as well as to provide the communication channels for them". Does it mean "We use Ned just because we need to dynamically create IPC gate (channel) between different applications". If there is no need to use IPC gate we can use Moe directly to boot application. is it correct?
Ned launches apps, so if you just have one, you can start it directly without using ned inbetween. Also if you just have one app, there's also no need for any cross task channels obviously.
Adam
Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
l4-hackers@os.inf.tu-dresden.de
-
Adam Lackorzynski -
cheng guanghui