From owner-freebsd-usb@FreeBSD.ORG Tue Apr 8 10:59:20 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5406C6E3 for ; Tue, 8 Apr 2014 10:59:20 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 174161258 for ; Tue, 8 Apr 2014 10:59:20 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id A13C81FE027; Tue, 8 Apr 2014 12:59:18 +0200 (CEST) Message-ID: <5343D6B6.9010802@selasky.org> Date: Tue, 08 Apr 2014 13:00:06 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Ivan Rokotov Subject: Re: Realtek SD Card Reader 0x0bda / 0x0129 detection? References: <53429E5F.1030407@selasky.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-usb@freebsd.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2014 10:59:20 -0000 On 04/08/14 02:33, Ivan Rokotov wrote: > 2014-04-07 16:47 GMT+04:00 Hans Petter Selasky : >> Hi, >> >> How did you add the quirk? > > Hi hps@, > > I added this to sys/dev/usb/usbdevs: > product REALTEK USB20CRW_T 0x0129 USB20CRW Card Reader > > and this to sys/dev/usb/quirk/usb_quirk.c > USB_QUIRK(REALTEK, USB20CRW_T, 0x0000, 0xffff, ), > > and recompiled my kernel. 'usbconfig' confirms that quirks were added, e.g. > > # usbconfig -d 1.4 dump_device_quirks | grep 0x0129 > VID=0x0bda PID=0x0129 REVLO=0x0000 REVHI=0xffff QUIRK=UQ_MSC_NO_SYNC_CACHE > > Changing quirks without recompiling kernel (simply using add_quirks > and then turning off/on the device) gave no visible effect, i.e. no > dmesg events. > Hi, Can you check using: usbdump -i usbusX -f Y -s 65536 -vvv what is going on with regards to USB communication towards your adapter? X and Y are the numbers after ugenX.Y for your device. --HPS