Re: [rtc-linux] Re: [Bug 10866] /dev/rtc was missing until Idisabled CONFIG_RTC_CLASS

[Adrian Bunk]

On Sat, Jun 14, 2008 at 11:35:35AM +0200, Alessandro Zummo wrote:
> On Fri, 13 Jun 2008 15:38:54 -0700
> David Brownell <david-b@xxxxxxxxxxx> wrote:
> 
> > They can continue working just fine with *only* the legacy RTC.
> > If they stuck with defaults, no problems appear.  (Modulo the
> > fact that bitrot is setting in.)
> > 
> > The only thing that causes the least hiccup is someone who was
> > for a while using a bogus (and non-default) configuration.
> > 
> > Given a bogus configuration, how should it be fixed?  There
> > can be several solutions, and the right answer for one system
> > will always be the right one for another.  So any approach
> > that doesn't expect a human to select options sometimes will
> > be inherently wrong in various cases.
> 
>  I agree with david. oldconfig cannot be made to fix every possible
>  manual misconfiguration that has been introduced by the user, even
>  those that, by chance, just worked.
> 
>  The actual Kconfig will handle pretty well the transition from
>  a good config. where good is different from working-by-chance.
> 
>  There are far too many people that just keep pressing Y
>  when a new kernel option appears without even considering what would
>  happen or reading the help.

If Lior's problem was due to something like CONFIG_RTC_CLASS=y, 
CONFIG_RTC_DRV_CMOS=n that's a kernel configuration that would
anyway break when the old driver gets removed, and it just broke
earlier.

Everyone seems to focus on this kconfig related case, what about my 
point of no /dev/rtc with a static /dev ? When talking about existing 
setups and embedded systems that's a real issue for some systems.

>  Best regards,
> 
>  Alessandro Zummo,

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/