Gitiles
Code Review Sign In
gerrit.openbmc.org / stefanberger / openbmc / aee56c5e5866fa2d6e2f810279654837a74c95a3
commitaee56c5e5866fa2d6e2f810279654837a74c95a3[log] [tgz]
authorJayanth Othayoth <ojayanth@in.ibm.com>Wed Aug 04 23:11:47 2021 -0500
committerJayanth Othayoth <ojayanth@in.ibm.com>Mon Aug 09 10:05:00 2021 -0500
treecef6f994fe61f8eb7de63d09131cb6317b354151
parentce7dbecf0facf092f488748b1d9bd7734b88c6d8 [diff]
ekb: srcrev bump 52e5c0038a..c14cb37697

Commit included.

  - Release tag & head commit information updated for hw071421a.opmst10 
  - Gard the clock on CBS_NOT_IN_IDLE_STATE error                       
  - SW528598 - Unmask MCFIR bit 5                                       
  - Supporing 48 bit target type for SBE FFDC                           
  - RAS Review: p10_do_fw_hb_istep.xml                                  
  - RAS Review: p10_ram_errors.xml                                      
  - RAS Review: p10_block_wakeup_intr_errors.xml                        
  - RAS Review: p10_qme_sram_access_errors.xml                          
  - RAS Review: p10_query_core_stop_state.xml                           
  - Release tag & head commit information updated for hw071221a.opmst10 
  - RAS Review: p10_scomt_errors.xml                                    
  - p10_fbc_eff_config -- calculate tsnoop based on core, mc, pau freqs 
  - RAS Review: p10_query_host_meminfo_errors.xml                       
  - p10_sbe_scrach_regs -- raise DD2 PAU frequency to support high frequency sorts
  - Define ATTR_MRW_FREQ_SYSTEM_CORE_FLOOR_MHZ for per system control   
  - RAS Review: p10_qme_customize_errors.xml                            
  - RAS Review - p10_tod                                                
  - Release tag & head commit information updated for hw070921a.opmst10 
  - Change MFG OMI screen test to use x4 downgrade                      
  - Add null pointer check to FFDC gathering functions                  
  - Release tag & head commit information updated for hw070721a.opmst10 
  - Minor attribute cleanup                                             
  - Minor attribute cleanup                                             
  - Add type for MDS Media Controller Device                            
  - Allow multicast targets for target ffdc in fapi error xml           
  - Add correct FFDC info for RNG regs                                  
  - Release tag & head commit information updated for hw070521a.opmst10 
  - p10_frequency_buckets -- adjust DDR 2933 mesh clock speed constant  
  - p10_mss_eff_grouping RAS updates                                    
  - Release tag & head commit information updated for hw063021a.opmst10 
  - Using uint8_t variable for CLOCK_POS FFDC                           
  - p10.pci.scan.initfile -- updates for HW 507934                      
  - P10 Dynamic VIO Setpoint                                            
  - Release tag & head commit information updated for hw062821a.opmst10 
  - Adding simple clock detector check                                  
  - Fix for defect SW521078                                             
  - QME: enable MMA dynamic mode                                        
  - Release tag & head commit information updated for hw062521a.opmst10 
  - PPB HWP: Bug fix in handling unsorted parts                         
  - P10 RAS Review io_init_done, io_lib, io_power, omi_init, omi_train_check
  - DD2 updates. For meas seeprom use bkp for all errors as upd is not possible
  - Release tag & head commit information updated for hw062321a.opmst10 
  - p10_sbe_gptr_time_initf -- swap PAUC DTS constants                  
  - Release tag & head commit information updated for hw062121a.opmst10 
  - Release tag & head commit information updated for hw061821a.opmst10 
  - DD2 ABUS CCM updates                                                
  - RCS Setup Updates

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: Ic5b7eb3eca9236d26979fc2e60d498f5e27d6032
1 file changed
tree: cef6f994fe61f8eb7de63d09131cb6317b354151
  1. .github/
  2. meta-alibaba/
  3. meta-amd/
  4. meta-ampere/
  5. meta-arm/
  6. meta-aspeed/
  7. meta-asrock/
  8. meta-bytedance/
  9. meta-evb/
  10. meta-facebook/
  11. meta-fii/
  12. meta-google/
  13. meta-hpe/
  14. meta-hxt/
  15. meta-ibm/
  16. meta-ingrasys/
  17. meta-inspur/
  18. meta-intel-openbmc/
  19. meta-inventec/
  20. meta-lenovo/
  21. meta-microsoft/
  22. meta-nuvoton/
  23. meta-openembedded/
  24. meta-openpower/
  25. meta-phosphor/
  26. meta-portwell/
  27. meta-qualcomm/
  28. meta-quanta/
  29. meta-raspberrypi/
  30. meta-security/
  31. meta-supermicro/
  32. meta-wistron/
  33. meta-x86/
  34. meta-xilinx/
  35. meta-yadro/
  36. poky/
  37. bitbake ⇨ poky/bitbake/
  38. LICENSE ⇨ poky/LICENSE
  39. meta ⇨ poky/meta
  40. meta-poky ⇨ poky/meta-poky/
  41. meta-skeleton ⇨ poky/meta-skeleton
  42. oe-init-build-env ⇨ poky/oe-init-build-env
  43. scripts ⇨ poky/scripts/
  44. .gitignore
  45. .gitreview
  46. .templateconf
  47. MAINTAINERS
  48. openbmc-env
  49. OWNERS
  50. README.md
  51. setup
README.md

OpenBMC

Build Status

OpenBMC is a Linux distribution for management controllers used in devices such as servers, top of rack switches or RAID appliances. It uses Yocto, OpenEmbedded, systemd, and D-Bus 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:

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

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

. setup romulus

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