| /openbmc/linux/Documentation/process/ |
| H A D | kernel-enforcement-statement.rst | 6 As developers of the Linux kernel, we have a keen interest in how our software
7 is used and how the license for our software is enforced. Compliance with the
9 sustainability of our software and community.
12 contributions made to our community, we share an interest in ensuring that
13 individual enforcement actions are conducted in a manner that benefits our
15 growth of our software ecosystem. In order to deter unhelpful enforcement
16 actions, we agree that it is in the best interests of our development
18 on behalf of ourselves and any successors to our copyright interests:
21 it is in the best interests of our development community to adopt the
22 following provisions of GPL-3.0 as additional permissions under our
[all …]
|
| /openbmc/linux/drivers/net/ethernet/chelsio/ |
| H A D | Kconfig | 31 For general information about Chelsio and our products, visit
32 our website at <http://www.chelsio.com>.
34 For customer support, please visit our customer support page at
58 For general information about Chelsio and our products, visit
59 our website at <http://www.chelsio.com>.
61 For customer support, please visit our customer support page at
81 For general information about Chelsio and our products, visit
82 our website at <http://www.chelsio.com>.
84 For customer support, please visit our customer support page at
122 For general information about Chelsio and our products, visit
[all …]
|
| /openbmc/linux/drivers/scsi/csiostor/ |
| H A D | Kconfig | 11 For general information about Chelsio and our products, visit
12 our website at <http://www.chelsio.com>.
14 For customer support, please visit our customer support page at
|
| /openbmc/linux/drivers/crypto/chelsio/ |
| H A D | Kconfig | 14 For general information about Chelsio and our products, visit
15 our website at <http://www.chelsio.com>.
17 For customer support, please visit our customer support page at
|
| /openbmc/linux/drivers/infiniband/hw/cxgb4/ |
| H A D | Kconfig | 12 For general information about Chelsio and our products, visit
13 our website at <http://www.chelsio.com>.
15 For customer support, please visit our customer support page at
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/wangxun/ |
| H A D | ngbe.rst | 12 If you have problems with the software or hardware, please contact our
13 customer support team via email at nic-support@net-swift.com or check our website
|
| /openbmc/linux/arch/parisc/math-emu/ |
| H A D | README | 5 enough to update our copies with later changes from HP-UX -- it'll
6 make their 'diff' job easier if our code is relatively unmodified.
|
| /openbmc/openbmc/meta-phosphor/recipes-support/boost/ |
| H A D | boost_%.bbappend | 3 #This is largely to improve our build times by not building or installing
4 #modules that OpenBMC does not use by our coding standard. Another thing to
|
| /openbmc/linux/Documentation/gpu/amdgpu/display/ |
| H A D | index.rst | 8 reason, our Display Core Driver is divided into two pieces:
23 If you want to learn more about our driver details, take a look at the below
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/abseil-cpp/abseil-cpp/ |
| H A D | 0005-Don-t-match-Wnon-virtual-dtor-in-the-flags-are-neede.patch | 6 our warnings on others" case. Do this by matching on "-Wno-*" instead of
28 # These flags are needed to suppress warnings that might fire in our headers.
|
| /openbmc/linux/arch/alpha/lib/ |
| H A D | strrchr.S | 22 zapnot a1, 1, a1 # e0 : zero extend our test character
24 sll a1, 8, t5 # e0 : replicate our test character
80 addq t6, t0, v0 # .. e1 : add our aligned base ptr to the mix
|
| /openbmc/openbmc/poky/meta/recipes-support/lzo/lzo/ |
| H A D | 0001-Use-memcpy-instead-of-reinventing-it.patch | 7 constraints for our architectures.
37 +/* Debian-specific change: we know that our compiler inlines memcpy() with
62 +/* Debian-specific change: we know that our compiler inlines memcpy() with
|
| /openbmc/openbmc/meta-security/meta-tpm/recipes-tpm1/trousers/files/ |
| H A D | 0001-build-don-t-override-localstatedir-mandir-sysconfdir.patch | 39 -# like put our sbin stuff in /usr/sbin and our library in /usr/lib. It'll do some other
40 -# things that don't make sense like put our config file in /usr/etc. So, I'll just hack
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/ |
| H A D | 0028-corstone1000-boot-index-from-active.patch | 6 In our platform, the Secure Enclave is the one who control
29 + * in our platform, the Secure Enclave is the one who control
|
| /openbmc/webui-vue/docs/guide/guidelines/ |
| H A D | internationalization.md | 24 provides to our components) for outputting translation messages.
28 - A new `src/i18n.js` file is added and it registers Vue I18n as a plugin to our
30 - The CLI creates a `src/locales/en-US.json` file, which contains our default
|
| /openbmc/qemu/hw/hyperv/ |
| H A D | trace-events | 30 hv_balloon_our_range_add(uint64_t count, uint64_t start) "adding our range %"PRIu64" @ 0x%"PRIx64
32 …ge hole %"PRIu64" @ 0x%"PRIx64" from range %"PRIu64" @ 0x%"PRIx64", before our start 0x%"PRIx64", …
33 …mmon range %"PRIu64" @ 0x%"PRIx64" from range %"PRIu64" @ 0x%"PRIx64" with our %"PRIu64" @ 0x%"PRI…
|
| /openbmc/openbmc/poky/meta/classes-recipe/ |
| H A D | meson-routines.bbclass | 13 # Map our ARCH values to what Meson expects:
39 # Map our OS values to what Meson expects:
|
| /openbmc/u-boot/arch/arm/mach-omap2/ |
| H A D | lowlevel_init.S | 54 @ our registers
67 @ our registers
|
| /openbmc/u-boot/doc/ |
| H A D | README.blackfin | 22 All open source code for the Blackfin processors are being handled via our
45 For Blackfin specific documentation, you can visit our dedicated doc wiki:
|
| /openbmc/libcper/docs/ |
| H A D | OEMExtensions.md | 59 Once this is done, we can add our section to the parser.
63 To identify our section for parsing, we must define a section GUID within
88 Finally, we need to add a section definition for our section, matching the GUID
|
| /openbmc/qemu/docs/specs/ |
| H A D | ppc-spapr-hcalls.rst | 13 In addition to those calls, we have added our own private hypervisor
31 calls our private H_RTAS hypervisor call to pass the RTAS calls to QEMU.
66 is used by our SLOF firmware to invert the screen.
|
| /openbmc/openbmc/poky/meta-poky/classes/ |
| H A D | poky-sanity.bbclass | 31 # is used in a comment, so do our own here. The code below can be
45 # ensure our function runs after the OE-Core one
|
| /openbmc/docs/designs/ |
| H A D | bios-bmc-smm-error-logging.md | 111 An example of a processing library (and something we would like to push in our
118 - IPMI was considered, did not meet our speed requirement of writing 1KB entry
122 - LPC / eSPI was also considered but our BMC's SHM buffer was limited to 4KB
123 which was not enough for our use case.
126 and IPMI KCS for synchronization. LPC as discussed, does not fit our current
128 - We may use MCTP PCIe VDM on our future platforms once we have more resources
130 for our current project timeline.
|
| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | test-process.rst | 14 The project aims to test changes against our test matrix before those
22 "a-full", simply for ease of sorting in the UI. Use our Autobuilder
39 our sstate up to date. On the weekend, there is a ``master-next`` build
60 only along with point releases of our stable branches.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/python3/ |
| H A D | python3-manifest.json | 41 # created on the new release and for obvious reasons we wouldn't have it on our
42 # old manifest, all of these issues would cause runtime errors on our system.
79 # This will eventually cause runtime errors on our system if we don't include the misc packa…
80 # on our image, because the _uuid files will be missing.
|