Child pages (Children Display) |
---|
The RevPi kernel has been updated from version 5.10 to 6.1 . As the basis serves and is thus up to par again with the version used by RaspberryPi OS. It is based on version 6.1.46 of the stable kernel and version 6.1.46-rt13 of the real-time kernel patches. Beside general bug fixes and improvements in drivers and subsystems, the following has changed:TPM:
In the current kernel version, the TPM interrupt is now supported, so that the processor load is reduced when using the TPM. In addition, it is now ensured that the TPM chip is correctly removed from the reset during booting and correctly recognized when loading the driver.piControl:
The piControl kernel module has been largely reworked. Part of the previous functionality : A significant portion of it has been outsourced to a moved to an in-kernel driver that registers with the Linux kernel as a "serdev" device and handles all RS-485 communication via RS485 on the PiBridge. By default this driver is already included in This gets us one step closer to our long-term goal of upstreaming piControl into the mainline kernel.
The driver is compiled into the RevPi kernel, so as before only the piControl module needs to be loaded to communicate with the RevPi devices. When building your own kernel from our kernel source repository, the driver can optionally be built as an independent kernel module "pibridge.ko". For this the configuration parameter CONFIG_SERIAL_DEV_MUX_PIBRIDGE
must be changed from 'y' to 'm' in the kernel configuration. When using the pibridge driver as a standalone kernel module, it must be loaded before loading the piControl module.
By offloading the data traffic on the PiBridge the latencies One result of the reworked architecture is that latency for the communication with connected RevPi modules have has decreased, so that now shorter cycle times are achieved when querying and setting device statesstate.
TPM:
The TPM interrupt is now supported, so the processor load is reduced when using the TPM. In addition, it is now ensured that the TPM chip is correctly taken out of reset during booting and thus correctly recognized when loading the driver.
RTC:
The timestamping feature has been deactivated for the PCF2127. This avoids works around a hardware error erratum where a bit in one of the RTC interrupt registers was set by mistake during a warm restart. The errornoues erroneous set bit led to a malfunction of the watchdog on the Connect 4.