On Sat, 16 Nov 2002, Dan Kegel wrote:
> Alan Cox wrote:
> >>>Em Sat, Nov 16, 2002 at 04:04:05PM -0500, Jeff Garzik escreveu:
> >>>
> >>>>About the only thing WRT menuconfig I would be ok with is commenting out
> >>>>majorly broken drivers until they are fixed...
> >
> > Thats basically what "OBSOLETE" is
>
> So how 'bout this:
>
> * mark all drivers that don't compile OBSOLETE. That keeps us from
> trying to fix drivers without having hardware to test them.
> Anyone with proper hardware is invited to fix the drivers and then
> mark them non-OBSOLETE.
I would suggest that we not cause kconfig to attach a new, possibly
misleading, meaning to the terms OBSOLETE and BROKEN. Therefore I would
offer this nomenclature instead.
OBSOLETE - the code in question provides either support for a no longer
easily available hardware, or better software to support the hardware (or
feature) is available. It does not mean that the feature is known not to
work, just that there are alternatives.
BROKEN - the code in question is known not to work, may not compile. It
can be read as FIXME invitation.
Lots of people would immediately reject the idea of writing a driver from
scratch (including me, unless paid to do so), but at least some of those
who need working code might be willing to take the time to fix an existing
driver (or feature).
Two different concepts, and probably a good way to provide a quick "things
to do" list every time someone configures a kernel.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Nov 23 2002 - 22:00:24 EST