Name |
Date |
Size |
#Lines |
LOC |
||
---|---|---|---|---|---|---|
.. | - | - | ||||
adcapp/ | H | - | - | 1,301 | 879 | |
altitude/ | H | - | - | 96 | 71 | |
autojson/ | H | - | - | 17 | 10 | |
bbdbg/ | H | - | - | 56 | 45 | |
bi2cp/ | H | - | - | 478 | 383 | |
check_journal/ | H | - | - | 105 | 79 | |
cla-signers/ | H | - | - | 21 | 11 | |
dbus-pcap/ | H | - | - | 626 | 509 | |
dbus-vis/ | H | - | - | 5,407 | 4,366 | |
dbusView/ | H | - | - | 101 | 74 | |
dbus_sensor_tester/ | H | - | - | 303 | 251 | |
ddconvnotrunc/ | H | - | - | 153 | 112 | |
expectedJsonChecker/ | H | - | - | 344 | 319 | |
format-yaml/ | H | - | - | 47 | 33 | |
i2c/ | H | - | - | 95 | 70 | |
ipkdbg/ | H | - | - | 755 | 616 | |
netboot/ | H | - | - | 161 | 128 | |
openbmc-autobump/ | H | - | - | 270 | 193 | |
openbmctool/ | H | - | - | 29,165 | 28,140 | |
overlay/ | H | - | - | 73 | 62 | |
pldm/ | H | - | - | 14 | 13 | |
prepare-emmc-qemu/ | H | - | - | 79 | 63 | |
pretty-journal/ | H | - | - | 46 | 33 | |
pwmtachtool/ | H | - | - | 1,708 | 1,266 | |
reboot/ | H | - | - | 35 | 20 | |
reboot-ping-pong/ | H | - | - | 200 | 164 | |
rootfs_size/ | H | - | - | 3,582 | 3,556 | |
sensor_yaml_config/ | H | - | - | 1,488 | 1,378 | |
tof-voters/ | H | - | - | 557 | 400 | |
tracing/ | H | - | - | 160 | 129 | |
witherspoon-debug/ | H | - | - | 126 | 96 | |
.linter-ignore | H A D | 04-Dec-2022 | 27 | 2 | 1 | |
.shellcheck-ignore | H A D | 06-Dec-2022 | 207 | 11 | 10 | |
LICENSE | H A D | 13-Oct-2017 | 11.1 KiB | 202 | 169 | |
OWNERS | H A D | 21-Dec-2023 | 1.6 KiB | 47 | 43 | |
README.md | H A D | 07-Dec-2022 | 1.8 KiB | 51 | 33 |
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