From owner-freebsd-usb@FreeBSD.ORG  Sun Jan 28 10:21:04 2007
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
X-Original-To: freebsd-usb@freebsd.org
Delivered-To: freebsd-usb@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 6335B16A403
	for <freebsd-usb@freebsd.org>; Sun, 28 Jan 2007 10:21:04 +0000 (UTC)
	(envelope-from hselasky@c2i.net)
Received: from swip.net (mailfe06.swip.net [212.247.154.161])
	by mx1.freebsd.org (Postfix) with ESMTP id 0438913C46B
	for <freebsd-usb@freebsd.org>; Sun, 28 Jan 2007 10:21:03 +0000 (UTC)
	(envelope-from hselasky@c2i.net)
X-Cloudmark-Score: 0.000000 []
Received: from [193.217.102.48] (account mc467741@c2i.net HELO [10.0.0.249])
	by mailfe06.swip.net (CommuniGate Pro SMTP 5.0.12)
	with ESMTPA id 396648279; Sun, 28 Jan 2007 11:21:02 +0100
From: Hans Petter Selasky <hselasky@c2i.net>
To: freebsd-usb@freebsd.org
Date: Sun, 28 Jan 2007 11:20:39 +0100
User-Agent: KMail/1.9.5
References: <45bc10d0.uA36rj8LmuUpXUxA%perryh@pluto.rain.com>
In-Reply-To: <45bc10d0.uA36rj8LmuUpXUxA%perryh@pluto.rain.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200701281120.39855.hselasky@c2i.net>
Cc: 
Subject: Re: adding quirks to umass(4)
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Jan 2007 10:21:04 -0000

On Sunday 28 January 2007 03:56, perryh@pluto.rain.com wrote:
> I think I need to add a quirk entry to get umass(4) to handle my
> camera, but I haven't found any coverage of this in the handbook.
> Is there a "how to" somewhere (or is there something else I should
> be doing)?
>
> Upon connecting the camera, I get:
>
>   umass0: vendor 0x0784 product 0x4300, rev 1.10/3.00, addr 2
>   umass0: Get Max Lun not supported (SHORT_XFER)
>   umass0: Invalid CSW: sig 0x43425355 should be 0x53425355
>   umass0: Invalid CSW: sig 0x43425355 should be 0x53425355
>   umass0: Invalid CSW: sig 0x43425355 should be 0x53425355
>   umass0: Invalid CSW: sig 0x43425355 should be 0x53425355
>   umass0: Invalid CSW: sig 0x43425355 should be 0x53425355
>
> so I guess I need to set CAM_QUIRK_NOLUNS and something to adjust
> the sig.  This is on a Dell Optiplex GX1 with 6.1, and the camera
> is a Vivitar ViviCam 3825.

There is a quirk, WRONG_CSWSIG, that will fix this.

To me it seems like we should just accept both of these signatures, and avoid 
that growing quirk table.

--HPS