proc-driver-rtc

--proc-driver-rtcv1.0.0

Converts `/proc/driver/rtc` file to JSON

Linuxfileslurpable

$ jc-rs /proc/driver/rtc

A real pair

From the reference corpus (linux-proc/driver_rtc.json). The left pane is the input the fixture ships; the right pane is the corpus's expected JSON. CI compares jc-rs with it field by field under the published differential. Hover a value to see where it came from.

/proc/driver/rtclinux-proc

rtc_time	: 16:09:21
rtc_date	: 2022-09-03
alrm_time	: 00:00:00
alrm_date	: 2022-09-03
alarm_IRQ	: no
alrm_pending	: no
update IRQ enabled	: no
periodic IRQ enabled	: no
periodic IRQ frequency	: 1024
max user IRQ frequency	: 64
24hr		: yes
periodic_IRQ	: no
update_IRQ	: no
HPET_emulated	: yes
BCD		: yes
DST_enable	: no
periodic_freq	: 1024
batt_status	: okay

expected outputjson

{
  "rtc_time": "16:09:21",
  "rtc_date": "2022-09-03",
  "alrm_time": "00:00:00",
  "alrm_date": "2022-09-03",
  "alarm_IRQ": false,
  "alrm_pending": false,
  "update IRQ enabled": false,
  "periodic IRQ enabled": false,
  "periodic IRQ frequency": 1024,
  "max user IRQ frequency": 64,
  "24hr": true,
  "periodic_IRQ": false,
  "update_IRQ": false,
  "HPET_emulated": true,
  "BCD": true,
  "DST_enable": false,
  "periodic_freq": 1024,
  "batt_status": "okay"
}

Fixture coverage

1/1oracle-valid pairs match under the published structural JSON comparison

Magic syntax

jc-rs /proc/driver/rtcjc-rs reads this kernel-interface file directly and dispatches it through the matching /proc parser.

Source: crates/jc-rs-parsers/src/proc/proc_driver_rtc.rs. jc-rs targets the schemas defined by the original Python tool. Fixture coverage above is the measured evidence for this parser; test the inputs your pipeline depends on. Compare