public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: soma@cs.unm.edu (Anil B. Somayaji)
To: linux-kernel@vger.kernel.org
Subject: osst & ide-2.2.19 conflict?
Date: 23 Jun 2001 01:23:42 -0600	[thread overview]
Message-ID: <ut2lmmjek1t.fsf@lydia.adaptive.net> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In the ide.2.2.19.05042001 patch, there is the following bit of code
in ide-scsi.c, which prevents the ide-scsi driver from allowing access
to an OnStream DI-30 tape drive.  This is strange, since this same
drive can be used with the included ide-scsi + osst drivers in the
stock 2.2.19 kernel.  If you delete this bit, however, ide-scsi
recognizes the drive, and the osst driver seems to work fine.

Here's the offending code:

  #ifndef CONFIG_BLK_DEV_IDETAPE
   /*
    * The Onstream DI-30 does not handle clean emulation, yet.
    */
   if (strstr(drive->id->model, "OnStream DI-30")) {
           printk("ide-tape: ide-scsi emulation is not supported for %s.\n", drive->id->model);
           continue;
   }
  #endif /* CONFIG_BLK_DEV_IDETAPE */

Any reason for this to stay in the ide patch, or is it now obsolete?

  --Anil

- -- 
Anil Somayaji (soma@cs.unm.edu)
http://www.cs.unm.edu/~soma
+1 505 872 3150
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)

iEYEARECAAYFAjs0Q/UACgkQXOpXEmNZ3SfrogCfbNzSB7zOjkItzYTOoplxaJJt
5AYAnRrB+KGTYj7wf3/GeV92TLvpKGqi
=1TVG
-----END PGP SIGNATURE-----

             reply	other threads:[~2001-06-23  7:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-23  7:23 Anil B. Somayaji [this message]
2001-06-23 12:56 ` osst & ide-2.2.19 conflict? Willem Riede

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=ut2lmmjek1t.fsf@lydia.adaptive.net \
    --to=soma@cs.unm.edu \
    --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