From owner-svn-src-all@freebsd.org Tue May 3 11:49:30 2016 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFA9FB2B9C4; Tue, 3 May 2016 11:49:30 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9B28C1E92; Tue, 3 May 2016 11:49:30 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u43BnT6g014335; Tue, 3 May 2016 11:49:29 GMT (envelope-from pfg@FreeBSD.org) Received: (from pfg@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u43BnTeS014332; Tue, 3 May 2016 11:49:29 GMT (envelope-from pfg@FreeBSD.org) Message-Id: <201605031149.u43BnTeS014332@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: pfg set sender to pfg@FreeBSD.org using -f From: "Pedro F. Giffuni" Date: Tue, 3 May 2016 11:49:29 +0000 (UTC) To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r298976 - head/sys/dev/cxgbe/firmware X-SVN-Group: head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2016 11:49:30 -0000 Author: pfg Date: Tue May 3 11:49:29 2016 New Revision: 298976 URL: https://svnweb.freebsd.org/changeset/base/298976 Log: Revert r298955 for the cxgbe firmware. These files have checksums that are none of my business. Requested by: np Modified: head/sys/dev/cxgbe/firmware/t4fw_cfg_uwire.txt head/sys/dev/cxgbe/firmware/t5fw_cfg_fpga.txt head/sys/dev/cxgbe/firmware/t5fw_cfg_uwire.txt Modified: head/sys/dev/cxgbe/firmware/t4fw_cfg_uwire.txt ============================================================================== --- head/sys/dev/cxgbe/firmware/t4fw_cfg_uwire.txt Tue May 3 08:35:35 2016 (r298975) +++ head/sys/dev/cxgbe/firmware/t4fw_cfg_uwire.txt Tue May 3 11:49:29 2016 (r298976) @@ -17,7 +17,7 @@ # finite. This requires balancing the configuration/operation needs of # device drivers across OSes and a large number of customer application. # -# Some of the more important resources to allocate and their constraints are: +# Some of the more important resources to allocate and their constaints are: # 1. Virtual Interfaces: 128. # 2. Ingress Queues with Free Lists: 1024. PCI-E SR-IOV Virtual Functions # must use a power of 2 Ingress Queues. @@ -275,7 +275,7 @@ # to directly select the type of Physical Function to which they wish to be # attached. # -# Note that the actual values used for the PCI-E Intellectual Property will be +# Note that the actual values used for the PCI-E Intelectual Property will be # 1 less than those below since that's the way it "counts" things. For # readability, we use the number we actually mean ... # Modified: head/sys/dev/cxgbe/firmware/t5fw_cfg_fpga.txt ============================================================================== --- head/sys/dev/cxgbe/firmware/t5fw_cfg_fpga.txt Tue May 3 08:35:35 2016 (r298975) +++ head/sys/dev/cxgbe/firmware/t5fw_cfg_fpga.txt Tue May 3 11:49:29 2016 (r298976) @@ -17,7 +17,7 @@ # finite. This requires balancing the configuration/operation needs of # device drivers across OSes and a large number of customer application. # -# Some of the more important resources to allocate and their constraints are: +# Some of the more important resources to allocate and their constaints are: # 1. Virtual Interfaces: 128. # 2. Ingress Queues with Free Lists: 1024. PCI-E SR-IOV Virtual Functions # must use a power of 2 Ingress Queues. @@ -292,7 +292,7 @@ # to directly select the type of Physical Function to which they wish to be # attached. # -# Note that the actual values used for the PCI-E Intellectual Property will be +# Note that the actual values used for the PCI-E Intelectual Property will be # 1 less than those below since that's the way it "counts" things. For # readability, we use the number we actually mean ... # Modified: head/sys/dev/cxgbe/firmware/t5fw_cfg_uwire.txt ============================================================================== --- head/sys/dev/cxgbe/firmware/t5fw_cfg_uwire.txt Tue May 3 08:35:35 2016 (r298975) +++ head/sys/dev/cxgbe/firmware/t5fw_cfg_uwire.txt Tue May 3 11:49:29 2016 (r298976) @@ -18,7 +18,7 @@ # are finite. This requires balancing the configuration/operation needs of # device drivers across OSes and a large number of customer application. # -# Some of the more important resources to allocate and their constraints are: +# Some of the more important resources to allocate and their constaints are: # 1. Virtual Interfaces: 256. # 2. Ingress Queues with Free Lists: 1024. # 3. Egress Queues: 128K. @@ -309,7 +309,7 @@ # to directly select the type of Physical Function to which they wish to be # attached. # -# Note that the actual values used for the PCI-E Intellectual Property will be +# Note that the actual values used for the PCI-E Intelectual Property will be # 1 less than those below since that's the way it "counts" things. For # readability, we use the number we actually mean ... #