Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc-tools / 47007c29c277a0861268cb639f516807b0e0deb7
commit47007c29c277a0861268cb639f516807b0e0deb7[log] [tgz]
authorChristian Geddes <crgeddes@us.ibm.com>Wed Jul 28 16:49:54 2021 -0500
committercrgeddes <crgeddes@us.ibm.com>Thu Jul 29 00:02:29 2021 +0000
treed4c40db71b1b5d03c8f6ce9e9488beeb5a57e50d
parent0b047c48ba61e5bef5ce984d7339d3ecf24e362f [diff]
Introduce pdrdump.sh

This script will walk the PDR repository using the pldmtool
and print all of the PDR details output to a text file.

Signed-off-by: Christian Geddes <crgeddes@us.ibm.com>
Change-Id: I413085b7e162085ca3f2ddde6e08d606bac7d100
1 file changed
tree: d4c40db71b1b5d03c8f6ce9e9488beeb5a57e50d
  1. adcapp/
  2. altitude/
  3. autojson/
  4. bi2cp/
  5. cla-signers/
  6. dbus-pcap/
  7. dbusView/
  8. ddconvnotrunc/
  9. expectedJsonChecker/
  10. format-yaml/
  11. maintainers/
  12. netboot/
  13. openbmc-autobump/
  14. openbmc-events/
  15. openbmctool/
  16. pldm/
  17. pretty-journal/
  18. pwmtachtool/
  19. reboot/
  20. reboot-ping-pong/
  21. rootfs_size/
  22. sensor_yaml_config/
  23. tracing/
  24. upload_and_update/
  25. witherspoon-debug/
  26. LICENSE
  27. MAINTAINERS
  28. README.md
README.md

The OpenBMC Tools Collection

The goal of this repository is to collect the two-minute hacks you write to automate interactions with OpenBMC systems.

It's highly likely the scripts don't meet your needs - they could be undocumented, dysfunctional or utterly broken. Please help us improve!

Repository Rules

  • Always inspect what you will be executing
  • Some hacking on your part is to be expected

If you're still with us

Then this repository aims to be the default destination for your otherwise un-homed scripts. As such we are setting the bar for submission pretty low, and we aim to make the process as easy as possible.

Sending patches

Please use gerrit for all patches to this repository:

Do note that you will need to be party to the OpenBMC CLA before your contributions can be accepted. See Gerrit Setup and CLA for more information.

What we will do once we have your patches

So long as your patches look sane with a cursory glance you can expect them to be applied. We may push back in the event that similar tools already exist or there are egregious issues.

What you must have in your patches

We don't ask for much, but you need to give us at least a Signed-off-by, use SPDX markers in your source files and put your work under an Apache 2.0 compatible license.

How you consume the repository

There's no standard way to install the scripts housed here, and adding parts of the repository to your PATH might be a bit of a dice-roll. We may also move or remove scripts from time to time as part of housekeeping. It's probably best to copy things out if you need stability.