From: Adrian Bunk <bunk@stusta.de>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Jean Delvare <khali@linux-fr.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] mark the mcd cdrom driver as BROKEN
Date: Tue, 1 Feb 2005 23:36:45 +0100 [thread overview]
Message-ID: <20050201223645.GA3258@stusta.de> (raw)
In-Reply-To: <41FF9F48.60008@tmr.com>
On Tue, Feb 01, 2005 at 10:24:56AM -0500, Bill Davidsen wrote:
> Adrian Bunk wrote:
> >On Sat, Jan 29, 2005 at 06:22:55PM +0100, Jean Delvare wrote:
> >
> >>Hi Adrian,
> >>
> >>
> >>>The mcd driver drives only very old hardware (some single and double
> >>>speed CD drives that were connected either via the soundcard or a
> >>>special ISA card), and the mcdx driver offers more functionality for
> >>>the same hardware.
> >>>
> >>>My plan is to mark MCD as broken in 2.6.11 and if noone complains
> >>>completely remove this driver some time later.
> >>>(...)
> >>>- depends on CD_NO_IDESCSI
> >>>+ depends on CD_NO_IDESCSI && BROKEN
> >>
> >>Shouldn't we introduce a DEPRECATED option for use in cases like this
> >>one?
> >
> >
> >We could.
> >
> >We could also list MCD in Documentation/feature-removal-schedule.txt
> >first.
> >
> >But in this case I doubt it makes any difference.
> >
> >This driver is for hardware where I doubt many users exist today, and it
> >should have been removed nearly ten years ago when the better mcdx
> >driver for the same now-obsolete hardware entered the kernel.
>
> I actually have one (or two) of these, but I agree that in this case it
> makes no difference. As a general thing I think DEPRECIATED would be
> useful for the case where there is a newer functional driver. The
> systems I have are unlikely to ever run a current kernel, so I am not
> affected, and I suspect most others who have this old stuff are running
> 2.0 or 2.2 kernels, also.
Are you using the mcd or the mcdx driver?
At 2.2 times, I also had such a drive.
But I didn't observe any need for the mcd driver that was already
outdated at that time.
The mcd driver should perhaps have been removed 10 years ago when the
mcdx driver was introduced. You could start today with deprecating the
mcd driver instead of a quick removal of this driver. But why? The
question is whether the number of people using one of these drives with
a 2.6 kernel is above zero or not - not whether we need one or two
drivers for them.
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
next prev parent reply other threads:[~2005-02-01 22:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3s4gX-P6-45@gated-at.bofh.it>
2005-01-29 17:22 ` [2.6 patch] mark the mcd cdrom driver as BROKEN Jean Delvare
2005-01-29 19:14 ` Adrian Bunk
2005-02-01 15:24 ` Bill Davidsen
2005-02-01 22:36 ` Adrian Bunk [this message]
2005-02-01 23:23 ` Bill Davidsen
2005-02-02 1:18 ` Kyle Moffett
2005-01-29 17:08 Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050201223645.GA3258@stusta.de \
--to=bunk@stusta.de \
--cc=davidsen@tmr.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox