| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | NASA-1.3 | 56 …support, indemnity and/or liability obligations to one or more other Recipients of the Subject Sof…
|
| H A D | ErlPL-1.1 | 173 warranty, support, indemnity or liability obligations to one or more
177 support, indemnity or liability obligation is offered by You alone,
180 such Contributor as a result of warranty, support, indemnity or
|
| H A D | MPL-2.0 | 208 You may choose to offer, and to charge a fee for, warranty, support,
212 such warranty, support, indemnity, or liability obligation is offered by
214 liability incurred by such Contributor as a result of warranty, support,
|
| H A D | MPL-2.0-no-copyleft-exception | 95 …support, indemnity or liability obligations to one or more recipients of Covered Software. However…
|
| H A D | SISSL | 51 …support, indemnity or liability obligations to one or more recipients of Your version of the Code.…
|
| H A D | LPPL-1.3c | 103 requirements are made concerning any offers of support for the Work.
153 of the Work, provide any support, including (but not limited to)
156 they do provide such support for the Derived Work.
384 the community even when you can no longer maintain and support it
|
| H A D | LPPL-1.3a | 42 … Work is not restricted and no requirements are made concerning any offers of support for the Work.
58 …support, including (but not limited to) the reporting and handling of errors, to recipients of the…
164 … Work remains useful to the community even when you can no longer maintain and support it yourself.
|
| /openbmc/u-boot/doc/ |
| H A D | README.coccinelle | 125 if support for this is detected you will benefit from parmap parallelization.
212 DEBUG_FILE support is only supported when using coccinelle >= 1.2.
214 .cocciconfig support
|
| /openbmc/u-boot/board/gateworks/gw_ventana/ |
| H A D | README | 45 The Gateworks Ventana boards support booting from NAND or micro-SD depending
71 Linux with MTD support for the NAND on /dev/mtd0 you can program the SPL
172 For all boot mediums, raw mode is used. While support of more complex storage
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | bug-hunting.rst | 303 substantial support incorporated into ``klogd`` for processing protection
304 faults. In order to have full support for address resolution at least
347 seamless support for debugging protection faults which occur with
|
| /openbmc/qemu/docs/ |
| H A D | qdev-device-use.txt | 182 * -usbdevice braille doesn't support LEGACY-CHARDEV syntax. It always
269 that support it accept it.
281 machines support all -vga options.
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | devlink-port.rst | 216 with migration support, the user can migrate the VM with this VF from one HV to a
239 - Bind VF to VFIO driver with migration support::
407 Driver implementations are allowed to support both or either rate object types
|
| /openbmc/linux/Documentation/trace/coresight/ |
| H A D | coresight-etm4x-reference.rst | 677 There is currently no support in Perf for supplying modified binaries to the decoder, so this
728 ‘val’ determines level of Q element support enabled if
824 support for control of R or M profile infrastructure as part of a heterogeneous
|
| /openbmc/linux/tools/perf/ |
| H A D | design.txt | 115 on all CPUs that implement Performance Counters support under Linux,
131 * does not support performance counters. These counters measure various
464 - support for atomic64 types (and associated helper functions)
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-firmware-attributes | 30 All attribute types support the following values:
111 Enumeration attributes also support the following:
156 Devices support various authentication mechanisms which can be exposed
|
| /openbmc/openbmc/poky/documentation/ |
| H A D | README | 112 obvious reasons, we will only support building the Yocto Project
249 Pandoc. Sphinx has builtin support for substitutions
254 A Sphinx extension was implemented to support variable substitutions
|
| /openbmc/qemu/docs/devel/ |
| H A D | multi-thread-tcg.rst | 30 guest has had the required work done to support this safely
180 to support:
348 - Generic enough infrastructure to support all guest architectures
|
| /openbmc/qemu/qapi/ |
| H A D | machine-target.json | 156 # Some architectures may not support comparing CPU models. s390x
214 # Some architectures may not support baselining CPU models. s390x
292 # Some architectures may not support all expansion types. s390x
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | faq.rst | 273 How do I make the Yocto Project support my board?
283 Usually, if the board is not completely exotic, adding support in the
286 How do I make the Yocto Project support my package?
420 situation changes, the team will not support spaces in pathnames.
|
| /openbmc/u-boot/arch/x86/ |
| H A D | Kconfig | 85 bool "Intel MID platform support"
590 bool "Enable FSP framebuffer driver support"
628 via static tables in memory. Kernel SFI support is required to
642 provides a way for the operating system to support for symmetric
702 U-Boot can support up to 254 IRQ slot info in the PIRQ routing table
|
| /openbmc/linux/Documentation/networking/ |
| H A D | timestamping.rst | 117 require driver support and may not be available for all devices.
519 support HWTSTAMP_FILTER_PTP_V2_EVENT, then it should generally always upscale
579 A driver which supports hardware time stamping must support the
582 should also support SIOCGHWTSTAMP.
719 to each individual MAC driver for PHY timestamping support. This entails:
744 (case in which explicit MAC driver support is indeed needed), but the
755 any PHY even if it doesn't support timestamping. In Linux, they are
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | ipmi.rst | 46 support this, but it is unknown if it will work on every board. For
76 system doesn't support this option. This works on ATCA systems, the
121 ipmi_poweroff - Some systems support the ability to be turned off via
180 The "channel" here is generally zero, but some devices support more
480 If your IPMI interface does not support interrupts and is a KCS or
585 The I2C driver does not support non-blocking access or polling, so
803 does not support power cycling, it will always do the power off.
|
| /openbmc/linux/Documentation/infiniband/ |
| H A D | ipoib.rst | 53 and communication with peers that don't support connected mode. In
|
| /openbmc/linux/Documentation/driver-api/driver-model/ |
| H A D | binding.rst | 39 chance to verify that it really does support the hardware, and that
|
| /openbmc/linux/Documentation/i2c/ |
| H A D | dma-considerations.rst | 7 time of writing, only 10% of I2C bus master drivers have DMA support
|