From sacadmin Thu Jan 29 09:35:32 2009 Received: from tethys.sfbay.sun.com (tethys.SFBay.Sun.COM [129.146.226.92]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0THZWLf024832; Thu, 29 Jan 2009 09:35:32 -0800 (PST) Received: from tethys.sfbay.sun.com (localhost [127.0.0.1]) by tethys.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n0THUBDn000353; Thu, 29 Jan 2009 09:30:11 -0800 (PST) Received: (from jg@localhost) by tethys.sfbay.sun.com (8.14.3+Sun/8.14.3/Submit) id n0THUBcP000349; Thu, 29 Jan 2009 09:30:11 -0800 (PST) Date: Thu, 29 Jan 2009 09:30:11 -0800 (PST) From: Jerry Gilliam Message-Id: <200901291730.n0THUBcP000349@tethys.sfbay.sun.com> To: PSARC-record@sac.sfbay.sun.com Subject: prtconf PCI Vendor and Device Ids option [PSARC/2009/057 FastTrack timeout 02/05/2009] Status: RO Content-Length: 567 Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: prtconf PCI Vendor and Device Ids option 1.2. Name of Document Author/Supplier: Author: Judy Chen 1.3 Date of This Document: 29 January, 2009 4. Technical Description See the case directory for more detail 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From jg@jurassic.sfbay.Sun.COM Thu Jan 29 09:42:40 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0THge2Y025060 for ; Thu, 29 Jan 2009 09:42:40 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n0THgW6e056805; Thu, 29 Jan 2009 10:42:37 -0700 (MST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KE800F0DUJ06Y00@brm-avmta-1.central.sun.com>; Thu, 29 Jan 2009 10:42:36 -0700 (MST) Received: from jurassic.eng.sun.com ([129.146.106.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KE800A9IUIYM550@brm-avmta-1.central.sun.com>; Thu, 29 Jan 2009 10:42:35 -0700 (MST) Received: from tethys (tethys.SFBay.Sun.COM [129.146.226.92]) by jurassic.eng.sun.com (8.13.8+Sun/8.13.8) with SMTP id n0THgYe8134604; Thu, 29 Jan 2009 09:42:34 -0800 (PST) Date: Thu, 29 Jan 2009 09:37:13 -0800 (PST) From: Jerry Gilliam Subject: prtconf PCI Vendor and Device Ids option [PSARC/2009/057 02/05/2009] To: PSARC-ext@sun.com Cc: Judy.Chen@sun.com, Wesley.Shao@sun.com, pci-core@sun.com Reply-to: Jerry Gilliam Message-id: <200901291742.n0THgYe8134604@jurassic.eng.sun.com> MIME-version: 1.0 X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.7_98 SunOS 5.11 sun4u sparc Content-type: TEXT/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-MD5: 2kWX+SwyzGcL2sySYRFSbA== X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 8280 I am sponsoring the following case on behalf of Judy Chen and Wesley Shao as a fast-track, with timeout February 5, 2009. The project desires micro/patch binding. 1. Introduction 1.1. Project/Component Working Name: Add -d option for 'prtconf' 1.2. Name of Document Author/Supplier: Author: Judy Chen 1.3. Date of This Document: 29 July, 2008 4. Technical Description: 4.1. Overview This case proposes to provide a '-d' option for prtconf(1M) to print out vendor ID and device ID for PCI/PCI-X/PCIe devices. Release Binding requested is micro/patch. 4.2. Details Prtconf(1M) is often used to identify what devices are available on the system. For PCI/PCI-X/PCIe devices, vendor ID and device ID specify the manufactures of the device and are often checked to identify the device. But currently, prtconf(1M) only prints out PCI/PCI-X/PCIe devices' generic names (e.g. pci, network) as the node name on SPARC, and pci, on X86. To print out PCI/PCI-X/PCIe devices' vendor ID or device ID, one must run 'prtconf -pv' on SPARC and 'prtconf -v' on X86, then manually search and match through the device properties. This case proposes to provide a '-d' option for prtconf(1M) to print out below node name for PCI/PCI-X/PCIe device: , Sample output of prtconf(1M). - Output of prtconf(1M) without '-d' options * Generic name on SPARC: network, instance #0 * Subsystem vendor ID on X86: pci1028,214, instance #0 - Output of 'prtconf -d' * Actual PCI vendor ID and device ID on X86: pci1028,214 (pciex8086,105e), instance #0 * and on SPARC: network (pciex8086,105e), instance #0 4.3. Man Page Changes An updated prtconf(1M) man page included below. 4.4. Exported Interfaces ____________________________________________ | Interface | Classification | |_______________________|__________________| | /usr/sbin/prtconf -d | Committed | |_______________________|__________________| 6. Resources and Schedule: 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack prtconf(1M) System Administration Commands prtconf(1M) NAME prtconf - print system configuration SYNOPSIS ! /usr/sbin/prtconf [-V] | [-F] | [-x] | [-bpv] | [-acdDPv] ! [dev_path] DESCRIPTION The prtconf command prints the system configuration information. The output includes the total amount of memory, and the configuration of system peripherals formatted as a device tree. If a device path is specified on the command line for those command options that can take a device path, prtconf will only display informa- tion for that device node. OPTIONS The following options are supported: -a Display all the ancestors device nodes, up to the root node of the device tree, for the device specified on the command line. -b Display the firmware device tree root properties for the purpose of platform identification. These properties are "name", "compat- ible", "banner-name" and "model". -c Display the device subtree rooted at the device node specified on the command line, that is, display all the children of the device node specified on the command line. ! -d Display vendor ID and device ID for PCI and PCI Express devices ! in addition to the nodename. -D For each system peripheral in the device tree, displays the name of the device driver used to manage the peripheral. -F A SPARC-only option. Returns the device path name of the console frame buffer, if one exists. If there is no frame buffer, prtconf returns a non-zero exit code. This flag must be used by itself. It returns only the name of the console, frame buffer device or a non-zero exit code. For example, if the console frame buffer on a SUNW,Ultra-30 is ffb, the command returns: /SUNW,ffb@1e,0:ffb0. This option could be used to create a symlink for /dev/fb to the actual console device. -p Displays information derived from the device tree provided by the firmware (PROM) on SPARC platforms or the booting system on x86 platforms.The device tree information displayed using this option is a snapshot of the initial configuration and may not accurately reflect reconfiguration events that occur later. -P Includes information about pseudo devices. By default, informa- tion regarding pseudo devices is omitted. -v Specifies verbose mode. -V Displays platform-dependent PROM (on SPARC platforms) or booting system (on x86 platforms) version information. This flag must be used by itself. The output is a string. The format of the string is arbitrary and platform-dependent. -x Reports if the firmware on this system is 64-bit ready. Some existing platforms may need a firmware upgrade in order to run the 64-bit kernel. If the operation is not applicable to this platform or the firmware is already 64-bit ready, it exits silently with a return code of zero. If the operation is applica- ble to this platform and the firmware is not 64-bit ready, it displays a descriptive message on the standard output and exits with a non-zero return code. The hardware platform documentation contains more information about the platforms that may need a firmware upgrade in order to run the 64-bit kernel. This flag overrides all other flags and must be used by itself. OPERANDS The following operands are supported: dev_path The path to a target device minor node, device nexus node, or device link for which device node configuration informa- tion is displayed EXIT STATUS The following exit values are returned: 0 No error occurred. non-zero With the -F option (SPARC only), a non-zero return value means that the output device is not a frame buffer. With the -x option, a non-zero return value means that the firmware is not 64-bit ready. In all other cases, a non- zero return value means that an error occurred. ATTRIBUTES See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWesu | |Interface Stability |Unstable | +-----------------------------+-----------------------------+ SEE ALSO fuser(1M), modinfo(1M), sysdef(1M), attributes(5) Sun Hardware Platform Guide SPARC Only openprom(7D) NOTES The output of the prtconf command is highly dependent on the version of the PROM installed in the system. The output will be affected in poten- tially all circumstances. The driver not attached message means that no driver is currently attached to that instance of the device. In general, drivers are loaded and installed (and attached to hardware instances) on demand, and when needed, and may be uninstalled and unloaded when the device is not in use. On x86 platforms, the use of prtconf -vp provides a subset of informa- tion from prtconf -v. The value of integer properties from prtconf -vp might require byte swapping for correct interpretation. From cyril.plisko@gmail.com Thu Jan 29 10:04:32 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0TI4WwX025685 for ; Thu, 29 Jan 2009 10:04:32 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n0TI4Ta1022194; Thu, 29 Jan 2009 10:04:29 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KE800H0DVJF7100@brm-avmta-1.central.sun.com>; Thu, 29 Jan 2009 11:04:27 -0700 (MST) Received: from sca-ea-mail-2.sun.com ([192.18.43.25]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KE800A1QVJAM070@brm-avmta-1.central.sun.com>; Thu, 29 Jan 2009 11:04:27 -0700 (MST) Received: from relay14i.sun.com (ip124.net129179-4.block1.us.syntegra.com [129.179.4.124]) by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n0THeDPg025334; Thu, 29 Jan 2009 18:04:22 +0000 (GMT) Received: from mmp13es.mmp.us.syntegra.com ([160.41.208.13] [160.41.208.13]) by relay14i.sun.com with ESMTP id BT-MMP-3533277; Thu, 29 Jan 2009 18:04:22 +0000 (Z) Received: from relay14i.sun.com (relay14i.sun.com [129.179.4.124]) by mmp13es.mmp.us.syntegra.com with ESMTP id BT-MMP-136739; Thu, 29 Jan 2009 18:04:22 +0000 (Z) Received: from mail-fx0-f19.google.com ([209.85.220.19] [209.85.220.19]) by relay1i.sun.com with ESMTP id BT-MMP-35964022; Thu, 29 Jan 2009 18:04:21 +0000 (Z) Received: by fxm12 with SMTP id 12so11830fxm.8 for ; Thu, 29 Jan 2009 10:04:16 -0800 (PST) Received: by 10.181.60.13 with SMTP id n13mr103495bkk.92.1233252256454; Thu, 29 Jan 2009 10:04:16 -0800 (PST) Date: Thu, 29 Jan 2009 20:04:16 +0200 From: Cyril Plisko Subject: Re: prtconf PCI Vendor and Device Ids option [PSARC/2009/057 02/05/2009] In-reply-to: <200901291742.n0THgYe8134604@jurassic.eng.sun.com> Sender: cyril.plisko@gmail.com To: Jerry Gilliam Cc: PSARC-ext@sun.com, Wesley.Shao@sun.com, pci-core@sun.com, Judy.Chen@sun.com Message-id: MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=0FV0PjdindDYOLYIP6jWUXJ4aAddfoiq4hUnKxfrJ9c=; b=aLFJst+Lc7Pyy+0h2N+noHvtaIgv6LQET4FnqSXSYNQgC11Yo86XTAjCtduvg8b5cz I8ngNjvT1igtG/+B9phgmIzwyQb2NpVWh3ng6y62Vx9bbL75oc7N5v0JZ+TVs6sfropq w9JuGBJrxyn2aa1p7wusqwn65+PV60AP86xsI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=H1AarNBDcjUMP2nuyqjf8gsWZ4wLJBcMxsaoiGTjW14sQgft13m/XfENN9ZcvVOzQj iakB/4RzFKrf4p5bDlpMU2bv52rt5HLo8ym29+Go42qyFdWSHvCKNdo8bdH2A6s7Ylsn RxSI7vqZybd7r5XI+oUPD180FVns4c5SagDOE= X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Google-Sender-Auth: 0efadfc6e9fc55b5 X-Antispam: No, score=0.0/5.0, scanned in 0.050sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <200901291742.n0THgYe8134604@jurassic.eng.sun.com> Status: RO Content-Length: 861 On Thu, Jan 29, 2009 at 7:37 PM, Jerry Gilliam wrote: > > > - Output of 'prtconf -d' > * Actual PCI vendor ID and device ID on X86: > pci1028,214 (pciex8086,105e), instance #0 > * and on SPARC: > network (pciex8086,105e), instance #0 > I think that in many cases the next step would be to manually search in various tables what the actual device is. So why not do one more step and lookup these numbers in /usr/share/hwdata/pci.ids ? Perhaps, while combined with -v? I.e. - Output of 'prtconf -vd' * Actual PCI vendor ID and device ID on X86: pci1028,214 (pciex8086,105e [Intel 82571EB Gigabit Ethernet Controller]), instance #0 * and on SPARC: network (pciex8086,105e [Intel 82571EB Gigabit Ethernet Controller]), instance #0 -- Regards, Cyril From gdamore@sun.com Thu Jan 29 11:15:09 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0TJF9Y5027527 for ; Thu, 29 Jan 2009 11:15:09 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n0TJF207003887; Thu, 29 Jan 2009 11:15:09 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KE80041RYT8QO00@nwk-avmta-1.sfbay.Sun.COM>; Thu, 29 Jan 2009 11:15:08 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KE800AIBYT674C0@nwk-avmta-1.sfbay.Sun.COM>; Thu, 29 Jan 2009 11:15:08 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n0TJF61N017030; Thu, 29 Jan 2009 11:15:06 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KE800901Y6NFU00@fe-sfbay-09.sun.com> (original mail from gdamore@sun.com) ; Thu, 29 Jan 2009 11:15:06 -0800 (PST) Received: from [192.168.251.11] ([76.93.15.33]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KE8002YHYT5EJ20@fe-sfbay-09.sun.com>; Thu, 29 Jan 2009 11:15:05 -0800 (PST) Date: Thu, 29 Jan 2009 11:15:05 -0800 From: "Garrett D'Amore" Subject: Re: prtconf PCI Vendor and Device Ids option [PSARC/2009/057 02/05/2009] In-reply-to: Sender: Garrett.Damore@sun.com To: Cyril Plisko Cc: Jerry Gilliam , PSARC-ext@sun.com, Wesley.Shao@sun.com, pci-core@sun.com, Judy.Chen@sun.com Message-id: <49820039.20105@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200901291742.n0THgYe8134604@jurassic.eng.sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 1198 Cyril Plisko wrote: > On Thu, Jan 29, 2009 at 7:37 PM, Jerry Gilliam > wrote: > >> - Output of 'prtconf -d' >> * Actual PCI vendor ID and device ID on X86: >> pci1028,214 (pciex8086,105e), instance #0 >> * and on SPARC: >> network (pciex8086,105e), instance #0 >> >> > > I think that in many cases the next step would be to manually search > in various tables what the actual device is. So why not do one more > step and lookup these numbers in /usr/share/hwdata/pci.ids ? Perhaps, > while combined with -v? > > I.e. > > - Output of 'prtconf -vd' > > * Actual PCI vendor ID and device ID on X86: > pci1028,214 (pciex8086,105e [Intel 82571EB Gigabit Ethernet > Controller]), instance #0 > * and on SPARC: > network (pciex8086,105e [Intel 82571EB Gigabit Ethernet > Controller]), instance #0 > Seems like that overlaps with scanpci. If we could share the PCI id table between these projects, then I'd be happy. But I'm loathe to create yet another copy of the PCI ID mapping table that has to be maintained separately (and can get out of sync with the others.) -- Garrett From cyril.plisko@gmail.com Thu Jan 29 11:21:27 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0TJLQ2d027908 for ; Thu, 29 Jan 2009 11:21:26 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n0TJJoLT004708; Thu, 29 Jan 2009 19:21:22 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KE80050HZ3AFX00@nwk-avmta-1.sfbay.Sun.COM>; Thu, 29 Jan 2009 11:21:10 -0800 (PST) Received: from sca-ea-mail-3.sun.com ([192.18.43.21]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KE800A2PZ3974D0@nwk-avmta-1.sfbay.Sun.COM>; Thu, 29 Jan 2009 11:21:09 -0800 (PST) Received: from relay15i.sun.com (ip125.net129179-4.block1.us.syntegra.com [129.179.4.125]) by sca-ea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n0TJEbaZ004431; Thu, 29 Jan 2009 19:21:09 +0000 (GMT) Received: from mmp11es.mmp.us.syntegra.com ([160.41.208.11] [160.41.208.11]) by relay15i.sun.com with ESMTP id BT-MMP-3428944; Thu, 29 Jan 2009 19:21:08 +0000 (Z) Received: from relay12i.sun.com (relay12i.sun.com [129.179.4.122]) by mmp11es.mmp.us.syntegra.com with ESMTP id BT-MMP-3039922; Thu, 29 Jan 2009 19:21:08 +0000 (Z) Received: from fg-out-1718.google.com ([72.14.220.155] [72.14.220.155]) by relay1i.sun.com with ESMTP id BT-MMP-14026996; Thu, 29 Jan 2009 19:21:08 +0000 (Z) Received: by fg-out-1718.google.com with SMTP id e12so54100fga.6 for ; Thu, 29 Jan 2009 11:21:01 -0800 (PST) Received: by 10.180.218.15 with SMTP id q15mr116511bkg.194.1233256861222; Thu, 29 Jan 2009 11:21:01 -0800 (PST) Date: Thu, 29 Jan 2009 21:21:01 +0200 From: Cyril Plisko Subject: Re: prtconf PCI Vendor and Device Ids option [PSARC/2009/057 02/05/2009] In-reply-to: <49820039.20105@sun.com> Sender: cyril.plisko@gmail.com To: "Garrett D'Amore" Cc: Jerry Gilliam , PSARC-ext@sun.com, Wesley.Shao@sun.com, pci-core@sun.com, Judy.Chen@sun.com Message-id: MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=h33eprc4QCp/X3uX9YwsZ9IgPgvfo6eCNQMX/hHn7aE=; b=JsDM+NZQwDcubOhAck42APKEZFzIYkGDVSy1GmGwZPuLjy2OI7vkr9cvxyaJEX2EJo 58cbYXca4N7yAzvWFzTGTWOGCpTJbEoRZybi8WWgjqDkVxE+tMvOKLmfLgIxPeQ/4Oe9 oNef9wV+bD+zobpTI1pyMBwRGHaXCjcPEmutU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=TuEk0pvZK/Yeb2cIjfDe9p2LRbDnrAvFRjj/7a2w7dYj371PwyF7NqrjwKvtiKaEFW KNWBIoVo1yu9mah+iTiaUsASOgJplOLL4RC8KqNYX2DK7vqlDXoJLbAodzKXQyRQbX1S eEAzTPKdDxp7qJ0u4yrKPv3bLpg9tSEBoDDFk= X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Google-Sender-Auth: 8b02e66eb60bac88 X-Antispam: No, score=0.0/5.0, scanned in 0.061sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <200901291742.n0THgYe8134604@jurassic.eng.sun.com> <49820039.20105@sun.com> Status: RO Content-Length: 1463 On Thu, Jan 29, 2009 at 9:15 PM, Garrett D'Amore wrote: > Cyril Plisko wrote: >> >> On Thu, Jan 29, 2009 at 7:37 PM, Jerry Gilliam >> wrote: >> >>> >>> - Output of 'prtconf -d' >>> * Actual PCI vendor ID and device ID on X86: >>> pci1028,214 (pciex8086,105e), instance #0 >>> * and on SPARC: >>> network (pciex8086,105e), instance #0 >>> >>> >> >> I think that in many cases the next step would be to manually search >> in various tables what the actual device is. So why not do one more >> step and lookup these numbers in /usr/share/hwdata/pci.ids ? Perhaps, >> while combined with -v? >> >> I.e. >> >> - Output of 'prtconf -vd' >> >> * Actual PCI vendor ID and device ID on X86: >> pci1028,214 (pciex8086,105e [Intel 82571EB Gigabit Ethernet >> Controller]), instance #0 >> * and on SPARC: >> network (pciex8086,105e [Intel 82571EB Gigabit Ethernet >> Controller]), instance #0 >> > > Seems like that overlaps with scanpci. If we could share the PCI id table > between these projects, then I'd be happy. But I'm loathe to create yet > another copy of the PCI ID mapping table that has to be maintained > separately (and can get out of sync with the others.) > That's why I specifically mentioned /usr/share/hwdata/pci.ids. It is in this file where scanpci (libpciaccess to be more precise) gets all the info from. -- Regards, Cyril From Alan.Coopersmith@sun.com Thu Jan 29 11:28:50 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0TJSndX028155 for ; Thu, 29 Jan 2009 11:28:49 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n0TJSjtD010734; Thu, 29 Jan 2009 19:28:48 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KE80060FZFYDM00@nwk-avmta-1.sfbay.Sun.COM>; Thu, 29 Jan 2009 11:28:46 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KE800AZNZFX6NC0@nwk-avmta-1.sfbay.Sun.COM>; Thu, 29 Jan 2009 11:28:45 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n0TJSjFr018830; Thu, 29 Jan 2009 11:28:45 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KE800001Z4GB600@fe-sfbay-09.sun.com> (original mail from Alan.Coopersmith@Sun.COM); Thu, 29 Jan 2009 11:28:45 -0800 (PST) Received: from [10.6.102.118] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KE8002NIZFVEJ90@fe-sfbay-09.sun.com>; Thu, 29 Jan 2009 11:28:44 -0800 (PST) Date: Thu, 29 Jan 2009 11:28:43 -0800 From: Alan Coopersmith Subject: Re: prtconf PCI Vendor and Device Ids option [PSARC/2009/057 02/05/2009] In-reply-to: <49820039.20105@sun.com> Sender: Alan.Coopersmith@sun.com To: "Garrett D'Amore" Cc: Cyril Plisko , Jerry Gilliam , PSARC-ext@sun.com, Wesley.Shao@sun.com, pci-core@sun.com, Judy.Chen@sun.com Message-id: <4982036B.6060304@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 X-Enigmail-Version: 0.95.1 References: <200901291742.n0THgYe8134604@jurassic.eng.sun.com> <49820039.20105@sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20071119) Status: RO Content-Length: 889 Garrett D'Amore wrote: > Cyril Plisko wrote: >> >> I think that in many cases the next step would be to manually search >> in various tables what the actual device is. So why not do one more >> step and lookup these numbers in /usr/share/hwdata/pci.ids ? Perhaps, >> while combined with -v? > > Seems like that overlaps with scanpci. If we could share the PCI id > table between these projects, then I'd be happy. But I'm loathe to > create yet another copy of the PCI ID mapping table that has to be > maintained separately (and can get out of sync with the others.) That would share the mapping table, since scanpci was switched in PSARC 2008/638 from using it's own private mapping table to using /usr/share/hwdata/pci.ids (which HAL introduced in PSARC 2005/399). -- -Alan Coopersmith- alan.coopersmith@sun.com Sun Microsystems, Inc. - X Window System Engineering From gdamore@Sun.COM Thu Jan 29 11:35:09 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0TJZ8ha028576 for ; Thu, 29 Jan 2009 11:35:08 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n0TJZ5xO005118; Fri, 30 Jan 2009 03:35:07 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KE80030PZQGDT00@nwk-avmta-2.sfbay.sun.com>; Thu, 29 Jan 2009 11:35:04 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KE800H56ZQGZVC0@nwk-avmta-2.sfbay.sun.com>; Thu, 29 Jan 2009 11:35:04 -0800 (PST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n0TJZ4bW019803; Thu, 29 Jan 2009 11:35:04 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KE800G01ZL4QC00@fe-sfbay-09.sun.com> (original mail from gdamore@sun.com) ; Thu, 29 Jan 2009 11:35:04 -0800 (PST) Received: from [192.168.251.11] ([76.93.15.33]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KE8002R0ZQFEJC0@fe-sfbay-09.sun.com>; Thu, 29 Jan 2009 11:35:03 -0800 (PST) Date: Thu, 29 Jan 2009 11:35:03 -0800 From: "Garrett D'Amore" Subject: Re: prtconf PCI Vendor and Device Ids option [PSARC/2009/057 02/05/2009] In-reply-to: Sender: Garrett.Damore@Sun.COM To: Cyril Plisko Cc: Jerry Gilliam , PSARC-ext@Sun.COM, Wesley.Shao@Sun.COM, pci-core@Sun.COM, Judy.Chen@Sun.COM Message-id: <498204E7.8010604@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200901291742.n0THgYe8134604@jurassic.eng.sun.com> <49820039.20105@sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 1704 Cyril Plisko wrote: > On Thu, Jan 29, 2009 at 9:15 PM, Garrett D'Amore wrote: > >> Cyril Plisko wrote: >> >>> On Thu, Jan 29, 2009 at 7:37 PM, Jerry Gilliam >>> wrote: >>> >>> >>>> - Output of 'prtconf -d' >>>> * Actual PCI vendor ID and device ID on X86: >>>> pci1028,214 (pciex8086,105e), instance #0 >>>> * and on SPARC: >>>> network (pciex8086,105e), instance #0 >>>> >>>> >>>> >>> I think that in many cases the next step would be to manually search >>> in various tables what the actual device is. So why not do one more >>> step and lookup these numbers in /usr/share/hwdata/pci.ids ? Perhaps, >>> while combined with -v? >>> >>> I.e. >>> >>> - Output of 'prtconf -vd' >>> >>> * Actual PCI vendor ID and device ID on X86: >>> pci1028,214 (pciex8086,105e [Intel 82571EB Gigabit Ethernet >>> Controller]), instance #0 >>> * and on SPARC: >>> network (pciex8086,105e [Intel 82571EB Gigabit Ethernet >>> Controller]), instance #0 >>> >>> >> Seems like that overlaps with scanpci. If we could share the PCI id table >> between these projects, then I'd be happy. But I'm loathe to create yet >> another copy of the PCI ID mapping table that has to be maintained >> separately (and can get out of sync with the others.) >> >> > > That's why I specifically mentioned /usr/share/hwdata/pci.ids. It is > in this file where scanpci (libpciaccess to be more precise) gets all > the info from. > > Okay, I'll +1 the project -- either with the name mapping, or without. (It'd be nice to have it, but it isn't, IMO, absolutely critical.) -- Garrett From Nicolas.Williams@Sun.COM Thu Jan 29 11:47:57 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0TJluLU029066 for ; Thu, 29 Jan 2009 11:47:56 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n0TJloaj022683; Thu, 29 Jan 2009 19:47:52 GMT Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KE9004070BQFB00@brm-avmta-1.central.sun.com>; Thu, 29 Jan 2009 12:47:50 -0700 (MST) Received: from binky.Central.Sun.COM ([129.153.128.104]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KE90009D0BPSN20@brm-avmta-1.central.sun.com>; Thu, 29 Jan 2009 12:47:50 -0700 (MST) Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n0TJcvDj006375; Thu, 29 Jan 2009 13:38:57 -0600 (CST) Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n0TJcte9006374; Thu, 29 Jan 2009 13:38:55 -0600 (CST) Date: Thu, 29 Jan 2009 13:38:55 -0600 From: Nicolas Williams Subject: Re: prtconf PCI Vendor and Device Ids option [PSARC/2009/057 02/05/2009] In-reply-to: <498204E7.8010604@sun.com> To: "Garrett D'Amore" Cc: Cyril Plisko , Jerry Gilliam , PSARC-ext@Sun.COM, Wesley.Shao@Sun.COM, pci-core@Sun.COM, Judy.Chen@Sun.COM Message-id: <20090129193854.GU1044@Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200901291742.n0THgYe8134604@jurassic.eng.sun.com> <49820039.20105@sun.com> <498204E7.8010604@sun.com> X-Authentication-warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f User-Agent: Mutt/1.5.7i Status: RO Content-Length: 814 On Thu, Jan 29, 2009 at 11:35:03AM -0800, Garrett D'Amore wrote: > Cyril Plisko wrote: > >>>- Output of 'prtconf -vd' > >>> > >>>* Actual PCI vendor ID and device ID on X86: > >>> pci1028,214 (pciex8086,105e [Intel 82571EB Gigabit Ethernet > >>>Controller]), instance #0 > >>>* and on SPARC: > >>> network (pciex8086,105e [Intel 82571EB Gigabit Ethernet > >>>Controller]), instance #0 > > Okay, I'll +1 the project -- either with the name mapping, or without. > (It'd be nice to have it, but it isn't, IMO, absolutely critical.) I agree that "it'd be nice to have it" and that it's not critical from some p.o.v., but if there's no reason not to do it and if it would greatly improve the UI (IMO: yes, it would) then I think it should be done. Why should we be building non-user-friendly UIs?? From Wesley.Shao@sun.com Thu Jan 29 11:57:07 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0TJv65u029484 for ; Thu, 29 Jan 2009 11:57:07 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n0TJugD3028362; Thu, 29 Jan 2009 19:57:05 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KE90090R0R4WQ00@nwk-avmta-1.sfbay.Sun.COM>; Thu, 29 Jan 2009 11:57:04 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KE900AVI0R36MC0@nwk-avmta-1.sfbay.Sun.COM>; Thu, 29 Jan 2009 11:57:03 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n0TJv3jA019104; Thu, 29 Jan 2009 11:57:03 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KE900H010MHY100@fe-sfbay-10.sun.com> (original mail from Wesley.Shao@Sun.COM); Thu, 29 Jan 2009 11:57:03 -0800 (PST) Received: from [129.146.96.108] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KE900MHR0R3TS60@fe-sfbay-10.sun.com>; Thu, 29 Jan 2009 11:57:03 -0800 (PST) Date: Thu, 29 Jan 2009 11:56:45 -0800 From: Wesley Shao Subject: Re: prtconf PCI Vendor and Device Ids option [PSARC/2009/057 02/05/2009] In-reply-to: <20090129193854.GU1044@Sun.COM> Sender: Wesley.Shao@sun.com To: Nicolas Williams Cc: "Garrett D'Amore" , Cyril Plisko , Jerry Gilliam , PSARC-ext@sun.com, pci-core@sun.com, Judy.Chen@sun.com Message-id: <498209FD.8090508@sun.com> MIME-version: 1.0 Content-type: text/html; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200901291742.n0THgYe8134604@jurassic.eng.sun.com> <49820039.20105@sun.com> <498204E7.8010604@sun.com> <20090129193854.GU1044@Sun.COM> User-Agent: Thunderbird 2.0.0.20pre (X11/20090101) Status: RO Content-Length: 1634 Nicolas Williams wrote: 
On Thu, Jan 29, 2009 at 11:35:03AM -0800, Garrett D'Amore wrote:
  
Cyril Plisko wrote:
    
- Output of 'prtconf -vd'

* Actual PCI vendor ID and device ID on X86:
        pci1028,214 (pciex8086,105e [Intel 82571EB Gigabit Ethernet
Controller]), instance #0
* and on SPARC:
        network (pciex8086,105e [Intel 82571EB Gigabit Ethernet
Controller]), instance #0
          
Okay, I'll +1 the project -- either with the name mapping, or without.  
(It'd be nice to have it, but it isn't, IMO, absolutely critical.)
    

I agree that "it'd be nice to have it" and that it's not critical from
some p.o.v., but if there's no reason not to do it and if it would
greatly improve the UI (IMO: yes, it would) then I think it should be
done.

Why should we be building non-user-friendly UIs??
I guess we are going from counter intuitive to livable. Please file an RFE on this so we can go from livable to user friendly. I wonder if the PCI database parsing code can be leveraged.

Wes
From Nicolas.Williams@sun.com Thu Jan 29 12:07:13 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n0TK7DcR028541 for ; Thu, 29 Jan 2009 12:07:13 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n0TK74fs005240; Thu, 29 Jan 2009 12:07:11 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KE900B3X17J1Q00@nwk-avmta-1.sfbay.Sun.COM>; Thu, 29 Jan 2009 12:06:55 -0800 (PST) Received: from binky.Central.Sun.COM ([129.153.128.104]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KE900AMK17HF800@nwk-avmta-1.sfbay.Sun.COM>; Thu, 29 Jan 2009 12:06:53 -0800 (PST) Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n0TJw8da006399; Thu, 29 Jan 2009 13:58:08 -0600 (CST) Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n0TJw8tZ006398; Thu, 29 Jan 2009 13:58:08 -0600 (CST) Date: Thu, 29 Jan 2009 13:58:08 -0600 From: Nicolas Williams Subject: Re: prtconf PCI Vendor and Device Ids option [PSARC/2009/057 02/05/2009] In-reply-to: <498209FD.8090508@sun.com> To: Wesley Shao Cc: "Garrett D'Amore" , Cyril Plisko , Jerry Gilliam , PSARC-ext@sun.com, pci-core@sun.com, Judy.Chen@sun.com Message-id: <20090129195807.GX1044@Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200901291742.n0THgYe8134604@jurassic.eng.sun.com> <49820039.20105@sun.com> <498204E7.8010604@sun.com> <20090129193854.GU1044@Sun.COM> <498209FD.8090508@sun.com> X-Authentication-warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f User-Agent: Mutt/1.5.7i Status: RO Content-Length: 561 On Thu, Jan 29, 2009 at 11:56:45AM -0800, Wesley Shao wrote: > > I guess we are going from counter intuitive to livable. Please file an > RFE on this so we can go from livable to user friendly. I wonder if the > PCI database parsing code can be leveraged.
HTML e-mail on these lists is barely livable, and certainly not user friendly. Perhaps you were trying to emphasize your point! ;) IMO the ARC should put its foot down on this one, but I can only state my opinion. Cheers, Nico -- From jg@jurassic.sfbay.Sun.COM Mon Feb 9 18:30:27 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1A2UQrW003180 for ; Mon, 9 Feb 2009 18:30:27 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1A2ULEt003977; Tue, 10 Feb 2009 02:30:22 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KET00M07WAKJP00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 09 Feb 2009 18:30:20 -0800 (PST) Received: from jurassic.eng.sun.com ([129.146.106.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KET00EN9WAKII40@nwk-avmta-1.sfbay.Sun.COM>; Mon, 09 Feb 2009 18:30:20 -0800 (PST) Received: from tethys (tethys.SFBay.Sun.COM [129.146.226.92]) by jurassic.eng.sun.com (8.13.8+Sun/8.13.8) with SMTP id n1A2UK6h470657; Mon, 09 Feb 2009 18:30:20 -0800 (PST) Date: Mon, 09 Feb 2009 18:24:54 -0800 (PST) From: Jerry Gilliam Subject: Re: prtconf PCI Vendor and Device Ids option [PSARC/2009/057 02/05/2009] To: Judy.Chen@sun.com, Wesley.Shao@sun.com, pci-core@sun.com Cc: PSARC-ext@sun.com Reply-to: Jerry Gilliam Message-id: <200902100230.n1A2UK6h470657@jurassic.eng.sun.com> MIME-version: 1.0 X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.7_98 SunOS 5.11 sun4u sparc Content-type: TEXT/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-MD5: uxCxS2LshQ1I/yGl87eCcw== X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 57 This case has timed out and is thereby approved. -jg