| commit | 1d9800bc3d3d122d39e9a019f102852dc29dcf02 | [log] [tgz] |
|---|---|---|
| author | Joel Stanley <joel@jms.id.au> | Wed Nov 16 14:00:05 2016 +1030 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Nov 17 00:46:58 2016 +0000 |
| tree | 33327c551911dc8d840a7b5a435d6dc433680ad6 | |
| parent | b0960a5dba86a4c16dabf567556358910b5f4b4d [diff] |
Fix pflash PNOR access
pflash changes:
Move to latest upstream release of skiboot which includes the mtd erase
patch we were carrying. Adds a patch to fix parsing of the longer mtd
labels we have since updating the device tree bindings.
dev: size erasesize name
mtd0: 00060000 00001000 "u-boot"
mtd1: 00020000 00001000 "u-boot-env"
mtd2: 00280000 00001000 "kernel"
mtd3: 001c0000 00001000 "initramfs"
mtd4: 01740000 00001000 "rofs"
mtd5: 00400000 00001000 "rwfs"
mtd6: 02000000 00001000 "1e620000.flash-controller:flash@1"
mtd7: 08000000 00001000 "1e630000.flash-controller:pnor@0"
Linux kernel changes:
Three of the patches move the comaptible string for the bt interface to match
what we have sent upstream. There is also a dts change to the mtd nodes that
add back the 'pnor' label to the PNOR mtd device, as required by pflash.
Cédric Le Goater (2):
ipmi/bt-bmc: change compatible node to 'aspeed, ast2400-ibt-bmc'
ARM: dts: aspeed: fix flash module device nodes
Joel Stanley (2):
ipmi/bt-bmc: Add comaptible node for ast2500
arm: dts: aspeed: Use upstream comaptible string
Fixes openbmc/openbmc#785
Change-Id: If2c293b85075edcf3078ef599e7b61f3a6d77c66
Signed-off-by: Joel Stanley <joel@jms.id.au>
- meta-openbmc-machines/meta-openpower/common/recipes-bsp/skiboot/skiboot.inc[diff]
- meta-openbmc-machines/meta-openpower/common/recipes-bsp/skiboot/skiboot/0002-arch_flash_arm-Don-t-assume-mtd-partitions-are-short.patch[Added - diff]
- meta-openbmc-machines/meta-openpower/common/recipes-bsp/skiboot/skiboot/0002-external-common-Teach-ARM-code-to-erase-mtd-chips.patch[Deleted - diff]
- meta-phosphor/common/recipes-kernel/linux/linux-obmc_4.7.bb[diff]
4 files changed
tree: 33327c551911dc8d840a7b5a435d6dc433680ad6
- 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
README.md
OpenBMC
Building
OpenBMC uses Yocto/Open-Embedded for a build system, which supports an out-of-tree build. It is recommended that you create an empty directory somewhere to hold the build. This directory will get big.
On Ubuntu 14.04 the following packages are required to build the default target
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
On Fedora 23 the following packages are required to build the default target:
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake sudo dnf groupinstall "C Development Tools and Libraries"
To start a build:
cd <builddir> . <repodir>/openbmc-env bitbake obmc-phosphor-image