From owner-p4-projects@FreeBSD.ORG Sat Feb 2 21:15:16 2008 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 2C88716A46C; Sat, 2 Feb 2008 21:15:16 +0000 (UTC) Delivered-To: perforce@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E74016A468; Sat, 2 Feb 2008 21:15:15 +0000 (UTC) (envelope-from hselasky@freebsd.org) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id E5D1B13C467; Sat, 2 Feb 2008 21:15:14 +0000 (UTC) (envelope-from hselasky@freebsd.org) X-Cloudmark-Score: 0.000000 [] Received: from [85.19.218.18] (account mc467741@c2i.net [85.19.218.18] verified) by mailfe07.swip.net (CommuniGate Pro SMTP 5.1.13) with ESMTPA id 790384774; Sat, 02 Feb 2008 22:00:13 +0100 From: Hans Petter Selasky To: Alfred Perlstein Date: Sat, 2 Feb 2008 22:01:07 +0100 User-Agent: KMail/1.9.7 References: <200712020001.lB201XbN000811@repoman.freebsd.org> <200802020818.57037.hselasky@freebsd.org> <20080202121301.GY99258@elvis.mu.org> In-Reply-To: <20080202121301.GY99258@elvis.mu.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802022201.08030.hselasky@freebsd.org> Cc: Perforce Change Reviews Subject: Re: PERFORCE change 129920 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2008 21:15:16 -0000 On Saturday 02 February 2008, Alfred Perlstein wrote: > * Hans Petter Selasky [080201 23:18] wrote: > > On Saturday 02 February 2008, Alfred Perlstein wrote: > > > This change makes very little sense. If xfer->frbuffers is a bare > > > pointer, then why add 0 to it? Just pass xfer->frbuffers or use a > > > macro that explains what you are doing. > > > > I can change those to a plain "xfer->frlengths". It was just a reminder > > for me, because some places we use "xfer->frlengths + 1" and > > "xfer->frbuffers + 1". > > > > I will write a script that converts all of those. > > What does '+ 1' mean? Is it something special like a channel or something? > > If so it should be a macro that's more descriptive. Hi, "frlengths" and "frbuffers" simply make up an I/O-vector. Usually all elements go the same direction, either IN or OUT relative to the USB Host. The exception is control transfers. These usually have three parts: < DATA IN or OUT > < STATUS direction is opposite of DATA stage> < [frlengths and frbuffers] + 0> < [frlenghts and frbuffers] + 1> < the STATUS does not have any frlenghts or frbuffers entry > --HPS