All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Aldo Gavioli <aldo.gavioli@netstorage.it>
Cc: linux-scsi@vger.kernel.org
Subject: Re: sd driver
Date: Tue, 24 May 2005 16:20:52 +1000	[thread overview]
Message-ID: <4292C7C4.2030204@torque.net> (raw)
In-Reply-To: <42919ABC.9030508@netstorage.it>

Aldo Gavioli wrote:
> Hello All,
> 
> Hello All,
> I'm trying to attach one proprietary SCSI driver for optical disk on 
> kernel 2.6.
> I noted that if sd attach the same device before, my driver will never 
> be called in the probe function. How can I by-pass this situation ?
> If anyone can help me I appreciate very much.

Aldo,
Upper Level Drivers (ULDs of which sd is one) discriminate
on the basis of the peripheral device type returned by an
INQUIRY. Currently sd_probe() takes control of TYPE_DISK
(pdt=0x0) and TYPE_MOD (pdt=0x7 "Optical memory device")
and will soon take control of TYPE_RBC.

If the class of devices you are interested in is TYPE_MOD
then (at least for testing) just comment out that bit of
code in sd_probe().

The st and osst (tape ULDs) co-operate to do a finer
grain division of labour (see their respective *_probe()
functions). These ULDs show you one way of solving the
problem. Another way would be a kernel/module option
to sd (and possibly other ULDs) telling it to leave
device <h,c,t,l> (or better some world wide unique
identifier) alone.


As for Arjan's comment about extending sd to cope with
your class of devices, recent experience with RBC devices
indicates that such a move may not add to the coherency
of the sd driver.

Doug Gilbert





  reply	other threads:[~2005-05-24  6:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23  8:56 sd driver Aldo Gavioli
2005-05-24  6:20 ` Douglas Gilbert [this message]
2005-05-24 11:58   ` Aldo Gavioli
2005-05-24 12:02     ` Arjan van de Ven
2005-05-24 12:21       ` Aldo Gavioli
  -- strict thread matches above, loose matches on Subject: below --
2005-05-23 15:39 Aldo Gavioli
2005-05-23 16:01 ` Arjan van de Ven
2005-05-24  0:49   ` Kumba
2005-05-24  2:41     ` randy_dunlap
2005-05-24  3:26       ` Kumba
2005-05-24  3:39         ` randy_dunlap

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=4292C7C4.2030204@torque.net \
    --to=dougg@torque.net \
    --cc=aldo.gavioli@netstorage.it \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.