From owner-freebsd-current@FreeBSD.ORG  Mon Mar 10 07:47:31 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 1033)
 id A8DC969D; Mon, 10 Mar 2014 07:47:31 +0000 (UTC)
Date: Mon, 10 Mar 2014 07:47:31 +0000
From: Alexey Dokuchaev <danfe@FreeBSD.org>
To: Kevin Lo <kevlo@FreeBSD.org>
Subject: Re: urtwn driver for Edimax EW-7811U WLAN nano USB Adapter
Message-ID: <20140310074731.GA55224@FreeBSD.org>
References: <201310081742.r98HfbBV055077@fire.js.berklix.net>
 <589BAB21-30E9-4750-A345-BE7AB1116F48@FreeBSD.org>
 <20140210122146.GA26853@FreeBSD.org> <531D6C9C.7010607@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <531D6C9C.7010607@FreeBSD.org>
User-Agent: Mutt/1.5.22 (2013-10-16)
Cc: "Julian H. Stacey" <jhs@berklix.com>, Alfred Perlstein <bright@mu.org>,
 Rui Paulo <rpaulo@FreeBSD.org>,
 "freebsd-current@freebsd.org bsd" <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Mar 2014 07:47:31 -0000

On Mon, Mar 10, 2014 at 03:41:16PM +0800, Kevin Lo wrote:
> On 2014/02/10 20:21, Alexey Dokuchaev wrote:
> >To augment this a bit: I also came across one of these dongles (vendor
> >0x0bda product 0x8176) that gave me this "timeout waiting for checksum
> >report" message.  Retrying didn't help, but plugging the dongle out and
> >then back in did.  After powercycling the machine, I had to replug it
> >again.  Once replugged, the dongle seems to work fine (I rebuilt kernel
> >and some ports via NFS over it thus far).
> >
> >This suggests that the driver (or more generic part of the USB stack)
> >does not initialize something correctly, while full plug-and-play thing
> >does it.  Any ideas?
> 
> We have to reset the bit of the R92C_MCUFWDL associated with checksum report
> before writing firmware.  Could you try this patch? Thanks.

Shit.  I'd like to help, but no longer have access to the dongle.  If I find
anything similar (or find a way to get access to original dongle remotely),
I'll let you know. :(

Thanks for working on these things Kevin, I appreciate it.

./danfe