From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933120AbXC3Xf5 (ORCPT ); Fri, 30 Mar 2007 19:35:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933020AbXC3Xf4 (ORCPT ); Fri, 30 Mar 2007 19:35:56 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:37111 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932886AbXC3Xf4 (ORCPT ); Fri, 30 Mar 2007 19:35:56 -0400 Message-ID: <460D9ED9.1050801@garzik.org> Date: Fri, 30 Mar 2007 19:35:53 -0400 From: Jeff Garzik User-Agent: Thunderbird 1.5.0.10 (X11/20070302) MIME-Version: 1.0 To: Ed Lin CC: linux-scsi , linux-kernel , "james.Bottomley" , promise_linux Subject: Re: [PATCH 1/4] [SCSI]stex: fix id mapping issue References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.3 (----) X-Spam-Report: SpamAssassin version 3.1.8 on srv5.dvmed.net summary: Content analysis details: (-4.3 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Ed Lin wrote: > The internal id/lun mapping of st_vsc and st_vsc1 controllers is different > from st_shasta. The original driver code can only map first 16 'entities' > for st_vsc and st_vsc1 while there are actually 128 available. > > Also the ST_MAX_LUN_PER_TARGET should be 8, although this can do > no harm because inquiries beyond boundary are discarded by firmware. > > The correct internal mapping should be: > id:0~15, lun:0~7 (st_shasta) > id:0, lun:0~127 (st_yosemite) > id:0~127, lun:0 (st_vsc and st_vsc1) > To scsi mid layer they are all channel:0~7, id:0~15, lun:0, with a maximun > 'entity' number of 128. The RAID console only interfaces to scsi mid layer > and is always mapped at channel:0, id:16, lun:0. > > Signed-off-by: Ed Lin ACK patches 1-4. I presume James will apply them to scsi-fixes... Jeff