[RFC: 2.6 patch] no longer mark MTD_OBSOLETE_CHIPS as BROKEN and remove broken MTD_OBSOLETE_CHIPS drivers

On Mon, Dec 12, 2005 at 10:38:15AM +0100, David Woodhouse wrote:
> On Sun, 2005-12-11 at 20:31 +0100, Adrian Bunk wrote:
> > Either the depency of MTD_OBSOLETE_CHIPS on BROKEN is correct (in
> > which case CONFIG_MTD_OBSOLETE_CHIPS=y wouldn't bring you anything),
> > or the dependency on BROKEN is not correct and should be corrected.
> >
> > David, can you comment on this issue?
>
> I don't see any justification for MTD_OBSOLETE_CHIPS depending on
> BROKEN. That option covers a few of the obsolete chip drivers which
> people shouldn't be using any more -- and I'm perfectly willing to
> believe that one or two of those don't work any more, but if that's the
> case then those individual drivers ought to be marked BROKEN (or just
> removed). We shouldn't mark MTD_OBSOLETE_CHIPS broken.
>...

Two of them don't even compile any more.

The patch below removes them and all code depending on them and makes
the remaining one (MTD_SHARP) compilable again.

> dwmw2

cu
Adrian


<-- snip -->


MTD_OBSOLETE_CHIPS shouldn't be marked as BROKEN.

This patch brings the MTD_SHARP driver back into life and removes the
non-compiling MTD_AMDSTD and MTD_JEDEC with everything depending on
them.


Signed-off-by: Adrian Bunk <bunk@xxxxxxxxx>

<-- snip -->

Due to it's size, the patch is attached gzip'ed.

arch/cris/arch-v10/drivers/Kconfig | 1
arch/cris/arch-v10/drivers/axisflashmap.c | 3
arch/cris/arch-v32/drivers/Kconfig | 1
arch/cris/arch-v32/drivers/axisflashmap.c | 3
drivers/mtd/chips/Kconfig | 22
drivers/mtd/chips/Makefile | 2
drivers/mtd/chips/amd_flash.c | 1403 ----------------------
drivers/mtd/chips/jedec.c | 935 --------------
drivers/mtd/maps/Kconfig | 18
drivers/mtd/maps/Makefile | 2
drivers/mtd/maps/octagon-5066.c | 248 ---
drivers/mtd/maps/vmax301.c | 198 ---
include/linux/mtd/jedec.h | 66 -
13 files changed, 1 insertion(+), 2901 deletions(-)

Attachment:patch-MTD_OBSOLETE_CHIPS.gz
Description: Binary data

Relevant Pages

  • Re: Raid 0 X SCSI
    ... computer so I can't check but I'm sure it does both depending on what options you choose. ... If your RAID is hardware based and you have a bootable disk/cd with drivers that support it, then you can restore any image made by Ghost to ... It can also restore everything *but* the system partition within Windows - but that's still not a problem as the restoration environment is built on WinPE, so you have the opportunity to load RAID drivers during boot if required. ...
    (microsoft.public.windowsxp.hardware)
  • RE: IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH] for idle=C1halt, 2.6.5
    ... > I also recollect that Windows had lockups with nforce2 for a while ... Windows nForce IDE drivers that would cause lockups during boot for some ... people depending on what type of devices were attached. ...
    (Linux-Kernel)
  • Re: Killing a spawned program
    ... It is not a good idea to kill a process under Windows. ... Depending on which ... DLLs and drivers are used by the process being killed, ...
    (comp.lang.ada)
  • Re: Computer internet question
    ... depending on the version of windows you have, it will do it for you, ho w ... > will read what the hardware is so I can search for the correct drivers? ...
    (rec.gambling.poker)
  • Re: If / Else Code (hiding rows based on cell value)
    ... The verbiage in the letter varies depending on the industry type ... extra rows of blank space hidden depending on the value in J1. ... code written now, however, the next if statement overrides the previous ... couple of different ways but I just end up with compile errors. ...
    (microsoft.public.excel.programming)