| /Zephyr-latest/tests/modules/thrift/ThriftTest/src/ |
| D | server.hpp | 34 void testString(string &out, const string &thing) override in testString() argument
36 printf("testString(\"%s\")\n", thing.c_str()); in testString()
37 out = thing; in testString()
40 bool testBool(const bool thing) override in testBool() argument
42 printf("testBool(%s)\n", thing ? "true" : "false"); in testBool()
43 return thing; in testBool()
46 int8_t testByte(const int8_t thing) override in testByte() argument
48 printf("testByte(%d)\n", (int)thing); in testByte()
49 return thing; in testByte()
52 int32_t testI32(const int32_t thing) override in testI32() argument
[all …]
|
| /Zephyr-latest/include/zephyr/arch/x86/ |
| D | pagetables.ld | 22 /* Top-level paging structure is the last thing in this section */
|
| /Zephyr-latest/doc/build/dts/ |
| D | zephyr-user-node.rst | 75 * Same thing as:
86 * Same thing as:
|
| D | api-usage.rst | 362 /* This is same thing as DT_INST(0, my_driver_compat): */
366 * This is the same thing as
|
| D | howtos.rst | 138 If you're having trouble, see :ref:`dt-trouble`. The first thing to check is
162 successfully, the last thing to check is if the device is ready, like this:
|
| D | troubleshooting.rst | 52 (Recall that a missing ``status`` property means the same thing as ``status
|
| /Zephyr-latest/boards/common/ |
| D | openocd-nrf5.board.cmake | 27 # We can do the right thing for supported subfamilies using a generic
|
| /Zephyr-latest/samples/net/cloud/aws_iot_mqtt/ |
| D | README.rst | 38 Register a *thing* in AWS IoT Core and download the certificate and private key.
44 Core region, thing, and device advisor configuration:
49 - :kconfig:option:`CONFIG_AWS_THING_NAME`: The name of the thing created in AWS IoT Core. Associated
|
| /Zephyr-latest/boards/sparkfun/thing_plus/ |
| D | sparkfun_thing_plus_nrf9160_common.dtsi | 12 compatible = "sparkfun,thing-plus-nrf9160";
|
| /Zephyr-latest/samples/ |
| D | sample_definition_and_criteria.rst | 34 :zephyr_file:`tests/` folder. In a sample, the only thing you test is
|
| /Zephyr-latest/doc/develop/west/ |
| D | extensions.rst | 157 (if not given, the ``class`` value defaults to the same thing as ``name``).
228 same thing in the manifest's ``self`` section, like this:
|
| D | config.rst | 25 way to say the same thing is that ``manifest.path`` is ``zephyr`` in this file.
|
| D | workspaces.rst | 227 Another way to do the same thing is to copy/paste :file:`zephyr/west.yml`
|
| D | manifest.rst | 1327 want to maintain the whole thing using west. You don't want to modify any of
|
| /Zephyr-latest/subsys/net/l2/ethernet/gptp/ |
| D | Kconfig | 118 The port concept is the same thing as network interface.
|
| /Zephyr-latest/subsys/net/lib/ptp/ |
| D | Kconfig | 86 The port concept is the same thing as network interface.
|
| /Zephyr-latest/scripts/dts/python-devicetree/src/devicetree/ |
| D | dtlib.py | 1924 for thing in things:
1925 if isinstance(thing, Node):
1927 elif isinstance(thing, Property):
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_MMU.txt | 58 one thing the hardware can already do), and quite fast (only one
|
| /Zephyr-latest/doc/project/ |
| D | release_process.rst | 82 feature, the best thing to do is to wait for the next development cycle. (An
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 732 then the first thing to do is to add a configuration dependency between them.
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | syscalls.rst | 74 * :c:macro:`__syscall` must be the first thing in the prototype.
|
| /Zephyr-latest/cmake/modules/ |
| D | extensions.cmake | 1277 # files must instead define their own output sections to achieve the same thing:
1287 # the second with SECTIONS, the two examples do the same thing from a user
|
