Re: 2.6 must-fix list, v2

Mike Anderson (andmike@us.ibm.com)
Tue, 13 May 2003 11:11:06 -0700


James Bottomley [James.Bottomley@steeleye.com] wrote:
> For SCSI, as far as the basics go we still have
>
> Need to convert to DMA-mapping:
>
> am53c974 dpt_i2o initio pci2220i
>
> Don't compile currently:
>
> inia100 cpqfc pci2000 dc390t
>
> Need converting to the new eh:
>
> wd33c99 based: a2091 a3000 gpv11 mvme174 sgiwd93
> 53c7xx based: amiga7xxx bvme6000 mvme16x
> initio am53c974 pci2000 pci2220i qla1280 sym53c8xx dc390t
>
> I think the sym53c8xx could probably be pulled out of the tree because
> the sym_2 replaces it. I'm also looking at converting the qla1280.
>

I would vote for sym_2 replacement. I have bug 647 that fails on
sym53c8xx but works on sym_2. The bug still has a rmmod problem which
maybe cleaned up with the cleanups in scsi-misc.

> It also might be possible to shift the 53c7xx based drivers over to
> 53c700 which does the new EH stuff, but I don't have the hardware to
> check such a shift.
>
> For the non-compiling stuff, I've probably missed a few that just aren't
> compilable on my platforms, so any updates would be welcome. Also, are
> some of our non-compiling or unconverted drivers obsolete?

I have the following not covered by your list above

qlogicisp (isp1020) - Convert to new eh and other issues. Could be
covered by feral driver, but status unclear of inclusion of feral.
Bug 140.

iph5526.c - Compile failure. Bug 201.

ini9100u.c - DMA-mapping conversion. Bug 213.

tmscsim.c - Compile failure. Bug 219.

AM53C974.c - Compile failure Bug 220.

An issue on fixing some of these is that lack of hardware,
documentation, or maintainer makes verification beyond compile difficult
(and just compile testing could lead to hidden data issues).

-andmike

--
Michael Anderson
andmike@us.ibm.com

- 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/