From owner-freebsd-current@FreeBSD.ORG Mon Sep 22 06:42:08 2014 Return-Path: Delivered-To: freebsd-current@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 B0851D5C; Mon, 22 Sep 2014 06:42:08 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 6D542350; Mon, 22 Sep 2014 06:42:08 +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 F3B731FE027; Mon, 22 Sep 2014 08:42:05 +0200 (CEST) Message-ID: <541FC4B5.2030406@selasky.org> Date: Mon, 22 Sep 2014 08:41:57 +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: Kohji Okuno Subject: Re: Does the xHCI driver has a spec violation? References: <20140922.135800.1954695532570247771.okuno.kohji@jp.panasonic.com> <541FBB84.6050508@selasky.org> <20140922.153122.2173639902447525862.okuno.kohji@jp.panasonic.com> In-Reply-To: <20140922.153122.2173639902447525862.okuno.kohji@jp.panasonic.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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: Mon, 22 Sep 2014 06:42:08 -0000 On 09/22/14 08:31, Kohji Okuno wrote: > Hi HPS, > > Could you refer to the following document (4.6.6 Configure Endpoint:P.99)? > This document shows: > > If the Drop Context flag is `1' and the Add Context flag is `1', the xHC shall: > o Release the current Resources and Bandwidth allocated to the > endpoint and assign the new Resources and Bandwidth requested for > the endpoint. > Hi, I see. Then what is missing to your patch is to mask away bits 0 and 1, because those are reserved for D0 and D1 and should be zero? --HPS