Home
last modified time | relevance | path

Searched refs:We (Results 1 – 25 of 1626) sorted by relevance

12345678910>>...66

/openbmc/qemu/target/loongarch/
H A DREADME9 …We can get the latest loongarch documents at https://github.com/loongson/LoongArch-Documentation/t…
18 …We already support Linux user emulation. We can use LoongArch cross-tools to build LoongArch execu…
19 and We can also use qemu-loongarch64 to run LoongArch executables.
52 We can get the latest LoongArch documents or LoongArch tools at https://github.com/loongson/
/openbmc/openbmc/poky/meta/recipes-devtools/gcc/
H A Dlibgcc-initial.inc4 # We need a libgcc to build glibc. Tranditionally we therefore built
9 # We were able to drop the glibc dependency from gcc-cross, with two tweaks:
13 # the headers structure has support for it. We can do this with a simple
20 # non-shared case. We can do that by hacking the threading mode back to
22 # libgcc-intial build. We have to create the dummy limits.h to avoid
42 # We really only want this built by things that need it, not any recrdeptask
/openbmc/linux/arch/arm/boot/compressed/
H A Dhead-sharpsl.S58 bne .SHARPEND @ We have no w100 - Poodle
64 blo .SHARPEND @ We have a PXA250 - Corgi
70 beq .SHARPEND @ We have Shepherd
81 beq .SHARPEND @ We have Spitz
90 beq .SHARPEND @ We have Borzoi
94 b .SHARPEND @ We have Borzoi
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/pptp-linux/pptp-linux/
H A Doptions.pptp7 # We don't need the tunnel server to authenticate itself
18 # We want MPPE
26 # We want a sane mtu/mru
/openbmc/openbmc/poky/meta/recipes-devtools/binutils/binutils/
H A D0004-Point-scripts-location-to-libdir.patch19 # We put the scripts in the directory $(scriptdir)/ldscripts.
20 # We can't put the scripts in $(datadir) because the SEARCH_DIR
32 # We put the scripts in the directory $(scriptdir)/ldscripts.
33 # We can't put the scripts in $(datadir) because the SEARCH_DIR
H A D0010-sync-with-OE-libtool-changes.patch11 We don't want to add RPATHS which match default linker
38 + # We only want to hardcode in an rpath if it isn't in the
57 + # We only want to hardcode in an rpath if it isn't in the
76 + # We only want to hardcode in an rpath if it isn't in the
/openbmc/linux/Documentation/mm/
H A Dovercommit-accounting.rst73 * We account mmap memory mappings
74 * We account mprotect changes in commit
75 * We account mremap changes in size
76 * We account brk
77 * We account munmap
78 * We report the commit status in /proc
/openbmc/openbmc/meta-arm/meta-arm-systemready/recipes-test/arm-systemready-acs/arm-systemready-scripts/
H A D0002-check-sr-results-Device-tree-improvements.patch24 # We run dtc and dt-validate to produce the log when needed.
25 # We add markers to the log, which will be ignored by dt-parser.py.
26 # We return a Stats object.
33 # We use the compatible strings extracted from Linux bindings to filter out
/openbmc/openbmc/poky/meta/recipes-devtools/libtool/libtool/
H A D0002-ltmain.in-Don-t-encode-RATHS-which-match-default-lin.patch7 We don't want to add RPATHS which match default linker search paths, they're
31 + # We only want to hardcode in an rpath if it isn't in the
50 + # We only want to hardcode in an rpath if it isn't in the
69 + # We only want to hardcode in an rpath if it isn't in the
/openbmc/linux/Documentation/admin-guide/LSM/
H A Dtomoyo.rst57 We believe that inode based security and name based security are complementary
59 multiple LSM modules at the same time. We feel sorry that you have to give up
62 We hope that LSM becomes stackable in future. Meanwhile, you can use non-LSM
64 LSM version of TOMOYO is a subset of non-LSM version of TOMOYO. We are planning
/openbmc/qemu/docs/config/
H A Dq35-virtio-graphical.cfg49 # We use the q35 machine type and enable KVM acceleration
69 # We create eight PCI Express Root Ports, and we plug them
135 # We use virtio-scsi here so that we can (hot)plug a large
140 # We also create an optical disk, mostly for installation
178 # We use virtio-net for improved performance over emulated
196 # We add a virtualization-friendly USB 3.0 controller and
214 # We plug the QXL video card directly into the PCI Express
H A Dq35-virtio-serial.cfg43 # We use '-display none' to prevent QEMU from creating a
54 # We use the q35 machine type and enable KVM acceleration
74 # We create eight PCI Express Root Ports, and we plug them
140 # We use virtio-scsi here so that we can (hot)plug a large
145 # We also create an optical disk, mostly for installation
183 # We use virtio-net for improved performance over emulated
H A Dmach-virt-graphical.cfg45 # We use the virt machine type and enable KVM acceleration
118 # We create eight PCI Express Root Ports, and we plug them
184 # We use virtio-scsi here so that we can (hot)plug a large
189 # We also create an optical disk, mostly for installation
227 # We use virtio-net for improved performance over emulated
245 # We add a virtualization-friendly USB 3.0 controller and
266 # We use virtio-gpu because the legacy VGA framebuffer is
H A Dmach-virt-serial.cfg40 # We use '-display none' to prevent QEMU from creating a
51 # We use the virt machine type and enable KVM acceleration
124 # We create eight PCI Express Root Ports, and we plug them
190 # We use virtio-scsi here so that we can (hot)plug a large
195 # We also create an optical disk, mostly for installation
233 # We use virtio-net for improved performance over emulated
/openbmc/docs/designs/
H A Dcertificate-revocation-list.md55 We propose to introduce a new interface `CRL` in
59 interface to be `CRLString`, which contains the PEM encoded CRL. We can add more
64 We propose to add a new type of certificate-manager (CRL-manager) to the
82 We propose to introduce CRLs into BMCWeb's SSL Context. Whenever BMCWeb reloads,
89 We can model the whole CRLs list as a single object, but that's not aligned with
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/gperftools/gperftools/
H A Dppc-musl.patch34 // We don't care about the rest, since the IP value is at 'uc' field.
43 // We don't care about the rest, since IP value is at 'mctx' field.
52 // We don't care about the rest, since IP value is at 'uc' field.A
/openbmc/qemu/docs/system/
H A Dintroduction.rst153 general purpose platform for running Aarch64 guests. We enable
164 We then define the 4 vCPUs using the ``max`` option which gives us all
165 the Arm features QEMU is capable of emulating. We enable a more
167 algorithm. We explicitly specify TCG acceleration even though QEMU
177 devices we need to define them. We give them ids so we can link them
186 We connect the user-mode networking to our network device. As
194 We connect the guest visible block device to an LVM partition we have
201 We then tell QEMU to multiplex the :ref:`QEMU monitor` with the serial
/openbmc/openbmc/poky/meta/recipes-core/ovmf/
H A Dovmf-shell-image.bb14 # We want a minimal image with just ovmf-shell-efi unpacked in it. We
/openbmc/openbmc/meta-aspeed/recipes-bsp/u-boot/
H A Du-boot-common-aspeed-sdk_2019.04.inc11 # We use the revision in order to avoid having to fetch it from the
23 # We don't have 'u-boot-initial-env' target in our u-boot version
/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-connectivity/network-manager-applet/
H A Dnetwork-manager-applet_1.36.0.bb16 # We don't not have ubuntu's appindicator (yet?)
18 # We currently don't build NetworkManager with libteamdctl support
/openbmc/openbmc/meta-security/wic/
H A Dbeaglebone-yocto-verity.wks.in7 # A dm-verity variant of the regular wks for beaglebone black. We need to fetch
9 # not recreate the exact block device corresponding with the hash tree. We must
/openbmc/openbmc/poky/meta/recipes-devtools/qemu/qemu/
H A D0010-configure-lookup-meson-exutable-from-PATH.patch20 -# We expect mkvenv or pip to have created pyvenv/bin/meson for us.
21 -# We ignore PATH completely here: we want to use the venv's Meson
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-multimedia/libid3tag/libid3tag/
H A D10_utf16.patch22 + /* We were called with a bogus length. It should always
23 + * be an even number. We can deal with this in a few ways:
/openbmc/openbmc-tools/
H A DREADME.md33 be applied. We may push back in the event that similar tools already exist or
38 We don't ask for much, but you need to give us at least a
45 the repository to your PATH might be a bit of a dice-roll. We may also move or
/openbmc/openbmc/poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/
H A D0001-libc-compat.h-fix-some-issues-arising-from-in6.h.patch22 -/* We have included glibc headers... */
69 -/* We unconditionally define the in6_addr macros and glibc must
70 +/* We unconditionally define the in6_addr macros and libc must

12345678910>>...66