On 24/03/2020 17:33:00+0800, xiaolinkui wrote: > On 3/23/20 9:43 PM, Alexandre Belloni wrote: > > On 23/03/2020 20:43:39+0800, xiaolinkui wrote: > > > If the rtc driver is compiled into a module, hctosys can't > > > read the rtc clock during system startup. > > > The dmesg log will have the following information: > > > > > > [ 2.286512] hctosys: unable to open rtc device (rtc0) > > > > > > So the rtc driver configuration we need cannot be set to m. > > > > > Wow, you are not even trying, the solution is to not use hctosys. > > > > > Thank you for your reply. Yes, if we don't use hctosys, we won't have this > problem. But without hctosys, we cannot get the clock from rtc during > system startup. Is it wrong for the system time each time the system is > started for a machine without Internet access? > Your userspace can read the RTC and set the system time properly. -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
