On 17. 3. 2020 17:39, Julio Faracco wrote:
> I'm good with that.
> I verified other resources that use rtc... they are checking for rtc0.
> Thanks, Michal
>
Cool, I've fixed patches (actually I did slightly change them to make it
easier to add new timer) and pushed.
Reviewed-by: Michal Privoznik
I'm good with that.
I verified other resources that use rtc... they are checking for rtc0.
Thanks, Michal
--
Julio Cesar Faracco
Em ter., 17 de mar. de 2020 às 12:32, Michal Prívozník
escreveu:
>
> On 17. 3. 2020 14:41, Julio Faracco wrote:
> > Hi Michal,
> >
> > /dev/rtc symlink is created by u
On 17. 3. 2020 14:41, Julio Faracco wrote:
> Hi Michal,
>
> /dev/rtc symlink is created by udev default rules.
> Maybe we can check for both: /dev/rtc and /dev/rtc0.
I think it's safe to rely on default udev behavior and just create rtc0.
What do you think? No need to send another version, I can
Hi Michal,
/dev/rtc symlink is created by udev default rules.
Maybe we can check for both: /dev/rtc and /dev/rtc0.
--
Julio Cesar Faracco
Em seg., 16 de mar. de 2020 às 15:16, Michal Prívozník
escreveu:
>
> On 2. 3. 2020 1:54, Julio Faracco wrote:
> > This commit share host Real Time Clock devi
On 2. 3. 2020 1:54, Julio Faracco wrote:
> This commit share host Real Time Clock device (rtc) into LXC containers
> to support hardware clock. This should be available setting up a `rtc`
> timer under clock section. Since this option is not emulated, it should
> be available only for `localtime` c
This commit share host Real Time Clock device (rtc) into LXC containers
to support hardware clock. This should be available setting up a `rtc`
timer under clock section. Since this option is not emulated, it should
be available only for `localtime` clock. This option should be readonly
due to secur
