| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/yajl/yajl/ |
| H A D | CVE-2022-24795.patch | 40 need = buf->len;
42 - while (want >= (need - buf->used)) need <<= 1;
47 + while (want >= (need - buf->used)) {
48 + if (need >= (size_t)((size_t)(-1)<<1)>>1) {
49 + /* need would overflow. */
52 + need <<= 1;
55 if (need != buf->len) {
56 buf->data = (unsigned char *) YA_REALLOC(buf->alloc, buf->data, need);
|
| /openbmc/qemu/target/openrisc/ |
| H A D | mmu.c | 39 target_ulong addr, int need, bool super) in get_phys_mmu() argument
50 not match, zap the one we don't need. */ in get_phys_mmu()
52 if (need & PAGE_EXEC) { in get_phys_mmu()
82 "MMU lookup: need %d match %d valid %d right %d -> %s\n", in get_phys_mmu()
83 need, match, valid, right, (need & right) ? "OK" : "FAIL"); in get_phys_mmu()
86 if (likely(need & right)) { in get_phys_mmu()
91 if (need & valid) { in get_phys_mmu()
92 return need & PAGE_EXEC ? EXCP_IPF : EXCP_DPF; in get_phys_mmu()
94 return need & PAGE_EXEC ? EXCP_ITLBMISS : EXCP_DTLBMISS; in get_phys_mmu()
123 int need = (access_type == MMU_INST_FETCH ? PAGE_EXEC in openrisc_cpu_tlb_fill() local
[all …]
|
| /openbmc/qemu/docs/devel/ |
| H A D | block-coroutine-wrapper.rst | 7 coroutine_fn specifier. Still, sometimes we need to call them from
8 non-coroutine context; for this we need to start a coroutine, run the
10 BDRV_POLL_WHILE() loop. To run a coroutine we need a function with one
24 ``bdrv_co_foo(<some args>)`` and need a non-coroutine interface for it,
28 1. You need ``bdrv_foo`` declaration somewhere (for example, in
36 2. You need to feed this declaration to block-coroutine-wrapper script.
|
| H A D | build-environment.rst | 37 You first need to enable `Sources List <https://wiki.debian.org/SourcesList>`_.
47 You first need to install `Homebrew <https://brew.sh/>`_. Then, use it to
57 You first need to install `MSYS2 <https://www.msys2.org/>`_.
74 Note: Dependencies need to be installed again if you use a different MSYS2
79 # update MSYS2 itself, you need to reopen your shell at the end.
112 Meson detects x86_64 processes emulated, so you need to manually set the cpu,
|
| H A D | multi-thread-tcg.rst | 80 We need to protect the entire code generation cycle including any post
83 execution path that comes to the main run loop will need to hold a
84 mutex for code generation. This also includes times when we need flush
86 per-vCPU basis won't need locking unless other vCPUs will need to
127 book-keeping structures that need to be safely cleared.
130 now invalid blocks need the jump patches reversing so they will return
133 There are a number of look-up caches that need to be properly updated
188 we need to ensure it is done in a safe way so no inconsistent state is
198 - cross vCPU TLB flush may need other vCPU brought to halt
199 - change may need to be visible to the calling vCPU immediately
[all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/clock/ |
| H A D | rockchip,rk3399-dmc.txt | 4 - rockchip,cru: this driver should access cru regs, so need get cru here
5 - rockchip,pmucru: this driver should access pmucru regs, so need get pmucru here
6 - rockchip,pmugrf: this driver should access pmugrf regs, so need get pmugrf here
7 - rockchip,pmusgrf: this driver should access pmusgrf regs, so need get pmusgrf here
8 - rockchip,cic: this driver should access cic regs, so need get cic here
|
| /openbmc/libbej/src/ |
| H A D | bej_common.c | 29 // Only need to encode 0x00 or 0xFF in bejIntLengthOfValue()
49 // If the value is positive and encoded MSBbit is 1 we need to add 0x00 to in bejIntLengthOfValue()
56 // If the value is negative and encoded MSBbit is 0 we need to add 0xFF to in bejIntLengthOfValue()
71 // Even if the value is 0, we need a byte for that. in bejNnintEncodingSizeOfUInt()
75 // Need 1 byte to add the nnint length. in bejNnintEncodingSizeOfUInt()
81 // From the size of the encoded value, we need 1 byte for the length field. in bejNnintLengthFieldOfUInt()
|
| /openbmc/openbmc-test-automation/docs/ |
| H A D | redfish_request_via_mTLS.md | 44 - Original robot code of redfish request doesn’t need to modify. It will send
59 purposes. Therefore, some test cases need to write a new one to match it for
61 username) Some cases don’t need to be tested because the purpose of them are
69 not need to use mTLS to authenticate login and logout. It can be replaced as
77 don't need to create a session first. Therefore, there is no need to test
|
| /openbmc/u-boot/drivers/mtd/ubi/ |
| H A D | misc.c | 95 int need = ubi->beb_rsvd_level - ubi->beb_rsvd_pebs; in ubi_update_reserved() local
97 if (need <= 0 || ubi->avail_pebs == 0) in ubi_update_reserved()
100 need = min_t(int, need, ubi->avail_pebs); in ubi_update_reserved()
101 ubi->avail_pebs -= need; in ubi_update_reserved()
102 ubi->rsvd_pebs += need; in ubi_update_reserved()
103 ubi->beb_rsvd_pebs += need; in ubi_update_reserved()
104 ubi_msg(ubi, "reserved more %d PEBs for bad PEB handling", need); in ubi_update_reserved()
|
| /openbmc/u-boot/drivers/serial/ |
| H A D | Kconfig | 32 In various cases, we need to specify which of the UART devices that
191 You will need to provide parameters to make this work. The driver will
198 You will need to provide parameters to make this work. The driver will
206 You will need to provide parameters to make this work. The
215 You will need to provide parameters to make this work. The
223 will need to provide parameters to make this work. The driver will
231 will need to provide parameters to make this work. The driver will
238 will need to provide parameters to make this work. The driver will
254 will need to provide parameters to make this work. The driver will
262 will need to provide parameters to make this work. The driver will
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-prctl/ |
| H A D | 0001-support-cross-complication.patch | 19 # - Need gcc
20 # - Need C headers
21 # - Need libcap headers
39 - sys.stderr.write("You need to install gcc to build this module\n")
45 - sys.stderr.write("You need to install libc development headers to build this module\n")
51 - sys.stderr.write("You need to install libcap development headers to build this module\n")
|
| /openbmc/u-boot/doc/ |
| H A D | README.nios2 | 13 To add a new board/configuration (eg, mysystem) to u-boot, you will need
32 You will need to add additional properties to the dts. Please find an
41 2. If you use SPI/EPCS or I2C, you will need to add aliases to number
47 Next, you will need a default config file. You may start with
55 You will need to change the names of board header file and device tree,
86 You will need to change the environment variables location and setting,
|
| /openbmc/openbmc/poky/documentation/toaster-manual/ |
| H A D | start.rst | 9 This chapter describes how you need to prepare your system in order to
15 Before you can use Toaster, you need to first set up your build system
19 also need to do an additional install of pip3. ::
37 You need to install the packages that Toaster requires. Use this
49 If you need to remove something, the following works::
|
| /openbmc/docs/designs/oem/ibm/ |
| H A D | system-power-mode.md | 12 the system power mode and idle power save modes. We need the ability to set and
21 an Active state. Anytime the OCC state changes to active, the BMC will need to
23 need to send the commands if the user changes the mode or idle power save
34 runtime, the BMC will need to send the mode and the idle power saver settings to
57 Defaults will need to be configurable by the system owner (via JSON file)
69 Code will need to trigger off of OCC state changes. The kernel currently sends a
102 Documentation impact - need to document new parameters Performance impact -
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-4.2.rst | 83 to include such checksums. So, in case you need to add the list of checksums
126 recipes or bbappends, you will need to switch to using :term:`PACKAGE_PREPROCESS_FUNCS`
165 workspace layer enabled and you wish to retain it, you will need to manually
169 need it).
179 available on the build host. Most use cases with runqemu only need
185 However, if you need the qemu machine to be reachable from the
204 if triggered. If you prefer to avoid this you will need to adjust the value
235 image symlink creation, you also now need to set :term:`IMAGE_NAME` to still have
244 code reading this from ``/etc/os-release`` it may need to be updated.
247 signing. If you do not need this and wish to reclaim some space/avoid the dependency
[all …]
|
| H A D | migration-3.4.rst | 128 - ``meta``: no longer useful. Recipes that need to skip installing
168 configuration files) they will need to be updated.
182 portion of the eSDK then you will now need to set this variable.
189 bbappends for the perl recipe then these may need extending.
196 in its own ``xwayland`` recipe. If you need Xwayland in your image
197 then you may now need to add it explicitly.
200 if by chance you still need rpm package building functionality in
214 missing explicit dependencies that need to be added.
220 as a result, you will need to fix the installation/packaging issues.
225 configuration). If in your CI system you need to have the original
[all …]
|
| /openbmc/qemu/tests/functional/qemu_test/ |
| H A D | tuxruntest.py | 28 # We need zstd for all the tuxrun tests
33 # reasonable defaults but we sometimes need to tweak the
48 # Occasionally we need extra devices to hook things up
86 # Sometimes we need extra devices attached
93 # Some machines need an explicit DTB
126 Common path for LKFT tests. Unless we need to do something
|
| /openbmc/openbmc/poky/bitbake/lib/bb/tests/runqueue-tests/classes/ |
| H A D | base.bbclass | 154 # Return - False - We need this dependency
169 # We only need to trigger populate_lic through direct dependencies
173 # We only need to trigger packagedata through direct dependencies
174 # but need to preserve packagedata on packagedata links
187 # do_package_write_* and do_package doesn't need do_package
190 # do_package_write_* need do_populate_sysroot as they're mainly postinstall dependencies
193 # do_package/packagedata/package_qa don't need do_populate_sysroot
207 # Native/Cross populate_sysroot need their dependencies
210 # Target populate_sysroot depended on by cross tools need to be installed
217 # Target populate_sysroot need their dependencies
|
| /openbmc/docs/designs/ |
| H A D | error-log-handling-for-phal.md | 18 initialization, any software/hardware error returned by the pHAL layer need to
91 status need to be returned to the caller so that caller can create PEL on
96 libpdbg library is used for hardware access, any hardware access errors need to
102 need to be created in the [message registry][8].
113 Inventory strings for the targets to Callout/Guard/Deconfig need to be added to
116 Applications need to register callback methods in libekb library to get back the
123 Applications need to register callback methods in libipl library to get back the
130 Applications need to register callback methods to get the debug traces from
|
| H A D | vpd-collection.md | 18 - Some of the VPD information such as FRU part number, serial number need to be
23 application that controls voltage regulators might need to set different
56 specification does define it, but will need to use the ECC for IBM's
71 BMC applications need to be able to read VPD for FRUs to determine, for ex.,
74 Some of the VPD will need to be exchanged with the host.
76 Manufacturing and Service engineers need the ability to view and program the
97 - Applications on the BMC need to have the ability to query any given VPD
100 - Applications also need to have the ability to update the VPD contents in a
239 - We do not need the full spectrum of functions offered by the entity manager,
255 - Applications that need to read VPD keywords will be impacted in the sense that
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-ninja/ |
| H A D | no-scikit-build.patch | 1 We don't need to build ninja so there's no need to use scikit-build,
2 as we just need the python module with it's one ninja() function.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/gcc/ |
| H A D | libgcc-initial.inc | 4 # We need a libgcc to build glibc. Tranditionally we therefore built
19 # libgcc-initial is tricky as we need to imitate the non-threaded and
26 # handler" capable libgcc (libgcc_eh.a). Since we know glibc doesn't need
42 # We really only want this built by things that need it, not any recrdeptask
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | new-machine.rst | 25 To add a new machine, you need to add a new machine configuration file
43 You might also need these variables:
59 machine. You need to either create a new kernel recipe for this machine,
65 apply for setting up a :term:`SRC_URI`. Thus, you need to specify any
66 necessary patches and set :term:`S` to point at the source code. You need to
100 customization is necessary, you need to create a ``machconfig`` file in
|
| H A D | new-recipe.rst | 41 that is similar in function to the recipe you need.
74 To run the tool, you just need to be in your :term:`Build Directory` and
177 Consequently, you need to be sure you locate your new recipe inside
183 - *Naming Your Recipe:* When you name your recipe, you need to follow
208 BitBake to process your recipe. All you need to provide is the
318 SCM URLs), you need to provide the ``sha256`` checksum for each URL. For these
379 Some users are behind firewalls and need to fetch code through a proxy.
404 then you do not need to set :term:`S`. However, if :term:`SRC_URI` specifies to
409 files, you need to be sure that the directory pointed to by ``${S}``
472 package-specific. All variables that are package-specific need to have
[all …]
|
| H A D | speeding-up-build.rst | 50 the risk of data loss but decreases the need to write to the disk,
81 that you might not need.
83 - Exclude debug symbols and other debug information: If you do not need
101 - Some recipes need static libraries in order to work correctly
107 the static libraries. If so, you might need to exclude them as
|