1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
|
# OpenBMC
[](https://openpower.xyz/job/openbmc-build/)
OpenBMC is a Linux distribution for management controllers used in devices such
as servers, top of rack switches or RAID appliances. It uses
[Yocto](https://www.yoctoproject.org/),
[OpenEmbedded](https://www.openembedded.org/wiki/Main_Page),
[systemd](https://www.freedesktop.org/wiki/Software/systemd/), and
[D-Bus](https://www.freedesktop.org/wiki/Software/dbus/) to allow easy
customization for your platform.
## Setting up your OpenBMC project
### 1) Prerequisite
- Ubuntu 14.04
```
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
```
- Fedora 28
```
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake \
rpcgen perl-Thread-Queue perl-bignum perl-Crypt-OpenSSL-Bignum
sudo dnf groupinstall "C Development Tools and Libraries"
```
### 2) Download the source
```
git clone git@github.com:openbmc/openbmc.git
cd openbmc
```
### 3) Target your hardware
Any build requires an environment set up according to your hardware target.
There is a special script in the root of this repository that can be used
to configure the environment as needed. The script is called `setup` and
takes the name of your hardware target as an argument.
The script needs to be sourced while in the top directory of the OpenBMC
repository clone, and, if run without arguments, will display the list
of supported hardware targets, see the following example:
```
$ . setup <machine> [build_dir]
Target machine must be specified. Use one of:
bletchley gsj romulus
dl360poc kudo s2600wf
e3c246d4i mihawk swift
ethanolx mtjade tiogapass
evb-ast2500 nicole transformers
evb-ast2600 olympus-nuvoton witherspoon
evb-npcm750 on5263m5 witherspoon-tacoma
f0b p10bmc x11spi
fp5280g2 palmetto yosemitev2
g220a qemuarm zaius
gbs quanta-q71l
```
Once you know the target (e.g. romulus), source the `setup` script as follows:
```
. setup romulus
```
### 4) Build
```
bitbake obmc-phosphor-image
```
Additional details can be found in the [docs](https://github.com/openbmc/docs)
repository.
## OpenBMC Development
The OpenBMC community maintains a set of tutorials new users can go through
to get up to speed on OpenBMC development out
[here](https://github.com/openbmc/docs/blob/master/development/README.md)
## Build Validation and Testing
Commits submitted by members of the OpenBMC GitHub community are compiled and
tested via our [Jenkins](https://jenkins.openbmc.org/) server. Commits are run
through two levels of testing. At the repository level the makefile `make
check` directive is run. At the system level, the commit is built into a
firmware image and run with an arm-softmmu QEMU model against a barrage of
[CI tests](https://openpower.xyz/job/openbmc-test-qemu-ci/).
Commits submitted by non-members do not automatically proceed through CI
testing. After visual inspection of the commit, a CI run can be manually
performed by the reviewer.
Automated testing against the QEMU model along with supported systems are
performed. The OpenBMC project uses the
[Robot Framework](http://robotframework.org/) for all automation. Our
complete test repository can be found
[here](https://github.com/openbmc/openbmc-test-automation).
## Submitting Patches
Support of additional hardware and software packages is always welcome.
Please follow the [contributing guidelines](https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md)
when making a submission. It is expected that contributions contain test
cases.
## Bug Reporting
[Issues](https://github.com/openbmc/openbmc/issues) are managed on
GitHub. It is recommended you search through the issues before opening
a new one.
## Questions
First, please do a search on the internet. There's a good chance your question
has already been asked.
For general questions, please use the openbmc tag on
[Stack Overflow](https://stackoverflow.com/questions/tagged/openbmc).
Please review the [discussion](https://meta.stackexchange.com/questions/272956/a-new-code-license-the-mit-this-time-with-attribution-required?cb=1)
on Stack Overflow licensing before posting any code.
For technical discussions, please see [contact info](#contact) below for
Discord and mailing list information. Please don't file an issue to ask a
question. You'll get faster results by using the mailing list or Discord.
## Features of OpenBMC
**Feature List**
* Host management: Power, Cooling, LEDs, Inventory, Events, Watchdog
* Full IPMI 2.0 Compliance with DCMI
* Code Update Support for multiple BMC/BIOS images
* Web-based user interface
* REST interfaces
* D-Bus based interfaces
* SSH based SOL
* Remote KVM
* Hardware Simulation
* Automated Testing
* User management
* Virtual media
**Features In Progress**
* OpenCompute Redfish Compliance
* Verified Boot
**Features Requested but need help**
* OpenBMC performance monitoring
## Finding out more
Dive deeper into OpenBMC by opening the
[docs](https://github.com/openbmc/docs) repository.
## Technical Steering Committee
The Technical Steering Committee (TSC) guides the project. Members are:
* Brad Bishop (chair), IBM
* Nancy Yuen, Google
* Sai Dasari, Facebook
* James Mihm, Intel
* Sagar Dharia, Microsoft
* Samer El-Haj-Mahmoud, Arm
## Contact
- Mail: openbmc@lists.ozlabs.org [https://lists.ozlabs.org/listinfo/openbmc](https://lists.ozlabs.org/listinfo/openbmc)
- Discord: https://discord.gg/69Km47zH98
|
