LKML Archive on
help / color / mirror / Atom feed
From: "roland" <>
To: <>
Cc: <>
Subject: [RFC] - Schedule mcdx for removal ? was:  warning: #warning You have not edited mcdx.h
Date: Thu, 22 Mar 2007 10:14:18 +0100	[thread overview]
Message-ID: <052c01c76c62$78f7f7a0$eeeea8c0@aldipc> (raw)

anyway - i wonder if anybody is ever using 2.6.21+ on a system with one of 
those legacy mitsumi single-speed (LU-005/FX-001) and double-speed (FX-001D) 
cd-rom drives !?

iirc, these where the first drives available on the market (must have been 
around '94) and those were no ide/atapi compatible drives which had their 
own isa-bus controller.

i wonder if there still exist any of those devices in functional state in 
this world, at least not attached to some system being able to boot 
2.6.21+ - so, maybe mcdx driver is something for 
Documentation/feature-removal-schedule.txt , being removed in 2.6.25 or so 
after being announced for some time (i.e. driver telling "i will be gone 
soon, go spend those $15 to get a new drive") ?

not 100% sure here, but there really may be nobody to complain about 
removing this one.....


hey, i just read discussions about removing RAW driver, so if THAT being 
discussed for removal, this one probably should have been removed already ! 

----- Original Message ----- 
From: "roland" <>
To: <>
Cc: <>
Sent: Thursday, March 22, 2007 1:43 AM
Subject: warning: #warning You have not edited mcdx.h

> while looking at some more warnings i got with allyesconfig i came across 
> this really weird one:
> In file included from drivers/cdrom/mcdx.c:78:
> drivers/cdrom/mcdx.h:180:2: warning: #warning You have not edited mcdx.h
> drivers/cdrom/mcdx.h:181:2: warning: #warning Perhaps irq and i/o settings 
> are wrong.
> looking into the code :
> #ifndef I_WAS_HERE
> #ifndef MODULE
> #warning You have not edited mcdx.h
> #warning Perhaps irq and i/o settings are wrong.
> #endif
> #endif
> and before:
> /* *** make the following line uncommented, if you're sure,
> * *** all configuration is done */
> /* #define I_WAS_HERE */
> huh?
> is this file meant to be edited before compile ?
> searched the list and came across some patch from adrian bunk:
> [Patch] (new version) configure mcdx without editing mcdx.h
> at
> and
> and
> has this never been merged ?
> regards
> roland

             reply	other threads:[~2007-03-22  9:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22  9:14 roland [this message]
2007-03-22  9:35 ` Oliver Neukum
2007-03-23 22:59   ` roland
2007-03-23 23:09     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='052c01c76c62$78f7f7a0$eeeea8c0@aldipc' \ \ \ \
    --subject='Re: [RFC] - Schedule mcdx for removal ? was:  warning: #warning You have not edited mcdx.h' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).