Re: finding Tekram SCSI dc395U linux patch driver:

[Kurt Garloff]

--VZEZlOQeSr/zV9d3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Fri, Feb 16, 2001 at 06:27:20PM +0800, Thomas Lau wrote:
> Chmouel Boudjnah wrote:
> > Juergen Schoew <[e-mail]> writes:
> > > On 15-Feb-01 Thomas Lau wrote:
> > > > hey, I found this driver on mandrake kernel sources, it's ac3, but I
> > > > need ac14 code, also, why still not port this driver into kernel?
> > > > the patch file already released 1 years ago
> > >
> > > Have you checked http://www.garloff.de/kurt/linux/dc395/index.html
> > > there ist a driver Version 1.32 (2000-12-02).
> >
> > it's the version included with the mandrake kernel.
> 
> Well, I think it should add to normal kernel and do not need to patch, Thanks

No, it shouldn't.
Drivers normally get added to the mainstream kernel if the driver is stable
enough and somebody acting as maintainer requests to have it included. And,
then of course, Linus / Alan / ... need to accept it.

I'm maintaining this driver, but in spite of lots of requests to add it to
the mainstream kernels, I refused to do so. The reason is that some people
(ca. 5%) using this driver are having serious problems, which I have not
been able to track down so far. In the worst case, you can end up with data
corruption. (I could reproduce and fix some of the problems, but not the data
corruption one.) As that's not funny, I do not want the driver to be in the
mainstream kernel.

> also, why this driver still stick in ac3?

?

> and where can I find the new version of this patch?

My version is on
http://www.garloff.de/kurt/linux/dc395/

> I think mandrake was improved that driver, Thanks

I would be both amazed and pissed off if this would be the case.
Amazed because somebody was investing time to work on the driver and
potentially even fix problems. 
Pissed off, because I think it's very bad to fix problems and not submit 
the patches back to the official maintainers.

BTW, if somebody can provide a reasonable description of the chip
(TRM-S1040), the chances that I'd find the bug would increase a lot ...

Regards,
-- 
Kurt Garloff  <[e-mail]>                          Eindhoven, NL
GPG key: See mail header, key servers         Linux kernel development
SuSE GmbH, Nuernberg, FRG                               SCSI, Security

--VZEZlOQeSr/zV9d3
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6kpsAxmLh6hyYd04RAhgmAJ4rH+IK6Zr3w7GZAKrcM94mpjL31wCgrnQ4
oxmfNVu9tHhKVYyhW5pa1EE=
=gu9Z
-----END PGP SIGNATURE-----

--VZEZlOQeSr/zV9d3--