Lines Matching +full:application +full:- +full:specific

1 .. zephyr:code-sample:: userspace_prod_consumer
10 and generates interrupts with pointers to this data. The application needs
16  - Multiple logical applications, each with their own memory domain
17  - Creation of a sys_heap and assignment to a memory partition
18  - Use of APIs like ``k_queue_alloc_append()`` which require thread resource
20  - Management of permissions for kernel objects and drivers
21  - Show how application-specific system calls are defined
22  - Show IPC between ISR and application (using ``k_msgq``) and
23    application-to-application IPC (using ``k_queue``)
24  - Show how to create application-specific system calls
26 In this example, we have an Application A whose job is to talk to the
28 Application B.
30 Application B simply processes the data. Let's pretend this data is
31 untrusted and possibly malicious, so Application B is sandboxed from
36  - Sample driver issues interrupts, invoking its associated callback
37    function with a fixed-sized data payload.
38  - App A callback function, in supervisor mode, places the data payload
40  - App A monitor thread in user mode waits for data in the message queue.
43    monitored by application B.
44  - Application B processing thread waits on new items in the queue. It
45    then processes the data in-place, and after it's finished it places
47  - Application A writeback thread monitors the outgoing data queue for
51 We also demonstrate application-defined system calls, in the form of
57 .. code-block:: console