| /openbmc/qemu/docs/devel/migration/ |
| H A D | compatibility.rst | 7 When we do migration, we have two QEMU processes: the source and the
18 Let's start with a practical example, we start with:
36 I am going to list the number of combinations that we can have. Let's
50 This are the easiest ones, we will not talk more about them in this
53 Now we start with the more interesting cases. Consider the case where
54 we have the same QEMU version in both sides (qemu-5.2) but we are using
72 because we have the limitation than qemu-5.1 doesn't know pc-5.2. So
78 when we are developing 5.2 we need to take care about not to break
79 migration to qemu-5.1. Notice that we can't make updates to
86 than we are able to receive migrations from qemu-5.1. The problem is
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools/build/ |
| H A D | 0001-Riscv-Add-risc-v-Android-config-header.patch | 63 + * Do we have pthread_setname_np()?
66 + * the same name but different parameters, so we can't use that here.)
71 + * Do we have the futex syscall?
85 + * where we can write to /proc/<pid>/oom_adj to modify the out-of-memory
135 + * Define this if we have localtime_r().
140 + * Define this if we have gethostbyname_r().
145 + * Define this if we have ioctl().
150 + * Define this if we want to use WinSock.
160 + * Define this if we have linux style epoll()
167 + * HAVE_ENDIAN_H -- have endian.h header we can include.
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-multimedia/libid3tag/libid3tag/ |
| H A D | 10_utf16.patch | 25 + * - Try and parse as much as we can and
26 + * - return an error if we're called again when we
27 + * already tried to parse everything we can.
28 + * - tell that we parsed it, which is what we do here.
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/ |
| H A D | 0028-corstone1000-boot-index-from-active.patch | 7 all the boot tries and status, so, every time we get here
8 we know that the we are booting from the active index.
30 + * all the boot tries and status, so, every time we get here
31 + * we know that the we are booting from the active index
|
| /openbmc/u-boot/test/overlay/ |
| H A D | test-fdt-overlay.dts | 11 /* Test that we can change an int by another */
20 /* Test that we can replace a string by a longer one */
29 /* Test that we add a new property */
38 /* Test that we add a new node (by phandle) */
49 /* Test that we add a new node (by path) */
|
| /openbmc/u-boot/board/freescale/mpc8569mds/ |
| H A D | README | 39 defined in board/freescale/common/sys_eeprom.c. we must set all 8 MAC
41 we first get the board. The commands are as follows:
44 designer, we can set whatever we want */
46 designer, we can set whatever we want */
61 has been set but we want to update it, we can use the following commands:
69 MPC8569 doesn't have ROM in QE, so we must upload the microcode(ucode) to QE's
|
| /openbmc/qemu/linux-user/s390x/ |
| H A D | vdso.ld | 19 * QEMU handles syscall restart internally, so we don't
40 * when we relocate the binary. We want them to be initially
41 * writable for the relocation; we'll force them read-only after.
48 * But since we manipulated the segment layout,
49 * we have to put these sections somewhere.
|
| /openbmc/u-boot/doc/ |
| H A D | README.hwconfig | 8 via the `hwconfig' environment variable. Later we could write
20 2. Since we don't implement a hwconfig command, i.e. we're working
36 internal API and then we can continue improving the user
38 command with bells and whistles. Or not adding, if we feel
46 enabling HW feature X we may need to disable Y, and turn Z
|
| H A D | README.davinci.nand_spl | 1 With this approach, we don't need the UBL any more on DaVinci boards.
8 we need a command, which switches between this two read/write
9 functions, so we can write the UBL header and the spl
26 On the cam_enc_4xx board we have a NAND flash with blocksize = 0x20000 and
46 In the first "page" of the image, we have the UBL Header, needed for
62 * so we can define, how many UBL Headers
63 * we write before the real spl code
89 For the AIT board, we have:
93 So we need to copy the spl code to block 5 page 0
138 - If we make the nand read/write functions in the RBL equal to
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-support/apr/apr-util/ |
| H A D | configfix.patch | 34 - # If the LA_FILE exists where we think it should be, use it. If we're
36 - # (the LA_FILE may not have been installed). If we're building ourselves,
37 - # we'll assume that at some point the .la file be created.
42 - # Since the user is specifying they are linking with libtool, we
|
| /openbmc/qemu/tests/tsan/ |
| H A D | suppressions.tsan | 2 # The goal would be to have here only items we do not
6 # Since the recursive lock is intentional, we choose to ignore it.
11 # we choose to ignore it.
|
| /openbmc/qemu/linux-user/x86_64/ |
| H A D | vdso.ld | 41 * when we relocate the binary. We want them to be initially
42 * writable for the relocation; we'll force them read-only after.
50 * But since we manipulated the segment layout,
51 * we have to put these sections somewhere.
|
| /openbmc/qemu/linux-user/arm/ |
| H A D | vdso.ld | 35 * when we relocate the binary. We want them to be initially
36 * writable for the relocation; we'll force them read-only after.
43 * But since we manipulated the segment layout,
44 * we have to put these sections somewhere.
|
| /openbmc/qemu/linux-user/ppc/ |
| H A D | vdso-32.ld | 38 * when we relocate the binary. We want them to be initially
39 * writable for the relocation; we'll force them read-only after.
47 * But since we manipulated the segment layout,
48 * we have to put these sections somewhere.
|
| H A D | vdso-64.ld | 36 * when we relocate the binary. We want them to be initially
37 * writable for the relocation; we'll force them read-only after.
45 * But since we manipulated the segment layout,
46 * we have to put these sections somewhere.
|
| /openbmc/qemu/linux-user/i386/ |
| H A D | vdso.ld | 44 * when we relocate the binary. We want them to be initially
45 * writable for the relocation; we'll force them read-only after.
53 * But since we manipulated the segment layout,
54 * we have to put these sections somewhere.
|
| /openbmc/openbmc/poky/meta/recipes-support/db/db/ |
| H A D | sequence-type.patch | 6 This then breaks the overly complicated type check but as we know that int64_t
7 exists and works, we can just delete that.
21 - # Test to see if we can declare variables of the appropriate size
22 - # and format them. If we're cross-compiling, all we get is a link
|
| /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
12 non-coroutine interface, we should define a structure to pack the
18 so we have a script to generate them.
23 Assume we have defined the ``coroutine_fn`` function
|
| H A D | s390-dasd-ipl.rst | 34 the real operating system is loaded into memory and we are ready to hand
49 should contain the needed flags for the operating system we have loaded. The
50 psw's instruction address will point to the location in memory where we want
68 In theory we should merely have to do the following to IPL/boot a guest
79 When we start a channel program we pass the channel subsystem parameters via an
95 it from the disk. So we need to be able to handle this case.
100 Since we are forced to live with prefetch we cannot use the very simple IPL
101 procedure we defined in the preceding section. So we compensate by doing the
112 to read the very next record which will be IPL2. But since we are not reading
113 both IPL1 and IPL2 as part of the same channel program we must manually set
[all …]
|
| /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
6 # that to build libgcc-initial which is used to build glibc which we can
16 # Once gcc-cross is libc independent, we can use it to build both
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
27 # any exception handler, we can safely symlink to libgcc.a.
|
| /openbmc/openbmc/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/ |
| H A D | 0001-libc-compat.h-fix-some-issues-arising-from-in6.h.patch | 24 +#ifndef __KERNEL__ /* we're used from userspace */
59 /* Linux headers included first, and we must define everything
60 - * we need. The expectation is that glibc will check the
61 + * we need. The expectation is that libc will check the
75 * or we are being included in the kernel, then define everything
76 * that we need. Check for previous __UAPI_* definitions to give
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/freeradius/files/ |
| H A D | 0004-Fix-libtool-detection.patch | 26 @@ -319,6 +319,42 @@ dnl # See if we have Git.
39 +dnl exactly which version of libltdl is present in the system, so we
40 +dnl just assume that it's a working version as long as we have the
44 +dnl only implemented in libtool 2.x, and refine as we go if we have
48 +dnl libltdl.so for runtime, but no headers, and we want to bail out as
|
| /openbmc/qemu/linux-user/loongarch64/ |
| H A D | vdso.ld | 41 * when we relocate the binary. We want them to be initially
42 * writable for the relocation; we'll force them read-only after.
49 * But since we manipulated the segment layout,
50 * we have to put these sections somewhere.
|
| /openbmc/qemu/linux-user/riscv/ |
| H A D | vdso.ld | 42 * when we relocate the binary. We want them to be initially
43 * writable for the relocation; we'll force them read-only after.
50 * But since we manipulated the segment layout,
51 * we have to put these sections somewhere.
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | ANTLR-PD | 14 we do ask that credit is given to us for developing
15 ANTLR. By "credit", we mean that if you use ANTLR or
21 you developed it using ANTLR. In addition, we ask that the
23 guidelines are kept, we expect to continue enhancing this
|