Hi all, currently we have a use-case on embedded Linux machine to set/get RTC clock params by using hwclock. The support for those set/get RTC params ioctl()s was introduced in mainline kernel v5.16 [1].
For example: $ hwclock --param-set bsm=0x2 $ hwclock --param-get bsm Since we are using busybox's hwclock implementation instead of util-linux's, we of-course cannot do that on that specific machine. We are also quite reluctant at the moment to switch to util-linux just to cover this specific use-case. On the other hand, util-linux got support for those set/get RTC params ioctl()s with [2]. So the questions are: 1) Does anyone perhaps already work on hwclock supporting set/get RTC params? 2) If we invest time implementing hwlock set/get RTC params, would you be willing to accept it? We would like to avoid developing a solution that won't be accepted into busybox upstream. 3) At this stage, looking at [2], do you see any potential issues when trying to support hwclock set/get RTC params on Busybox? Best regards, Primoz References: [1] https://lore.kernel.org/all/[email protected]/ [2] https://github.com/util-linux/util-linux/pull/1570 -- Primoz Fiser | phone: +386-41-540-545 <tel:+386-41-390-545> | ---------------------------------------------------------| Norik systems d.o.o. | https://www.norik.com | Your embedded software partner | email: [email protected] | Slovenia, EU | phone: +386-41-540-545 <tel:+386-41-540-545> |
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
