From sac-owner Mon Dec 4 21:31:49 2006 Received: from sunmail1brm.Central.Sun.COM (sunmail1brm.Central.Sun.COM [129.147.62.17]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id kB55VmKq006113 for ; Mon, 4 Dec 2006 21:31:48 -0800 (PST) Received: (from noaccess@localhost) by sunmail1brm.Central.Sun.COM (8.11.7p1+Sun/8.11.7/ENSMAIL,v2.2) id kB55VmZ25646 for one-pager-not-2b-used-directly; Mon, 4 Dec 2006 22:31:48 -0700 (MST) Received: from nwk-avmta-1.sfbay.sun.com (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail1brm.Central.Sun.COM (8.11.7p1+Sun/8.11.7/ENSMAIL,v2.2) with ESMTP id kB55VlS25640 for <@sunmail2.sfbay.sun.com:one-pager@sun.com>; Mon, 4 Dec 2006 22:31:47 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2 (built Dec 2 2004)) id <0J9S00K01COZXP00@nwk-avmta-1.sfbay.Sun.COM> for one-pager@sun.com (ORCPT one-pager@sun.com); Mon, 04 Dec 2006 21:31:47 -0800 (PST) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2 (built Dec 2 2004)) with ESMTP id <0J9S002DHCOZAS70@nwk-avmta-1.sfbay.Sun.COM> for one-pager@sun.com (ORCPT one-pager@sun.com); Mon, 04 Dec 2006 21:31:47 -0800 (PST) Received: from fe-amer-04.sun.com ([192.18.108.178]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id kB55Vkkh022374 for ; Mon, 04 Dec 2006 22:31:46 -0700 (MST) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0J9S00H01B6QPD00@mail-amer.sun.com> (original mail from Tarl.Neustaedter@Sun.COM) for one-pager@sun.com (ORCPT one-pager@sun.com); Mon, 04 Dec 2006 22:31:46 -0700 (MST) Received: from [129.148.9.94] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0J9S00GNMCOUOX32@mail-amer.sun.com> for one-pager@sun.com (ORCPT one-pager@sun.com); Mon, 04 Dec 2006 22:31:46 -0700 (MST) Date: Tue, 05 Dec 2006 00:31:41 -0500 From: Tarl Neustaedter Subject: [/]USB Binding update for Interface Associations Sender: Tarl.Neustaedter@Sun.Com To: one-pager@Sun.Com Message-id: <4575043D.8090802@sun.com> Organization: Sun Microsystems, Scalable Systems Group MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_taPlyMIGJpzuk3LpqagA8w)" X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 2.0b1 (X11/20061202) Status: RO Content-Length: 5351 This is a multi-part message in MIME format. --Boundary_(ID_taPlyMIGJpzuk3LpqagA8w) Content-type: text/plain; format=flowed; charset=ISO-8859-15 Content-transfer-encoding: 7BIT --Boundary_(ID_taPlyMIGJpzuk3LpqagA8w) Content-type: text/plain; name=onepager.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=onepager.txt Template Version: @(#)onepager.txt 1.30 06/09/28 SMI This information is Copyright 2006 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: USB Binding update for Interface Associations 1.2. Name of Document Author/Supplier: Gaopeng Chen, Tarl Neustaedter 1.3. Date of This Document: 11/30/2006 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: APAC 1.4.2. The ARC(s) you expect to review your project: FWARC 1.4.3. The Director/VP who is "Sponsoring" this project: Amiram Hayardeny 1.4.4. The name of your business unit: Software/Solaris. 1.5. Email Aliases: 1.5.1. Responsible Manager: Diana.Shi@sun.com 1.5.2. Responsible Engineer: Gaopeng.Chen@sun.com, Tarl.Neustaedter@sun.com 1.5.3. Marketing Manager: Patrick.Morrisey@sun.com 1.5.4. Interest List: usb-tech@sun.com 2. Project Summary 2.1. Project Description: Update USB binding to deal with Interface Associations, as defined by "Interface Association Descriptor Engineering Change Notice (ECN)", a modification to the USB 2.0 spec by the USB Consortium. See: http://www.usb.org/developers/docs/InterfaceAssociationDescriptor_ecn.pdf Interface Associations are a new concept in USB, defined by a new configuration entry. These group multiple interfaces in a single cluster for use by a single driver, which requires changes to the device tree structure for USB devices containing associations. 2.2. Risks and Assumptions: The new device tree structure could cause compatibility problems, but only when using a newer device (implementing an association) as a boot-device on older firmware. 3. Business Summary 3.1. Problem Area: Changing market conditions require us to change our structures so we will be able to implement drivers for newer USB devices. 3.2. Market/Requester: USB peripherals. 3.3. Business Justification: Without these structural changes, we would not be able to properly write drivers for newer USB devices. 3.4. Competitive Analysis: N/A. 3.5. Opportunity Window/Exposure: N/A. 3.6. How will you know when you are done?: When the device tree produced for a USB device with one or more interface associations is layered in such a form that drivers may be written to either the association or the individual interfaces. This modified device tree should appear for both OBP and Solaris. 4. Technical Description: 4.1. Details: Modifications in Solaris are largely confined to usba.c. Modifications in OBP are largely confined to hub probing. 4.2. Bug/RFE Number(s): CR 6463853 USB IAD should be supported in solaris 4.3. In Scope: 4.4. Out of Scope: 4.5. Interfaces: A third form of device-tree entry for USB devices is defined. Existing forms of device tree entry are: combined@port (e.g., keyboard@6) device@port/interface@number (e.g., device@3/input@1) A new form will be created for devices defining associations: device@port/association@number/interface@number e.g., device@6/ia@1/audio@1 device@6/ia@1/control@2 4.6. Doc Impact: Book: Writing Device Drivers. Man pages: usba(7D), usb_mid(7D), usb_ia(7D), usb_set_alt_if(9F) 4.7. Admin/Config Impact: The change should impact only pathnames displayed for interface-assocation devices. 4.8. HA Impact: None. 4.9. I18N/L10N Impact: None. 4.10. Packaging & Delivery: SUNWcsr and openboot.bin 4.11. Security Impact: None. 4.12. Dependencies: None. 5. Reference Documents: USB Interface Association ECN ( http://www.usb.org/developers/docs/InterfaceAssociationDescriptor_ecn.pdf ) USB Binding (supplied with this ARC case) USB 2.0 Specification ( http://www.usb.org/developers/docs/usb_20_05122006.zip ) USB DevClass documents ( http://www.usb.org/developers/devclass_docs/ ) USB Defined Classes ( http://www.usb.org/developers/defined_class ) 6. Resources and Schedule: 6.1. Projected Availability: Q3FY07 6.2. Cost of Effort: 1 Person-year (split between Solaris and Openboot). 6.3. Cost of Capital Resources: N/A. 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: USB Binding. 6.4.3. Type of CPT Review and Approval expected: FastTrack 6.4.4. Project Boundary Conditions: N/A 6.4.5. Is this a necessary project for OEM agreements: Not yet. 6.4.6. Notes: 6.4.7. Target RTI Date/Release: Q3FY07 6.4.8. Target Code Design Review Date: N/A 6.4.9. Update approval addition: N/A 6.5. ARC review type: FastTrack 7. Prototype Availability: 7.1. Prototype Availability: N/A 7.2. Prototype Cost: N/A --Boundary_(ID_taPlyMIGJpzuk3LpqagA8w)--