From owner-freebsd-current@FreeBSD.ORG Sun Mar 15 12:21:17 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7EC71065670 for ; Sun, 15 Mar 2009 12:21:16 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 5A31E8FC0A for ; Sun, 15 Mar 2009 12:21:16 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id A8AE573098; Sun, 15 Mar 2009 13:10:06 +0100 (CET) Date: Sun, 15 Mar 2009 13:10:06 +0100 From: Luigi Rizzo To: Ian Freislich Message-ID: <20090315121006.GA72445@onelab2.iet.unipi.it> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: Umass device doesn't work (didn't with old stack either) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Mar 2009 12:21:17 -0000 On Sun, Mar 15, 2009 at 01:32:10PM +0200, Ian Freislich wrote: > Hi > > I have a device that I'd very much like to get working. It didn't > work with the old USB stack, but HPS has been *very* much more > responsive so maybe there's hope. You can try sysutils/kdpatch to patch the quirks table for umass. As far as I can tell the table has the same format in usb2 and usb1 so the following should work: kldpatch umass.ko - @0 0x10d6 0x0000xxxx 0xffffffff 0x0201 0x4200 (replace xxxx with the usb product id for your device). 0x201 means use ATAPI commands over BBB protocol which is what your messages say. Perhaps 0x101 also works here. 0x4000 means the following: /* Device cannot handle a SCSI synchronize cache command. Normally * this quirk would be handled in the cam layer, but for IDE bridges * we need to associate the quirk with the bridge and not the * underlying disk device. This is handled by faking a success result. */ # define NO_SYNCHRONIZE_CACHE 0x4000 you may have to play with different flags and quirks to make the thing work. cheers luigi > On insert I get the followinng message: > > ugen0.3: at usbus0 > umass0: on usbus0 > umass0: 8070i (ATAPI) over Bulk-Only; quirks = 0x0000 > umass0:3:0:-1: Attached to scbus3 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 1.000MB/s transfers > da0: 499MB (1023713 512 byte sectors: 64H 32S/T 499C) > GEOM: da0: partition 1 does not start on a track boundary. > GEOM: da0: partition 1 does not end on a track boundary. > (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 > umass0: at uhub0, port 1, addr 3 (disconnected) > (da0:umass-sim0:0:0:0): lost device > (da0:umass-sim0:0:0:0): removing device entry > ugen0.3: at usbus0 (disconnected > > Ian > > -- > Ian Freislich > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"