Name Date Size #Lines LOC

..Today-

adcapp/H07-Mar-2021-1,301879

altitude/H05-Dec-2022-9671

autojson/H05-Dec-2022-1710

bbdbg/H08-Dec-2022-5645

bi2cp/H08-Dec-2022-478383

check_journal/H26-Jul-2024-10579

cla-signers/H07-Mar-2021-2111

dbus-pcap/H22-Dec-2023-626509

dbus-vis/H08-Dec-2022-5,4074,366

dbusView/H05-Dec-2022-10174

dbus_sensor_tester/H14-Jul-2023-303251

ddconvnotrunc/H08-Dec-2022-153112

expectedJsonChecker/H08-Dec-2022-344319

format-yaml/H08-Dec-2022-4733

i2c/H22-Mar-2024-9570

ipkdbg/H18-Mar-2024-755616

netboot/H08-Dec-2022-161128

openbmc-autobump/H26-Jan-2023-270193

openbmctool/H08-Dec-2022-29,16528,140

overlay/H08-Dec-2022-7362

pldm/H29-Jul-2021-1413

prepare-emmc-qemu/H16-Dec-2022-7963

pretty-journal/H05-Dec-2022-4633

pwmtachtool/H07-Mar-2021-1,7081,266

reboot/H07-Mar-2021-3520

reboot-ping-pong/H05-Dec-2022-200164

rootfs_size/H05-Dec-2022-3,5823,556

sensor_yaml_config/H08-Dec-2022-1,4881,378

tof-voters/H23-May-2023-552395

tracing/H08-Dec-2022-160129

witherspoon-debug/H08-Dec-2022-12696

.linter-ignoreH A D05-Dec-202227 21

.shellcheck-ignoreH A D06-Dec-2022207 1110

LICENSEH A D07-Mar-202111.1 KiB202169

OWNERSH A D22-Dec-20231.6 KiB4743

README.mdH A D08-Dec-20221.8 KiB5133

README.md

1# The OpenBMC Tools Collection
2
3The goal of this repository is to collect the two-minute hacks you write to
4automate interactions with OpenBMC systems.
5
6It's highly likely the scripts don't meet your needs - they could be
7undocumented, dysfunctional or utterly broken. Please help us improve!
8
9## Repository Rules
10
11- _Always_ inspect what you will be executing
12- Some hacking on your part is to be expected
13
14## If you're still with us
15
16Then this repository aims to be the default destination for your otherwise
17un-homed scripts. As such we are setting the bar for submission pretty low, and
18we aim to make the process as easy as possible.
19
20## Sending patches
21
22Please use gerrit for all patches to this repository:
23
24- [Gerrit](https://gerrit.openbmc-project.xyz/) Repository
25
26Do note that you will need to be party to the OpenBMC CLA before your
27contributions can be accepted. See [Gerrit Setup and CLA][1] for more
28information.
29
30## What we will do once we have your patches
31
32So long as your patches look sane with a cursory glance you can expect them to
33be applied. We may push back in the event that similar tools already exist or
34there are egregious issues.
35
36## What you must have in your patches
37
38We don't ask for much, but you need to give us at least a
39[Signed-off-by](https://developercertificate.org/), use SPDX markers in your
40source files and put your work under an Apache 2.0 compatible license.
41
42## How you consume the repository
43
44There's no standard way to install the scripts housed here, and adding parts of
45the repository to your PATH might be a bit of a dice-roll. We may also move or
46remove scripts from time to time as part of housekeeping. It's probably best to
47copy things out if you need stability.
48
49[1]:
50  https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#submitting-changes-via-gerrit-server
51