| /openbmc/docs/designs/ |
| H A D | design-template.md | 7 - Not all new features need a design document. If a feature can be contributed
9 areas, it doesn't need a design discussion and documentation.
17 design proposals compel the reviewers agree with the proposal's conclusions.
23 - You should get your design reviewed and merged before writing your code.
25 may learn of new requirements during the design review process that could
46 "design"
50 # Example design - this is the design title
74 glossary if necessary. Note: this is background; do not write about your design,
87 ## Proposed Design
98 (2 paragraphs) Include alternate design ideas here which you are leaning away
[all …]
|
| H A D | cper-records.md | 33 design, and passes the OpenBMC CI tests currently. This is the proposed branch
54 ## Proposed Design
56 While this design fits into a much more elaborate design alluded to in the
62 might not meet all design goals for all contributors, having a common
65 Future design docs (or amendments to this design) will iterate on implementing
66 more of the design referenced in this [CPER specification][arm_sbmr], for common
68 the quality up to standards is the initial goal of this design.
72 Rewrite libcper decoding from a new design point. While this is certainly
85 - Which repositories are expected to be modified to execute this design?
99 design is complete.
|
| H A D | README.md | 3 This is a directory of design documents.
5 Newly authored design documents are encouraged to follow the
6 [design document template](design-template.md).
|
| H A D | expired-password.md | 61 This design uses meanings 3 and 4 except where indicated.
87 ## Proposed Design
89 This design has three main parts:
122 session. The ipmitool is not being enhanced by this design.
131 - Redfish: This design adds the Redfish PasswordChangeRequired handling to
152 This design is intended to cover any cause of expired password, including both
156 This design is intended to enable the webui-vue web application to implement a
159 Per the above design, when the web app uses either `/login` or
206 Warning. This design may leave the BMC with its default password for an extended
207 period of time if the use case given in the requirements section of this design
[all …]
|
| H A D | liquid-leak-detection.md | 24 generic in its design and does not meet most of the requirements.
42 ## Proposed Design
59 This design involves implementing following Redfish schemas and associated
130 [event logging design](https://github.com/openbmc/docs/blob/master/designs/event-logging.md).
143 The current design of the phosphor-gpio-monitor is too generic and does not meet
155 design. This would require implementation in the BMCWeb.
159 The design may cause a minor reduction in system performance due to the need for
166 - Which repositories are expected to be modified to execute this design? BMCWeb,
|
| H A D | uart-mux-support.md | 1 # uart-mux-support design
19 but it has been determined that this feature needs a design document.
24 The background here is that there are some design choices which may affect other
49 ## Design Considerations
91 With these in mind we end up with the following table of design options:
161 concrete design of the platform itself.
289 API, i.e. with the out-of-band command design point (2.1). However, the choice
290 becomes more of an implementation detail if either of design options 2.2 or 2.3
294 ## Pruning the Design Decision Tree
314 eliminates design options A-D inclusive.
[all …]
|
| H A D | estoraged.md | 1 # eStoraged Design - Encrypted Secondary Storage Management Daemon
24 This design is intended to manage secondary storage devices and cannot be used
28 This design makes use of the
36 This design is specifically targeted for use with eMMC devices, and we plan to
55 This design should provide an interface for the following capabilities:
75 The users of this design can be any other software component in the BMC. Some
83 ## Proposed Design
165 organizations, it is outside the scope of this design.
|
| /openbmc/u-boot/arch/arm/mach-tegra/tegra20/ |
| H A D | Kconfig | 12 bool "Avionic Design Medcom-Wide board"
20 bool "Avionic Design Plutux board"
28 bool "Avionic Design Tamonten Evaluation Carrier"
49 source "board/avionic-design/medcom-wide/Kconfig"
51 source "board/avionic-design/plutux/Kconfig"
53 source "board/avionic-design/tec/Kconfig"
|
| /openbmc/webui-vue/ |
| H A D | CONTRIBUTING.md | 13 - [Design Reviews](#design-reviews)
103 the IBM Design Partner program.
105 ### What is an OpenBMC Design Partner?
110 interviews, participatory design, periodic surveys, or usability testing
118 ## Design Reviews
120 When making changes to an existing design, we create a design review issue in
122 [OpenBMC GUI Design Workgroup](https://github.com/openbmc/openbmc/wiki/GUI-Design-work-group).
|
| /openbmc/webui-vue/.github/ISSUE_TEMPLATE/ |
| H A D | design-review.md | 2 name: Design review
3 about: Create story used to track design proposals and decisions
21 ## Design Review Workflow
23 1. Each design iteration will have a comment section
|
| /openbmc/entity-manager/configurations/ |
| H A D | VENDORS.md | 7 In some cases a company might design a component (such as a network card),
11 when multiple companies are involved in the chain between design and end-user.
16 1. A company which primarily initiates and oversees the design, manufacture and
29 3. When one company primarily oversees the design but other companies
31 the company that primarily oversaw the design of the component would be the
|
| /openbmc/qemu/include/hw/watchdog/ |
| H A D | cmsdk-apb-watchdog.h | 14 * System Design Kit (CMSDK) and documented in the Cortex-M System
15 * Design Kit Technical Reference Manual (ARM DDI0479C):
16 * https://developer.arm.com/products/system-design/system-design-kits/cortex-m-system-design-kit
|
| /openbmc/qemu/include/hw/timer/ |
| H A D | cmsdk-apb-dualtimer.h | 14 * System Design Kit (CMSDK) and documented in the Cortex-M System
15 * Design Kit Technical Reference Manual (ARM DDI0479C):
16 * https://developer.arm.com/products/system-design/system-design-kits/cortex-m-system-design-kit
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp.md | 13 This design aims to use the Management Component Transport Protocol (MCTP) to
22 allows us to design these parts separately. Currently, IPMI defines both of
51 This document is focused on the "transport" part of the platform design. While
53 covered in detail much; we will propose those parts in separate design efforts.
54 For example, the PLDM design at [pldm-stack.md].
56 As part of the design, the references to MCTP "messages" and "packets" are
93 Design details for both approaches are covered in their relevant documents, but
125 Design and development needs to involve potential host, management controllers
|
| /openbmc/u-boot/include/configs/ |
| H A D | tec-ng.h | 4 * Avionic Design GmbH <www.avionic-design.de>
13 #define CONFIG_TEGRA_BOARD_STRING "Avionic Design Tamonten™ NG Evaluation Carrier"
|
| H A D | plutux.h | 6 * Avionic Design GmbH <www.avionic-design.de>
15 #define CONFIG_TEGRA_BOARD_STRING "Avionic Design Plutux"
|
| H A D | medcom-wide.h | 6 * Avionic Design GmbH <www.avionic-design.de>
15 #define CONFIG_TEGRA_BOARD_STRING "Avionic Design Medcom-Wide"
|
| H A D | tec.h | 6 * Avionic Design GmbH <www.avionic-design.de>
15 #define CONFIG_TEGRA_BOARD_STRING "Avionic Design Tamonten Evaluation Carrier"
|
| /openbmc/docs/designs/inventory/ |
| H A D | gpio-based-hardware-inventory.md | 19 gpios. This design focuses on those.
21 Connected entities detectable via other means are out of scope of this design.
25 The existing design for the gpio based cable presence is partially implemented
28 [existing design by Chu Lin](https://github.com/openbmc/docs/blob/879601d92becfa1dbc082f487abfb5e01…
116 ## Proposed Design
118 The proposed design is to create a new daemon in the entity-manager repository,
412 - Comparing to Chu Lin's design, this design is not focused on the IPMI or
416 which was created as part of Chu Lin's design.
418 - Comparing to Chu Lin's design, this design does not directly provide a cable
422 - Comparing to Chu Lin's design, this design is not limited to cables.
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/BIOSConfig/ |
| H A D | README.md | 9 Please refer to the [design][design] for more details.
44 [design]:
|
| /openbmc/u-boot/board/avionic-design/tec/ |
| H A D | MAINTAINERS | 2 M: Alban Bedel <alban.bedel@avionic-design.de>
4 F: board/avionic-design/tec/
|
| /openbmc/u-boot/board/avionic-design/plutux/ |
| H A D | MAINTAINERS | 2 M: Alban Bedel <alban.bedel@avionic-design.de>
4 F: board/avionic-design/plutux/
|
| /openbmc/u-boot/board/avionic-design/tec-ng/ |
| H A D | Makefile | 4 # Avionic Design GmbH <www.avionic-design.de>
|
| H A D | MAINTAINERS | 2 M: Alban Bedel <alban.bedel@avionic-design.de>
4 F: board/avionic-design/tec-ng/
|
| /openbmc/u-boot/board/avionic-design/medcom-wide/ |
| H A D | MAINTAINERS | 2 M: Alban Bedel <alban.bedel@avionic-design.de>
4 F: board/avionic-design/medcom-wide/
|