Re: [PATCH] Revert "hwclock-rtc.c: try the 'new' rtc class first"
Karel Zak <[email protected]>
| Newsgroups | org.kernel.vger.util-linux |
|---|---|
| Message-ID | <4cmotj2ocggd47627b4he7zs345dqi6zii7hfokvwscc43pwo7@sy4cmplnxk7d> |
On Mon, Mar 24, 2025 at 03:04:45PM +0100, Karel Zak wrote:
>
> Sorry, I somehow missed the PR on GitHub :-(
>
> On Wed, Mar 19, 2025 at 02:28:59PM +0100, Rasmus Villemoes wrote:
> > This (effectively) reverts commit
> > 1811900a91be856e794005511eac7859adb8e383.
> >
> > There was no real motivation given, and it certainly makes the default
> > behaviour of hwclock on current linux systems counter-intuitive: udev
> > has a standard rule so that whichever rtc device is designated as the
> > CONFIG_RTC_HCTOSYS_DEVICE one in the kernel configuration also becomes
> > the target of the /dev/rtc symlink. People may have some other way of
> > setting that symlink, but regardless, that must be considered the
> > primary or default rtc for the system.
>
> I agree that after 8 years, it's probably fine to use the /dev/rtc
> symlink as the first option and assume that udevd has done its job
> correctly. The current situation is somewhat messy.
>
> Let's CC: William who is author of the original patch.
Forgot the CC, fixed now,
Karel
--
Karel Zak <[email protected]>
http://karelzak.blogspot.com