linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ³¯¤ý®i <cwz@aic.ee.ndhu.edu.tw>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: About DC-315U scsi driver
Date: Tue, 13 Mar 2001 19:03:04 +0800	[thread overview]
Message-ID: <20010313190304.62fbf6c7.cwz@aic.ee.ndhu.edu.tw> (raw)
In-Reply-To: <20010312004401.H2697@garloff.casa-etp.nl>
In-Reply-To: <20010311163710.11a86b52.cwz@aic.ee.ndhu.edu.tw> <20010312004401.H2697@garloff.casa-etp.nl>

On Mon, 12 Mar 2001 00:44:01 +0100
Kurt Garloff <kurt@garloff.de> wrote:


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




   Today I try to recompiler a new kernel with integrated driver. And burn a test
CDR. The errors are still alive.

   The Driver from Tekram only support 2.2.x;I think that I cannot use it with 
2.4.2,is right?

   And I finally understand the readme which you wrote.
(I cannot found README.tmscsim at beginning)
 I try to lower the syncspeed, and it still has no help(8Mhz,5Mhz...).

echo "0 0 0 y n n  n n n -2 5 " > /proc/scsi/dc395x_trm/0
                   ^=======>>if I lower syncspeed and not set the DsCn=no
the system would  halt.

   I have no idea about why it is. :(  Now burning CDR is a nightmare.

Best Regards,cwz

  parent reply	other threads:[~2001-03-13 11:10 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
2001-03-12  0:15   ` Alan Cox
2001-03-13 11:03 ` ³¯¤ý®i [this message]
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=20010313190304.62fbf6c7.cwz@aic.ee.ndhu.edu.tw \
    --to=cwz@aic.ee.ndhu.edu.tw \
    --cc=linux-kernel@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).