From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [RFC] qla4xxx: TODO for re-submission Date: Tue, 13 Jun 2006 00:31:36 -0400 Message-ID: <448E3FA8.4050309@garzik.org> References: <8889.1149988615@bebe.enoyolf.org> <448DACD5.6090205@cs.wisc.edu> <20060612211038.GB7555@ranandlinuxbox.qlogic.org> <448DDE31.2090300@cs.wisc.edu> <20060612224325.GK7555@ranandlinuxbox.qlogic.org> <20060613034851.320777@bebe.enoyolf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:42369 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S932865AbWFMEbr (ORCPT ); Tue, 13 Jun 2006 00:31:47 -0400 In-Reply-To: <20060613034851.320777@bebe.enoyolf.org> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Doug Maxey Cc: Mike Christie , Ravi Anand , David Somayajulu , Duane Grigsby , linux-scsi@vger.kernel.org Doug Maxey wrote: > Having a common solution (ala ethtool) for the user/admin, across all > SWI, all HBAs, and all distros would be optimal in my view. Although > the QLogic tools are out there, they only work AFAIK, for the other, > non-mainline drivers. It is enough pain to manage the targets, > making one end of the configuration common would be a big bonus. Why, in fact... that's the purpose of blktool :) Vendor-specific code in blktool is quite welcome. The general idea is to manage various vendor-specific capabilities which fit common patterns. git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/blktool.git http://sourceforge.net/projects/gkernel/ Jeff