| /openbmc/u-boot/arch/arm/mach-stm32/stm32f4/ |
| H A D | Kconfig | 4 bool "STM32F429 Discovery board"
10 bool "STM32F469 Discovery board"
12 source "board/st/stm32f429-discovery/Kconfig"
14 source "board/st/stm32f469-discovery/Kconfig"
|
| /openbmc/u-boot/board/st/stm32f429-discovery/ |
| H A D | MAINTAINERS | 1 STM32F429-DISCOVERY BOARD
4 F: board/st/stm32f429-discovery/
5 F: include/configs/stm32f429-discovery.h
|
| H A D | Kconfig | 5 default "stm32f429-discovery"
17 default "stm32f429-discovery"
|
| /openbmc/u-boot/board/st/stm32f469-discovery/ |
| H A D | MAINTAINERS | 1 STM32F469-DISCOVERY BOARD
4 F: board/st/stm32f469-discovery/
5 F: include/configs/stm32f469-discovery.h
|
| H A D | Kconfig | 5 default "stm32f469-discovery"
17 default "stm32f469-discovery"
|
| H A D | Makefile | 6 obj-y := stm32f469-discovery.o
|
| /openbmc/docs/designs/management-console/ |
| H A D | service-discovery.md | 1 # Service processor discovery through Avahi
11 1. <https://www.engineersgarage.com/Articles/IoT-Service-Discovery-Protocols>
30 Currently in openBMC, Avahi is being used as service discovery. Avahi is a
31 system which facilitates service discovery on a local network via the
52 As part of avahi discovery response, the client receives the following:
60 ### How to do discovery through avahi
|
| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | storage_controller.hpp | 13 Discovery, enumerator
28 {NVMeControllerType::Discovery, "Discovery"},
|
| H A D | external_account_provider.hpp | 39 Discovery, enumerator
72 {OAuth2Mode::Discovery, "Discovery"},
|
| H A D | account_service.hpp | 59 Discovery, enumerator
126 {OAuth2Mode::Discovery, "Discovery"},
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-connectivity/gupnp/ |
| H A D | gssdp_1.6.3.bb | 1 SUMMARY = "Resource discovery and announcement over SSDP"
2 DESCRIPTION = "GSSDP implements resource discovery and announcement over SSDP \
3 (Simpe Service Discovery Protocol)."
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-bsp/irda-utils/irda-utils-0.9.18/ |
| H A D | init | 28 DISCOVERY=
34 DISCOVERY=
50 if [ "$DISCOVERY" = "yes" ];then
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/MCTP/ |
| H A D | README.md | 4 mcptd and aids in the discovery of MCTP enabled devices by application layer
6 layer protocols will rely on the discovery of
11 complete the PLDM discovery flow with the MCTP endpoint. Also mctpd discovers
|
| /openbmc/smbios-mdr/src/ |
| H A D | speed_select.cpp | 373 * @return Whether discovery was successfully finished.
381 // Persistent list - only populated after complete/successful discovery in discoverCPUsAndConfigs()
387 // next discovery attempt. in discoverCPUsAndConfigs()
393 // PECI contention, SST discovery could take a long time. This lets us in discoverCPUsAndConfigs()
502 * Attempt discovery process, and if it fails, wait for 10 seconds to try again.
516 DEBUG_PRINT << "Starting discovery\n"; in discoverOrWait()
524 // In case of repeated failure to finish discovery, turn off this in discoverOrWait()
529 std::cerr << "Aborting SST discovery\n"; in discoverOrWait()
533 std::cerr << "Retrying SST discovery later\n"; in discoverOrWait()
536 DEBUG_PRINT << "Finished discovery attempt: " << finished << '\n'; in discoverOrWait()
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/ndisc6/ |
| H A D | ndisc6_1.0.8.bb | 59 DESCRIPTION:${PN}-ndisc6 = "ICMPv6 Neighbor Discovery tool. \
60 Performs IPv6 neighbor discovery in userland. Replaces arping from the \
62 DESCRIPTION:${PN}-rdisc6 = "ICMPv6 Router Discovery tool. \
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-dbs/rocksdb/files/ |
| H A D | 0001-CMakeLists.txt-Make-the-test-discovery-occur-on-targ.patch | 4 Subject: [PATCH] CMakeLists.txt: Make the test discovery occur on target
6 Set DISCOVERY_MODE to PRE_TEST to delay test discovery until just
|
| /openbmc/qemu/hw/arm/ |
| H A D | b-l475e-iot01a.c | 2 * B-L475E-IOT01A Discovery Kit machine
21 * Discovery kit for IoT node, multi-channel communication with STM32L4.
120 mc->desc = "B-L475E-IOT01A Discovery Kit (Cortex-M4)"; in bl475e_machine_init()
|
| /openbmc/phosphor-networkd/src/ |
| H A D | ncsi_cmd.cpp | 85 …" --package PACKAGE, -p For non-discovery commands this is required; for discovery it is optio… in print_usage()
86 " restricts the discovery to a specific package index.\n" in print_usage()
328 // For non-discovery commands, package is required. in parseGlobalOptions()
334 // Do nothing; package remains nullopt for discovery. in parseGlobalOptions()
700 std::cout << "Starting NC-SI Package and Channel Discovery...\n"; in ncsiDiscover()
707 std::cout << "Restricting discovery to Package " << *options.package in ncsiDiscover()
758 << ". Stopping discovery.\n"; in ncsiDiscover()
771 // We found a channel on this package, so we stop discovery in ncsiDiscover()
782 << "No available NC-SI packages or channels found. Discovery complete.\n"; in ncsiDiscover()
819 // For non-discovery commands, package must be provided. in main()
|
| /openbmc/u-boot/arch/arm/mach-stm32/stm32f7/ |
| H A D | Kconfig | 4 bool "STM32F746 Discovery board"
|
| /openbmc/u-boot/arch/arm/mach-stm32/stm32h7/ |
| H A D | Kconfig | 4 bool "STM32H743 Discovery board"
|
| /openbmc/u-boot/board/st/stm32f746-disco/ |
| H A D | MAINTAINERS | 1 STM32F746 DISCOVERY BOARD
|
| /openbmc/openbmc/meta-google/recipes-google/networking/gbmc-bridge/ |
| H A D | gbmc-br-ra.service | 2 Description=gBMC Bridge RA Discovery
|
| /openbmc/qemu/hw/uefi/ |
| H A D | var-service-sysbus.c | 79 /* generic: hardware discovery via FDT */
110 /* x64: hardware discovery via etc/hardware-info fw_cfg */
|
| /openbmc/u-boot/board/st/stm32h743-disco/ |
| H A D | MAINTAINERS | 1 STM32H743 DISCOVERY BOARD
|
| /openbmc/openbmc/meta-google/recipes-google/networking/gbmc-nic-config/ |
| H A D | gbmc-nic-ra@.service | 2 Description=gBMC %i RA Discovery
|