| commit | 169657e29c16309a5fc1e66f3ebee720930f8663 | [log] [tgz] |
|---|---|---|
| author | Joel Stanley <joel@jms.id.au> | Mon Mar 06 17:11:18 2017 +1030 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Jun 15 17:04:43 2017 +0000 |
| tree | 9b42db20d21ab70909be836d135bc69444f8f964 | |
| parent | debfbd049512f4097e77b37604c253d68e61ae2b [diff] |
kernel: Update 4.10 tree Move to 4.10.17. This incorporates all of the 4.10 stable fixes. 4.10 is now end of lifed and does not receive further fixes. New drivers: - LPC snoop - OCC SBE - SBE FIFO - Infineon IR35221 - Maxim MAX31785 - of_serial reset support - Aspeed PWM and fan tach driver - UCHI driver - FSI device tree match support New platforms: - Mellanox MSN BMC Config and device tree changes: - Enable VMSPLIT_2G for ast2400. This is allows us to map all of the mtd flash - Fix device trees for ast2400 mtd support Resolves openbmc/openbmc#1686 - Add CFAM layout to device tree Resolves openbmc/openbmc#1697 - Enable new drivers [the content below is for the changes made in c13af44db76bd1 and are included so that the details are in openbmc history] This is OpenBMC's third major kernel change. We now move to a 4.10 base, where a larger amount of our driver support has been upstreamed. - NCSI stack - IRQ driver - Watchdog driver - Clocksource driver - GPIO driver - Pinmux driver - ftgmac100 ast2500 support - IPMI BT driver - adm1275 driver fix In addition, this contains backports of a significant amount of work that was done post-4.10. - LPC bindings - Pinctrl enhancements - Flash controller (spi-nor) basic support - ast2500 GPIO support - LPC host interface controller driver - Aspeed ADC - GPIO debounce support - Pinconf (biasing and drive strength) driver Finally, there is the work-in-progress that has been temporarly staged in the dev tree while we get it reviewed and upstreamed. - New I2C driver - OCC driver - LPC mailbox driver - FSI core - VUART driver Defconfig updates - Optmise options for network performance - Update for upstreamed drivers (MTD driver was renamed, etc) - Enable drivers that are in use Legacy Yocto layer changes - Remove palmetto GPIO hog patch. It is in the kenrel tree Change-Id: I4b48b843572c8f8d547763f0d3cb5a6742bbf0e3 Signed-off-by: Joel Stanley <joel@jms.id.au>
- meta-openbmc-bsp/meta-aspeed/meta-ast2400/recipes-kernel/linux/linux-obmc/defconfig[diff]
- meta-openbmc-bsp/meta-aspeed/meta-ast2500/recipes-kernel/linux/linux-obmc/defconfig[diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc.inc[diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc/0001-arm-dts-aspeed-Add-FSI-devices.patch[Deleted - diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc/0001-fsi-Match-fsi-slaves-engines-to-available-device-tre.patch[Deleted - diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc/0001-hwmon-Add-support-for-MAX31785-intelligent-fan-contr.patch[Deleted - diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc/linux-dev-4.10-1-3-drivers-fsi-sbefifo-Add-in-kernel-API.patch[Deleted - diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc/linux-dev-4.10-2-3-drivers-fsi-sbefifo-Add-OCC-driver.patch[Deleted - diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc/linux-dev-4.10-drivers-fsi-Add-FSI-SBEFIFO-driver.patch[Deleted - diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc/linux-dev-4.10-v2-1-6-drivers-i2c-Add-FSI-attached-I2C-master-algorithm.patch[Deleted - diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc/linux-dev-4.10-v2-2-6-drivers-i2c-Add-port-structure-to-FSI-algorithm.patch[Deleted - diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc/linux-dev-4.10-v2-3-6-drivers-i2c-Add-transfer-implementation-for-FSI-algorithm.patch[Deleted - diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc/linux-dev-4.10-v2-4-6-drivers-i2c-Add-I2C-master-locking-to-FSI-algorithm.patch[Deleted - diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc/linux-dev-4.10-v2-5-6-drivers-i2c-Add-bus-recovery-for-FSI-algorithm.patch[Deleted - diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc/v2-0001-arm-dts-aspeed-Add-missing-clock-sources-for-barr.patch[Deleted - diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc_4.10.bb[diff]
- import-layers/
- meta-openbmc-bsp/
- meta-openbmc-machines/
- meta-phosphor/
- bitbake ⇨ import-layers/yocto-poky/bitbake
- documentation ⇨ import-layers/yocto-poky/documentation
- LICENSE ⇨ import-layers/yocto-poky/LICENSE
- meta ⇨ import-layers/yocto-poky/meta
- meta-poky ⇨ import-layers/yocto-poky/meta-poky
- meta-selftest ⇨ import-layers/yocto-poky/meta-selftest
- meta-skeleton ⇨ import-layers/yocto-poky/meta-skeleton
- meta-yocto-bsp ⇨ import-layers/yocto-poky/meta-yocto-bsp
- oe-init-build-env ⇨ import-layers/yocto-poky/oe-init-build-env
- oe-init-build-env-memres ⇨ import-layers/yocto-poky/oe-init-build-env-memres
- scripts ⇨ import-layers/yocto-poky/scripts
- .gitignore
- .gitreview
- .templateconf
- openbmc-env
- README.md
OpenBMC
The OpenBMC project can be described as a Linux distribution for embedded devices that have a BMC; typically, but not limited to, things like servers, top of rack switches or RAID appliances. The OpenBMC stack uses technologies such as Yocto, Open-Embedded, Systemd and DBus to allow easy customization for your server 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 23
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake 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 variable known as TEMPLATECONF to be set to a hardware target. OpenBMC has placed all known hardware targets in a standard directory structure meta-openbmc-machines/meta-openpower/[company]/[target]. You can see all of the known targets with find meta-openbmc-machines -type d -name conf. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet
| Machine | TEMPLATECONF |
|---|---|
| Palmetto | meta-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf |
| Barreleye | meta-openbmc-machines/meta-openpower/meta-rackspace/meta-barreleye/conf |
| Zaius | meta-openbmc-machines/meta-openpower/meta-ingrasys/meta-zaius/conf |
| Witherspoon | meta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/conf |
As an example target Palmetto
export TEMPLATECONF=meta-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf
3) Build
. openbmc-env bitbake obmc-phosphor-image
Additional details can be found in the docs repository.
Build Validation and Testing
Commits submitted by members of the OpenBMC Github community are compiled and tested via our Jenkins 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 a arm-softmmu QEMU model against a barrage of CI tests.
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 for all automation. Our complete test repository can be found here.
Submitting Patches
Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.
Bug Reporting
Issues are managed on Github. It is recommended you search through the issues before opening a new one.
Finding out more
Dive deeper in to OpenBMC by opening the docs repository
Contact
- Mail: openbmc@lists.ozlabs.org https://lists.ozlabs.org/listinfo/openbmc
- IRC: #openbmc on freenode.net
- Riot: #openbmc:matrix.org