linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Luben Tuikov <luben_tuikov@adaptec.com>,
	Christoph Hellwig <hch@infradead.org>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>, linuxraid@amcc.com
Subject: Re: [PATCH] 3ware: use scsi_scan_target()
Date: Wed, 05 Oct 2005 15:24:30 -0400	[thread overview]
Message-ID: <4344286E.5090306@pobox.com> (raw)
In-Reply-To: <43442312.4030304@adaptec.com>

Luben Tuikov wrote:
> On 10/05/05 12:28, Christoph Hellwig wrote:
>>How does 3x-9xxx support luns?  From reading the

> AFAIR the firmware just exports the LUs.  The FW doesn't
> support REPORT LUNS; the LLDD exported LUs directly to SCSI Core.

Some 9xxx firmwares do support LUNs:

>         /* Check if this FW supports luns */
>         if ((SCpnt->device->lun != 0) && (tw_dev->working_srl < TW_FW_SRL_LUNS_SUPPORTED)) {

and the newer 9xxx are quite different from 3w-xxxx, because 9xxx 
firmware interface is largely just a execute-scsi-command message, 
rather than the translation stuff the goes on in 3w-xxxx.

As to Christoph's question, _how_ does the firmware support LUNs?  No 
idea.  It clearly does support it, though.

	Jeff



  parent reply	other threads:[~2005-10-05 19:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-04  0:57 [PATCH] 3ware: use scsi_scan_target() Jeff Garzik
2005-10-05 16:28 ` Christoph Hellwig
2005-10-05 19:01   ` Luben Tuikov
2005-10-05 19:20     ` adam radford
2005-10-05 19:24     ` Jeff Garzik [this message]
2005-10-05 19:34   ` Jeff Garzik
2005-10-05 23:19     ` Luben Tuikov
2005-10-07  1:07       ` James Bottomley
2005-10-07 21:36         ` Luben Tuikov
2005-10-08 14:30           ` James Bottomley
2005-10-09 16:25             ` Luben Tuikov
2005-10-10  5:05               ` Mike Anderson
2005-10-14 16:19                 ` Luben Tuikov
  -- strict thread matches above, loose matches on Subject: below --
2005-10-06 13:13 James.Smart
2005-10-06 18:09 ` Luben Tuikov

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=4344286E.5090306@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxraid@amcc.com \
    --cc=luben_tuikov@adaptec.com \
    /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).