Hi,
Le 07/12/2018 à 14:04, Alexander Graf a écrit :
Am 07.12.2018 um 13:34 schrieb Guillaume GARDET <[email protected]>:
Hi,
On my Chromebook ARM, hctosys does not wait that /dev/rtc0 appears and fails on
rtc0 opening as it is not accessible at this point. See my dmesg:
[ 7.026205] hctosys: unable to open rtc device (rtc0)
[ 9.474121] max77686-rtc max77686-rtc: rtc core: registered max77686-rtc as
rtc0
The RTC appears 2.5 sec after hctosys failed. This is because i2c module is
needed and is loaded at this time.
Any idea how to fix/workaround that?
Are the drivers in the initrd? If not, maybe that helps.
I added i2c driver to initrd, RTC driver is already built-in. But it does not
help. The same problem appears earlier in the boot process.
BTW, we should be able to get time via EFI, no? Not sure what is the u-boot
support for this, though.
Guillaume
Alex
Thanks,
Guillaume
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
