Home
last modified time | relevance | path

Searched refs:looks (Results 1 – 25 of 39) sorted by relevance

12

/f-stack/freebsd/contrib/device-tree/src/arm/
H A Dam335x-osd335x-common.dtsi26 * Therefore, from a DEVICE_ID revision point of view, the silicon looks
28 * the HW OPP table, the silicon looks like it is Revision 1.0 (ie the
H A Dda850-lego-ev3.dts197 * The I2C bootloader looks for this magic value to either
/f-stack/dpdk/devtools/
H A Dgit-log-fixes.sh16 It looks for the word "fix" in the headline or a tag "Fixes" or "Reverts".
/f-stack/tools/libxo/doc/
H A Dhowto.rst207 Typically these developer looks for a "for" loop as an indication of
344 - The "{G:}" role looks for a translation of the format string.
345 - The "{g:}" modifier looks for a translation of the field.
346 - The "{p:}" modifier looks for a pluralized version of the field.
H A Dencoders.rst107 Be aware that since the CSV encoder looks for data instances, when
242 for `dlopen`(). libxo looks for a symbol called
H A Doptions.rst159 Consider the common situation where blue output looks unreadable on a
H A Dfield-roles.rst118 according to their own tastes, so assuming that "blue" looks nice is
/f-stack/freebsd/contrib/libsodium/m4/
H A Dax_check_gnu_make.m442 # something like this (note that GNU make always looks for GNUmakefile
/f-stack/freebsd/contrib/openzfs/config/
H A Dprogtest.m431 # contains only /bin. Note that ksh looks also at the FPATH variable,
H A Dlib-ld.m441 # contains only /bin. Note that ksh looks also at the FPATH variable,
/f-stack/dpdk/doc/guides/nics/
H A Dnfp.rst79 PF looks for a firmware file in this order:
110 available ports is firmware and hardware dependent, and the driver looks for a
/f-stack/freebsd/contrib/dev/ice/
H A DREADME115 The DDP package loads during device initialization. The driver looks for the
131 The DDP package loads during device initialization. The driver looks for
/f-stack/freebsd/contrib/device-tree/Bindings/spi/
H A Dspi-controller.yaml35 cs-gpios looks like this
/f-stack/freebsd/contrib/device-tree/Bindings/pinctrl/
H A Dfsl,imx-pinctrl.txt30 looks like <PIN_FUNC_ID CONFIG> in the example below.
/f-stack/freebsd/contrib/device-tree/Bindings/i3c/
H A Di3c.txt28 When undefined, the core looks at LVR (Legacy Virtual Register)
/f-stack/dpdk/doc/guides/faq/
H A Dfaq.rst21 When you stop and restart the test application, it looks to see if the pages are available in the `…
109 If you allocated 256B, you would get memory that looks like this:
/f-stack/freebsd/contrib/zlib/doc/
H A Dalgorithm.txt69 stream, and looks it up in the table. The table will tell if the next
95 looks like. You are correct that it's not a Huffman tree. It is simply a
/f-stack/dpdk/doc/guides/sample_app_ug/
H A Dskeleton.rst190 looks like the following:
H A Dipv4_multicast.rst37 it looks only at the IPv4 destination address for any given packet.
H A Dflow_filtering.rst289 looks like the following:
H A Dflow_classify.rst412 For the Basic Forwarding application the ``lcore_main`` function looks like the
/f-stack/dpdk/doc/guides/prog_guide/
H A Dmember_lib.rst323 The ``rte_member_lookup()`` function looks up a single key/element in the set-summary structure. It
339 The ``rte_member_lookup_multi()`` function looks up a single key/element in the
355 The ``rte_membership_lookup_multi_bulk()`` function looks up a bulk of keys/elements in the
/f-stack/freebsd/contrib/openzfs/cmd/zpool_influxdb/
H A DREADME.md30 visualization looks like:
/f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/perf/
H A Dperf.shlib535 # On illumos this looks like: ":sd3:sd4:sd1:sd2:"
/f-stack/dpdk/doc/guides/tools/
H A Dtestbbdev.rst320 In case where variable is a single value correct assignment looks like the

12