generally (full) in projects: openbmc - OpenGrok search results

Searched full:generally (Results 1 – 25 of 1390) sorted by relevance

/openbmc/docs/
H A D	glossary.md	`12 band management access to a host, generally a computer system. 22 ODM - Original design manufacturer. In OpenBMC, ODM generally refers to the 25 OEM - Original equipment manufacturer. In OpenBMC, OEM generally refers to the 40 Server - A computing device, generally the one served by the BMC.`
H A D	meta-layer-guidelines.md	`20 features, and codebase are prioritized over any one patch, and generally does so 21 in code review. If patches are checked into meta layers, generally the 115 Generally an OpenBMC specific repository is something that does any of the`
/openbmc/bmcweb/redfish-core/include/registries/
H A D	openbmc_message_registry.readmefirst.md	`5 Messages in this registry are intended to be generally useful across OpenBMC 9 1. Messages should not be specific to a piece or type of hardware. Generally 20 This generally involves placing the substitution parameters in the`
/openbmc/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A D	uncore-interconnect.json	25 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 34 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 622 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 764 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 772 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 781 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 790 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 799 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 808 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 817 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… [all …]
/openbmc/docs/architecture/
H A D	optionality.md	`37 limits, and required commands. These types of features generally show no 60 and generally will default to disabled. Features of this nature, when disabled, 67 CI will generally enable all developer opt-in features to ensure the most`
/openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellx/
H A D	uncore-interconnect.json	615 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 756 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 764 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 773 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 782 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 791 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 800 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 809 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 818 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 827 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A D	uncore-interconnect.json	615 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 757 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 765 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 774 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 783 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 792 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 801 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 810 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 819 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 828 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… [all …]
/openbmc/linux/Documentation/power/
H A D	suspend-and-interrupts.rst	`12 Device interrupt request lines (IRQs) are generally disabled during system 61 System wakeup interrupts generally need to be configured to wake up the system 72 After wakeup, it generally is better to disable that input to prevent the 128 interrupt source and an IRQF_NO_SUSPEND interrupt source does not generally`
H A D	freezing-of-tasks.rst	`36 kernel/freezer.c & include/linux/freezer.h). User space processes are generally 104 Generally speaking, there is a couple of reasons to use the freezing of tasks: 123 devices are deactivated, because we generally need them for swapping out. 206 tasks, since it generally exists anyway.`
/openbmc/linux/Documentation/driver-api/media/
H A D	camera-sensor.rst	`15 divisors. The clock tree is generally configured by the driver based on a few 17 and the link frequency. The two parameters generally are obtained from system 64 Register list based drivers generally, instead of able to configure the device 115 level interface natively, generally use the concept of frame interval (or frame`
/openbmc/openpower-hw-diags/analyzer/
H A D	resolution.hpp	`67 * which generally means this chip is a child of another. 83 * empty string refers to the chip itself, which generally means this chip 109 * which generally means this chip is a child of another. 125 * empty string refers to the chip itself, which generally means this chip`
/openbmc/linux/Documentation/devicetree/bindings/memory-controllers/ddr/
H A D	jedec,lpddr-props.yaml	`10 Different LPDDR types generally use the same properties and only differ in the 12 reused for each type. Nodes using this schema should generally be nested under`
/openbmc/u-boot/arch/mips/lib/
H A D	reloc.c	`97 * relocate_code() - Relocate U-Boot, generally from flash to DDR 102 * Relocate U-Boot from its current location (generally in flash) to a new one 103 * (generally in DDR). This function will copy the U-Boot binary & apply`
/openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A D	uncore-interconnect.json	25 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 34 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 379 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 467 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 619 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 627 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 635 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 643 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 651 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 659 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … [all …]
/openbmc/u-boot/doc/
H A D	README.kconfig	`109 When adding a new board, the following steps are generally needed: 125 It is generally placed at board/<board>/MAINTAINERS or 129 When removing an obsolete board, the following steps are generally needed:`
/openbmc/u-boot/include/configs/
H A D	ti_armv7_common.h	`85 * large malloc pool as we generally have a lot of DDR, and we opt for 87 * generally easily constrained later if needed. We enable the config 114 * SPL framework found under common/spl/. Given our generally common memory`
/openbmc/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/
H A D	uncore-interconnect.json	2181 …age requested but lost arbitration : Home (REQ) messages on AD. REQ is generally used to send req… 2208 …lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2235 …uested but lost arbitration : Data Response (WB) messages on BL. WB is generally used to transmit… 2244 …age requested but lost arbitration : Home (REQ) messages on AD. REQ is generally used to send req… 2271 …lost arbitration : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2298 …uested but lost arbitration : Data Response (WB) messages on BL. WB is generally used to transmit… 2379 … due to lack of remote UPI credits : Home (REQ) messages on AD. REQ is generally used to send req… 2406 …mote UPI credits : Non-Coherent Broadcast (NCB) messages on BL. NCB is generally used to transmit… 2433 … lack of remote UPI credits : Data Response (WB) messages on BL. WB is generally used to transmit… 2442 … due to lack of remote UPI credits : Home (REQ) messages on AD. REQ is generally used to send req… [all …]
/openbmc/qemu/docs/system/
H A D	target-riscv.rst	`10 QEMU has generally good support for RISC-V guests. It has support for 13 CPUs are generally built into "system-on-chip" (SoC) designs created by`
H A D	device-emulation.rst	`35 can be inferred, for example PCI devices are generally automatically 66 While the choice of back end is generally transparent to the guest,`
/openbmc/sdbusplus/
H A D	.gitignore	`107 # Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control. 114 # Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.`
/openbmc/qemu/python/
H A D	README.rst	10 ``setup.py``. You will generally invoke it by doing one of the following: 54 A strong downside to both approaches is that they generally interfere
/openbmc/qemu/docs/devel/
H A D	submitting-a-pull-request.rst	`6 QEMU welcomes contributions of code, but we generally expect these to be 9 for more details). Generally only existing submaintainers of a tree`
/openbmc/linux/Documentation/i2c/busses/
H A D	i2c-ali15x3.rst	`61 - Gigabyte GA-5AX (Generally doesn't work because the BIOS doesn't 121 SMBus. Therefore the SMBus hangs can generally be avoided`
/openbmc/linux/Documentation/mm/
H A D	active_mm.rst	`80 should generally just do 85 we have a user context", and is generally done by the page fault handler`
/openbmc/entity-manager/
H A D	CONFIG_FORMAT.md	`21 Config file writers are generally building support for a wide range of 22 reactors on a single piece of hardware, and will generally have less 30 - Hardware constraints, bugs, and oddities are generally found over time. The 68 channels can generally be represented with a default that works for all`

12 3 4 5 6 7 8 9 10 >>...56

Project(s)

Full Search
Definition
Symbol
File Path
History
Type