/openbmc/linux/drivers/scsi/mpt3sas/ |
H A D | Kconfig | 32 # DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND 60 MAX_PHYS_SEGMENTS in most kernels. However in SuSE kernels this 61 can be 256. However, it may decreased down to 16. Decreasing this 72 MAX_PHYS_SEGMENTS in most kernels. However in SuSE kernels this 73 can be 256. However, it may decreased down to 16. Decreasing this
|
/openbmc/linux/Documentation/powerpc/ |
H A D | pmu-ebb.rst | 34 events, however unless the target process enables EBBs (via mtspr(BESCR)) no 48 It is however safe to run 'perf' commands on a process which is using EBBs. The 94 However, due to the design of the perf_events API, enabling an event does not 102 this case the enable will be successful. However if there is already an event 109 It is possible to read() from an EBB event. However the results are 125 The EBB handler is just regular userspace code, however it must be written in
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | Net-SNMP | 21 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY… 31 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY… 51 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY… 61 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY… 71 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY… 85 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY… 97 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY… 107 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
|
H A D | Sleepycat | 32 INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 59 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 86 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
H A D | DOC | 3 …ell as copy and distribute modified versions of this software. You must, however, include this cop… 5 …stribute any of your source code that is built using DOC software. Note, however, that you may not… 9 … companies around the world provide commercial support for DOC software, however. DOC software is …
|
H A D | Catharon | 23 o We don't promise that this software works. However, we are 101 our work, you must acknowledge us. However, no fee need be paid 116 accept it. However, as the Catharon Packages are copyrighted
|
/openbmc/linux/Documentation/gpu/rfc/ |
H A D | xe.rst | 48 However, the force_probe mechanism existent in both drivers will allow only one 81 Xe primarily uses Firmware based scheduling (GuC FW). However, it will use 83 resolve syncobj and dma-buf implicit sync dependencies. However, drm_scheduler is 119 development of a common new drm_infrastructure. However, the Xe team needs to 151 However, there are more aspects around the rules for that and the usage of 181 in a next stage. However, this should not block the initial merge. 195 However, display code should not gate the acceptance of Xe in upstream. Xe
|
/openbmc/linux/Documentation/mm/ |
H A D | hugetlbfs_reserv.rst | 18 kernel, the code has evolved over time. However, the basic idea was to 139 always the value (to - from). However, for shared mappings it is possible that 153 However, within those routines the code is simply checking to ensure there 204 However, in every case the avoid_reserve argument overrides the use of 243 in the reserve map already existed so no change is made. However, if there 322 However, if reserves are associated with the subpool a return value less 407 return value of region_chg(). However, in the case of shared mappings it is 437 indicate that there is a reservation for the page. However, the subpool and 462 in the section "Reservation Map Modifications". However, they do take into 524 However, there are several instances where errors are encountered after a huge [all …]
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | disk-space.rst | 22 final disk usage of 22 Gbytes instead of &MIN_DISK_SPACE; Gbytes. However, 31 disk space. However, only the most recent ones are likely to be reused. 47 exploring a set of build configurations. However, this command
|
/openbmc/docs/designs/management-console/ |
H A D | Authorities_List_Management.md | 16 1. It only allows replacing a single Authority object in dbus; however, Google's 20 certs; however, Google's trust bundle file contains multiple PEM encoded 91 existing codes. However, trust bundle isn't in BMCWeb, neither in Redfish
|
/openbmc/u-boot/include/configs/ |
H A D | integrator-common.h | 37 * However it may be needed if Integrator/CP switch S2-1 47 * However, the default U-Boot code also performs the initialization. 57 * However, the default U-Boot code performs the relocation check,
|
/openbmc/linux/drivers/misc/echo/ |
H A D | echo.h | 41 well. However, it only works well for signals of constant amplitude. It works 48 FAP, etc. Some perform significantly better than NLMS. However, factors such 53 the NLMS algorithm works very well. However, speech has more low frequency than 96 assess whether that signal contains a strong far end component. However, by the
|
/openbmc/linux/arch/arm64/boot/dts/qcom/ |
H A D | msm8916-samsung-e7.dts | 14 * However, it is possible to use this device tree by compiling an ARM32 kernel 16 * to the other MSM8916 device trees. However, it is actually used through
|
H A D | msm8916-samsung-e5.dts | 14 * However, it is possible to use this device tree by compiling an ARM32 kernel 16 * to the other MSM8916 device trees. However, it is actually used through
|
/openbmc/linux/arch/alpha/include/uapi/asm/ |
H A D | types.h | 9 * not a major issue. However, for interoperability, libraries still 18 * However, some user programs are fine with this. They can
|
/openbmc/qemu/include/exec/ |
H A D | target_long.h | 14 * Usually this should only be included via cpu-defs.h however for 16 * object we can include directly. However the build-system must
|
/openbmc/linux/drivers/hwmon/occ/ |
H A D | Kconfig | 12 On-Chip Controller (OCC) on a POWER8 processor. However, this driver 26 On-Chip Controller (OCC) on a POWER9 processor. However, this driver
|
/openbmc/linux/tools/memory-model/Documentation/ |
H A D | ordering.txt | 115 synchronize_srcu() and so on. However, these primitives have orders 184 the write to "y". However, you are usually better off using a release 216 "x". However, you are usually better off using an acquire load, as described 432 However, control dependencies are easily destroyed by compiler 452 However, if a group of CPUs apply these operations to a single variable, 462 a number of destructive optimizations. However, they provide no 470 a number of destructive optimizations. However, they provide no 483 However, many CPUs will happily reorder these operations with 554 fastpaths. However, the price is great care and continual attention
|
/openbmc/qemu/docs/devel/ |
H A D | lockcnt.rst | 15 by stashing away its ``next`` pointer. However, ``ioh->fd_write`` could 31 If however this loop must also be reentrant, i.e. it is possible that 138 However, critical sections are easy to forget since you have to do 157 However, these are usually not a problem if any of the following 170 frequent and can happen on a fast path; however: 1) it is almost never
|
/openbmc/linux/arch/powerpc/include/uapi/asm/ |
H A D | types.h | 6 * not a major issue. However, for interoperability, libraries still 22 * However, some user programs are fine with this. They can
|
/openbmc/linux/include/linux/ |
H A D | rculist_nulls.h | 29 * hlist_nulls_del_rcu(), running on this same list. However, it is 70 * However, it is perfectly legal to run concurrently with 93 * However, it is perfectly legal to run concurrently with 124 * However, it is perfectly legal to run concurrently with
|
/openbmc/u-boot/drivers/usb/dwc3/ |
H A D | io.h | 31 * However, the offsets are given starting from xHCI address space. in dwc3_readl() 45 * However, the offsets are given starting from xHCI address space. in dwc3_writel()
|
/openbmc/linux/Documentation/networking/device_drivers/can/ |
H A D | can327.rst | 35 As such, can327 is a best effort driver. However, this is more than 210 However, immediately after sending a frame, the ELM327 will be in 238 However, they do send ACKs while waiting for a reply immediately 276 However there is an exception: With a separate flag, it may set the 293 helpful here, however SocketCAN does not currently provide a facility
|
/openbmc/linux/Documentation/ |
H A D | atomic_t.txt | 196 later accesses against the RMW op and all accesses preceding it. However, 218 However the atomic_fetch_add() might be implemented more efficiently. 321 operations -- those in the Arithmetic and Bitwise classes and xchg(). However 326 indefinitely. However, this is not evident on LL/SC architectures, because 356 However, even the forward branch from the failed compare can cause the LL/SC
|
/openbmc/openbmc/poky/documentation/migration-guides/ |
H A D | migration-general.rst | 37 that everything works for the new release. However, this is not the 44 them much more manageable. However, sometimes it is not practical to 53 releases. However, if the append file is specific to a
|