Re: Kconfig RTC selection (was: 2.6.25-rc7: Ugh.)

Adrian Bunk
2008-03-28T21:06:55Z

On Fri, Mar 28, 2008 at 01:04:38PM -0700, David Brownell wrote:
> [ CC's trimmed a bit ]
>
> On Friday 28 March 2008, Mark Lord wrote:
> > > +# These legacy RTC drivers just cause too many conflicts with the generic
> > > +# RTC framework ... let's not even try to coexist any more.
> > ...
> >
> > Thanks, David.  Could you perhaps also update the option descriptions
> > to clearly indicate which set of RTCs are the new ones, and which are
> > the old ones that are going away someday?
>
> Hmm, I thought that would be clear from context.
> "These" (drivers/char) legacy RTC drivers (old),
> vs generic RTC framework (toplevel driver Kconfig).
>
> Admittedly the *previous* Kconfig was troublesome,
> at the UI level (vs. those comments outside the GUI).
>
>
> A more general issue seems to be what to do with
> those legacy RTC drivers. Few of them seem to
> have maintainers. I don't want to own them, and
> I doubt Alessandro does either. If their Kconfig
> is going to change, I'd rather just see them all
> flagged as deprecated ... with plans to delete them.
>
> The RTCs in question being:
>
> "RTC" ... replaced by new "rtc-cmos"
> --> ready to deprecate now ?

The only reason against killing it immediately seems to be SND_RTCTIMER.

> "JS_RTC" ... a SPARC32 thing
> --> bug?? no "js-rtc.c" in the tree! patch sent

Where's the bug?
js-rtc is built from rtc.c

>...
> "DS1302" ... M32R-specific, "rtc-ds1302" should replace it
> --> ready to deprecate now?
>...

Kconfig currently offers rtc-ds1302 only for an sh platform...

> - Dave

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