Hello:
In the page 19 of the l4re-source document there is a description about caps as following:
Caps The table with application-specific named capabilities (default is an empty table). If the table does not contain a capability with the name ’rom’, the ’rom’ capability from Ned’s initial caps is inserted into the table.
How can i understand "If the table does not contain a capability with the name ’rom’, the ’rom’ capability from Ned’s initial caps is inserted into the table."
Thanks. Warm regards.
Cheng Guanghui
On Mon Jul 18, 2011 at 16:31:15 +0800, cheng guanghui wrote:
In the page 19 of the l4re-source document there is adescription about caps as following:
Caps The table with application-specific namedcapabilities (default is an empty table). If the table does not contain a capability with the name ’rom’, the ’rom’ capability from Ned’s initial caps is inserted into the table.
How can i understand "If the table does not contain acapability with the name ’rom’, the ’rom’ capability from Ned’s initial caps is inserted into the table."
It just means that ned always gives a 'rom' service to each app, either one explicitly set or, if that hasn't been done, the default one which happens to be the same 'rom' service used by ned itself. So in most cases you can omit specifying a 'rom' service as there will be the default one automatically.
Adam
Thanks for your explanation. Warm regards.
Cheng Guanghui
On Tue, Jul 19, 2011 at 4:37 AM, Adam Lackorzynski adam@os.inf.tu-dresden.de wrote:
On Mon Jul 18, 2011 at 16:31:15 +0800, cheng guanghui wrote:
In the page 19 of the l4re-source document there is a description about caps as following:
Caps The table with application-specific named capabilities (default is an empty table). If the table does not contain a capability with the name ’rom’, the ’rom’ capability from Ned’s initial caps is inserted into the table.
How can i understand "If the table does not contain a capability with the name ’rom’, the ’rom’ capability from Ned’s initial caps is inserted into the table."
It just means that ned always gives a 'rom' service to each app, either one explicitly set or, if that hasn't been done, the default one which happens to be the same 'rom' service used by ned itself. So in most cases you can omit specifying a 'rom' service as there will be the default one automatically.
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