Date: Wed, 24 Jan 2007 23:47:11 -0800 From: perryh@pluto.rain.com To: freebsd-questions@freebsd.org Subject: umass(4) vs Vivitar USB camera Message-ID: <45b8607f.LBqpMn/1AZIiEUnl%perryh@pluto.rain.com> In-Reply-To: <44irfgtfy3.fsf@be-well.ilk.org> References: <45a1d35d.4bEc3ED%2BdOKSmi62%perryh@pluto.rain.com> <44irfgtfy3.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Does anyone happen to know where I would find a how-to for > > downloading and displaying images from a Vivitar ViviCam 3825? > > That camera seems to support umass(4), so just plug it in and use it > like a USB hard drive... It seems not to be quite that simple :( When I plug it in and turn it on, the console reports (on 6.1): 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 The "Invalid CSW" message appears to originate about 2/3 of the way into umass.c:umass_bbb_state(), and it looks as if there is a quirks mechanism to override it, but how do I go about configuring it? The handbook, umass(4), and "apropos quirks" all come up empty. In case it matters, this is the report when I turn it off: umass0: at uhub0 port 2 (addr 2) disconnected umass0: detached
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45b8607f.LBqpMn/1AZIiEUnl%perryh>