Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / 7eb438a61ba2d5b3cc7f0ac3fea1ca2e47390529
commit7eb438a61ba2d5b3cc7f0ac3fea1ca2e47390529[log] [tgz]
authorAndrew Geissler <geissonator@yahoo.com>Mon Nov 30 19:53:16 2020 -0600
committerAndrew Geissler <geissonator@yahoo.com>Mon Nov 30 19:53:21 2020 -0600
treef3aee6c10811ebe6196859c998bd78d8dad36589
parenta59e4ee570958d218c22cd0513fbaefcf4a27563 [diff]
meta-xilinx: subtree update:874b9cee5e..569f52f275

Jaewon Lee (1):
      xilinx-board.inc: Introducing inc file to add BOARD/BOARD_VARIANT

Madhurkiran Harikrishnan (2):
      weston.ini: Do not set hard requirement for input devices
      libmali-xlnx: Update the mali userspace libraries to 2020.2

Mark Hatle (2):
      libmali-xlnx: Fix the package arch
      Various: Packages using libGL may need to be declared SOC_VARIANT_ARCH

Raju Kumar Pothuraju (1):
      versal-generic.conf:zynqmp-generic.conf: Add MACHINE_ESSENTIAL_EXTRA_RDEPENDS variable only for specific machines.

Sai Hari Chandana Kalluri (7):
      Add meta-python2 in bblayers.conf
      xrt_git.bb: Replace deprecated boost macros
      perf: Fix compilation issues Fix perf variable definition and libtraceevent with binutils. The above errors are fixed by including the following patches to the kernel tree: 	0001-libtraceevent-Fix-build-with-binutils-2.35.patch         0001-perf-bench-Share-some-global-variables-to-fix-build-.patch         0001-perf-cs-etm-Move-definition-of-traceid_list-global-v.patch         0001-perf-tests-bp_account-Make-global-variable-static.patch
      opencv_3.4.3: Remove support for opencv 3.4
      Update commit id and branch for components for 2020.2 release
      update XILINX_VER_MAIN to 2020.2
      bootgen: Update commit id for 2020.2 release

Sandeep Gundlupet Raju (1):
      kernel-module-dp: Add support for Xilinx DP drivers

Vishal Sagar (1):
      kernel-module-hdmi: Update commit id and license md5sum for 2020.2

ch vamshi krishna (3):
      updating xrt commit id
      updating final XRT commit id for 2020.2
      updating XRT/Zocl commit id for 2020.2

rbramand (1):
      ] CR-1076958 Put libxrt libs softlinks in the main package

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I4c6b12024c4d07388334e29177417e34fe6dea87
57 files changed
tree: f3aee6c10811ebe6196859c998bd78d8dad36589
  1. .github/
  2. meta-amd/
  3. meta-arm/
  4. meta-aspeed/
  5. meta-bytedance/
  6. meta-evb/
  7. meta-facebook/
  8. meta-google/
  9. meta-hpe/
  10. meta-hxt/
  11. meta-ibm/
  12. meta-ingrasys/
  13. meta-inspur/
  14. meta-intel/
  15. meta-inventec/
  16. meta-lenovo/
  17. meta-mellanox/
  18. meta-microsoft/
  19. meta-nuvoton/
  20. meta-openembedded/
  21. meta-openpower/
  22. meta-phosphor/
  23. meta-portwell/
  24. meta-qualcomm/
  25. meta-quanta/
  26. meta-raspberrypi/
  27. meta-security/
  28. meta-x86/
  29. meta-xilinx/
  30. meta-yadro/
  31. poky/
  32. bitbake ⇨ poky/bitbake/
  33. LICENSE ⇨ poky/LICENSE
  34. meta ⇨ poky/meta
  35. meta-poky ⇨ poky/meta-poky/
  36. meta-skeleton ⇨ poky/meta-skeleton
  37. oe-init-build-env ⇨ poky/oe-init-build-env
  38. scripts ⇨ poky/scripts/
  39. .gitignore
  40. .gitreview
  41. .templateconf
  42. MAINTAINERS
  43. openbmc-env
  44. README.md
  45. setup
README.md

OpenBMC

Build Status

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, OpenEmbedded, systemd, and D-Bus 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 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:

centriq2400-rep         nicole                     stardragon4800-rep2
f0b                     olympus                    swift
fp5280g2                olympus-nuvoton            tiogapass
gsj                     on5263m5                   vesnin
hr630                   palmetto                   witherspoon
hr855xg2                qemuarm                    witherspoon-128
lanyang                 quanta-q71l                witherspoon-tacoma
mihawk                  rainier                    yosemitev2
msn                     romulus                    zaius
neptune                 s2600wf

Once you know the target (e.g. romulus), source the setup script as follows:

. setup romulus build

For evb-ast2500, please use the below command to specify the machine config, because the machine in meta-aspeed layer is in a BSP layer and does not build the openbmc image.

TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf . openbmc-env

4) Build

bitbake obmc-phosphor-image

Additional details can be found in the 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

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 an 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.

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. Please review the discussion on Stack Overflow licensing before posting any code.

For technical discussions, please see contact info 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 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
  • Supreeth Venkatesh, Arm

Contact