On Sat, 15 Dec 2018 17:36:00 +0300
Andrew Savchenko wrote:
> Yes, it is. CONFIG_RTC_HCTOSYS (and CONFIG_RTC_SYSTOHC) is
> available in kernel for years and should be a preferred way to
> handle the clock.
>
> Best regards,
> Andrew Savchenko
AFAIK those options still don’t work with RTCs set to
Hi!
On Thu, 13 Dec 2018 12:18:26 -0600 William Hubbs wrote:
> All,
>
> the hwclock service is Linux specific, so all of this applies only to
> OpenRC on Linux.
>
> OpenRC currently adds the hwclock service to the boot runlevel upstream.
> The linux kernel also has had a way for some time to hand
On 15.12.2018 5:00, Georgy Yakovlev wrote:
> Hi,
>
> while lurking on bugzilla lately I noticed that package part of
> "emerge --info" output may be lacking in some cases.
>
> Good candidates for adding to that file are:
>
> virtual/rust
> llvm ?
> dev-util/meson
> dev-util/ninja
>
> that should
On Fri, 14 Dec 2018 15:04:22 +0100
Jeroen Roovers wrote:
> According to Nvidia these are former "Short Lived" branches that are no
> longer supported.
>
>
> # Jeroen Roovers (14 Dec 2018)
> # Deprecated short lived branches
> # https://www.nvidia.com/object/unix.html
> # File a bug report if y
On Fri, 14 Dec 2018 18:00:55 -0800
Georgy Yakovlev wrote:
> Good candidates for adding to that file are:
>
> virtual/rust
> llvm ?
> dev-util/meson
> dev-util/ninja
I'm really not sure these are widespread enough to justify putting
those details in the ouput of every emerge --info.
Instead, it
