From owner-freebsd-arch@FreeBSD.ORG Wed Sep 20 06:43:00 2006 Return-Path: X-Original-To: freebsd-arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 571A716A415 for ; Wed, 20 Sep 2006 06:43:00 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77A9443D6B for ; Wed, 20 Sep 2006 06:42:59 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (rnjwfhehgl2tmk2i@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id k8K6gw2O052298 for ; Tue, 19 Sep 2006 23:42:59 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id k8K6gwNJ052297 for freebsd-arch@FreeBSD.org; Tue, 19 Sep 2006 23:42:58 -0700 (PDT) (envelope-from jmg) Date: Tue, 19 Sep 2006 23:42:58 -0700 From: John-Mark Gurney To: freebsd-arch@FreeBSD.org Message-ID: <20060920064258.GE23915@funkthat.com> Mail-Followup-To: freebsd-arch@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: Subject: PCI VPD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Sep 2006 06:43:00 -0000 I have made a patch exposes VPD information to devices so that they don't need to have their own implementation. The patch is available at: http://people.FreeBSD.org/~jmg/vpd.sk.patch It also makes sk use the VPD interface instead of hard coding the VPD cap register and rolling it's own code... This deals w/ two of the VPD capable devices that I have, one that has valid data (an sk card), and my DViCO FusionHDTV5 Lite card that has invalid VPD data... I haven't implemented writing to VPD data yet as I don't have a card that is capable. Comments? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."