linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kurt Garloff <kurt@garloff.de>
To: ³¯¤ý®i <cwz@aic.ee.ndhu.edu.tw>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>,
	Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: About DC-315U scsi driver
Date: Mon, 12 Mar 2001 00:44:01 +0100	[thread overview]
Message-ID: <20010312004401.H2697@garloff.casa-etp.nl> (raw)
In-Reply-To: <20010311163710.11a86b52.cwz@aic.ee.ndhu.edu.tw>
In-Reply-To: <20010311163710.11a86b52.cwz@aic.ee.ndhu.edu.tw>; from cwz@aic.ee.ndhu.edu.tw on Sun, Mar 11, 2001 at 04:37:10PM +0800

[-- Attachment #1: Type: text/plain, Size: 2287 bytes --]

Hi,

On Sun, Mar 11, 2001 at 04:37:10PM +0800, ³¯¤ý®i wrote:
> The driver has not to be included in officeal kernel.

Yes, that's what I tell people that ask me to submit the driver from
inclusion. The reason are strange problems, which unfortunately I have not
been able to track down, yet. Fortunately, they don't happen for everyone.
Unfortunately, that means I can't reproduce most of them.

I added quite some debugging feature to the driver, like a complete history
of every SCSI command being kept and output if something goes wrong
(_abort()). I guess, a good chipset docu would give more insight.

> And the maintainer has not updated the driver from 2.4.0-test9-pre7.
> Maybe he is very busy.The last update is 2000-12-03.

I'm quite busy, that's true.
The driver 1.32 (Dec 3 2000) can be used with 2.4.2. Just ignore the
patch rejection in the file MAINTAINERS.

> I used some kernels from 2.4.0 to 2.4.2-ac17,and the driver always go wrong
> when I burn CDRs. Some files burned is different from the origin at HD.
> I use 2.2.17 with Tekram's driver,and nothing is wrong.

Indeed; people report more problems on 2.4 kernels than on 2.2 kernels. I
currently have no clue why.
Anyway, you can use the patch from 1.32 to have the driver integrated in the
2.4 kernel and the use the version from Tekram. (I believe they distribute
my version 1.27, but I didn't check fro quite some time.)
I would like to hear your results.

> I think the scsi layer maybe changed from 2.2.x,so the driver cannot run well.

It did change. For example the way SCSI devices are scanned fro changed from
T_U_R to INQUIRY. However, the driver has been changed to accept that.

> I am sure the hardware&software is ok,and no error messages about scsi
> found by me.
> 
> Can anyone do me a favor to modify the driver in order to suite the
> new kernel?

Compiling it should be no problem.
Making it work flawlessly is. I'd like to know as well.

Regards,
-- 
Kurt Garloff                   <kurt@garloff.de>         [Eindhoven, NL]
Physics: Plasma simulations  <K.Garloff@Phys.TUE.NL>  [TU Eindhoven, NL]
Linux: SCSI, Security          <garloff@suse.de>   [SuSE Nuernberg, FRG]
 (See mail header or public key servers for PGP2 and GPG public keys.)

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-03-11 23:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-11  8:37 About DC-315U scsi driver ³¯¤ý®i
2001-03-11 23:44 ` Kurt Garloff [this message]
2001-03-12  0:15   ` Alan Cox
2001-03-13 11:03 ` ³¯¤ý®i
2001-03-19 18:30   ` Pierre Etchemaite
2001-03-20  1:28   ` ³¯¤ý®i
2001-03-13  9:21 Quim K Holland
2001-03-16  0:36 About DC-315U SCSI driver ³¯¤ý®i

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=20010312004401.H2697@garloff.casa-etp.nl \
    --to=kurt@garloff.de \
    --cc=cwz@aic.ee.ndhu.edu.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).