From Artem.Kachitchkin@sun.com Tue Apr 28 15:07: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 n3SM7RYJ016751 for ; Tue, 28 Apr 2009 15:07:27 -0700 (PDT) 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 n3SM7Few007162; Tue, 28 Apr 2009 23:07:26 +0100 (BST) 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 <0KIU00J0904EYL00@nwk-avmta-1.sfbay.Sun.COM>; Tue, 28 Apr 2009 15:07:26 -0700 (PDT) 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 <0KIU00IW304DIU10@nwk-avmta-1.sfbay.Sun.COM>; Tue, 28 Apr 2009 15:07:25 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n3SM7PW8009920; Tue, 28 Apr 2009 15:07:25 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KIT00I00ZS7Y100@fe-sfbay-10.sun.com>; Tue, 28 Apr 2009 15:07:25 -0700 (PDT) Received: from [129.146.104.83] ([unknown] [129.146.104.83]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KIU004PF03DCJ60@fe-sfbay-10.sun.com>; Tue, 28 Apr 2009 15:06:58 -0700 (PDT) Date: Tue, 28 Apr 2009 15:07:45 -0700 From: Artem Kachitchkine Subject: PSARC/2009/266 Edgeport USB serial mode configuration Sender: Artem.Kachitchkin@sun.com To: PSARC-ext@sun.com Cc: usb-tech@sun.com Message-id: <49F77E31.6080204@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 User-Agent: Thunderbird 2.0.0.18 (X11/20081215) Status: RO Content-Length: 2365 I'm sponsoring this fasttrack for Guoqing Zhu. The timer is set for 05/06/2009. My understanding is that even though the initial delivery is for usbser_edge driver, the proposed interface can be adopted by other USB serial drivers and new modes added in the future. -Artem Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Edgeport USB serial mode configuration 1.2. Name of Document Author/Supplier: Author: Guoqing Zhu 1.3 Date of This Document: 28 April, 2009 4. Technical Description 4.1. Summary Support Edgeport USB serial devices RS232/422/485 mode switching mode via usbser_edge.conf. Requested binding: patch. 4.2 Details Most Edgeport USBSerial devices only work in RS232 mode, except that two Edgeport devices, Edgeport 4S and Edgeport 8S, can work in RS232/422/485 mode. But current usbser_edge driver only supports RS232 mode. There needs to be a way to configure which mode the device should operate in. We propose to create a new usbser_edge.conf property called portflag, a comma-separated string array, each string in the following format: "serialnumber=SerNum portnumber=PortNum mode=Mode" where: SerNum: USB serial number, can be obtained from the 'usb-serialno' property from prtconf(1M) output. PortNum: serial port number Mode - could be following strings corresponding to the modes supported by the device's firmware: RS232 RS422_NOTERM RS422_TERM RS485_HALF_ECHO_ENDUNIT RS485_HALF_NOECHO_ENDUNIT RS485_HALF_ECHO_MIDDLE RS485_HALF_NOECHO_MIDDLE RS485_FULL_MASTER_ENDUNIT RS485_FULL_SLAVE_ENDUNIT RS485_FULL_MASTER_MIDDLE RS485_FULL_SLAVE_MIDDLE For example, set device (SN: W84662767-0) port 0 to RS422_NOTERM mode: portflag= "serialnumber=W84662767-0 portnumber=0 mode=RS422_NOTERM"; 5. Interfaces Name | Classification | Description ----------+----------------+------------------------------- portflag | Stable | driver.conf property ----------+----------------+------------------------------- Requested binding: patch. 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 Andrew.Gabriel@sun.com Tue Apr 28 15:48:34 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 n3SMmXVW017512 for ; Tue, 28 Apr 2009 15:48:34 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3SMmQlF000993; Wed, 29 Apr 2009 06:48:32 +0800 (SGT) 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 <0KIU0020320UEM00@nwk-avmta-1.sfbay.Sun.COM>; Tue, 28 Apr 2009 15:48:30 -0700 (PDT) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KIU00IZ720TIV80@nwk-avmta-1.sfbay.Sun.COM>; Tue, 28 Apr 2009 15:48:30 -0700 (PDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n3SMmTxY027556; Tue, 28 Apr 2009 22:48:29 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KIU009001ZWG600@fe-emea-09.sun.com>; Tue, 28 Apr 2009 23:48:29 +0100 (BST) Received: from [81.187.162.109] ([unknown] [81.187.162.109]) by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KIU00DIM20M1W80@fe-emea-09.sun.com>; Tue, 28 Apr 2009 23:48:29 +0100 (BST) Date: Tue, 28 Apr 2009 23:49:56 +0100 From: Andrew Gabriel Subject: Re: PSARC/2009/266 Edgeport USB serial mode configuration In-reply-to: <49F77E31.6080204@sun.com> Sender: Andrew.Gabriel@sun.com To: Artem Kachitchkine Cc: PSARC-ext@sun.com, usb-tech@sun.com Message-id: <49F78814.3020309@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: <49F77E31.6080204@sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20090209) Status: RO Content-Length: 1614 I'm not a great fan of .conf configuration files. What about using an ioctl to select the mode after opening the device? Are there any already existing API's in other OS's to allow the application to select the mode it requires? It seems to me like that's the sort of thing an application might well pick out of its own config file (things like MASTER, SLAVE), and use to configure the port appropriately, which it wouldn't be able to do with .conf file configuration. An alternative might be providing additional minor unit number bits and suitable /dev entries (a bit like the /dev/cua no-modem-control devices, or the zs/zsh devices)? What does the API for a RS422/485 port look like? Is it the same as an RS232 port? Does having ldterm and ttcompat autopushed on make sense? Artem Kachitchkine wrote: > > I'm sponsoring this fasttrack for Guoqing Zhu. The timer is set for > 05/06/2009. > > My understanding is that even though the initial delivery is for > usbser_edge driver, the proposed interface can be adopted by other USB > serial drivers and new modes added in the future. > > -Artem > > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > Edgeport USB serial mode configuration > 1.2. Name of Document Author/Supplier: > Author: Guoqing Zhu > 1.3 Date of This Document: > 28 April, 2009 > 4. Technical Description > 4.1. Summary > > Support Edgeport USB serial devices RS232/422/485 mode switching mode > via usbser_edge.conf. -- Andrew From Guoqing.Zhu@sun.com Tue Apr 28 21:17:08 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 n3T4H8b2017545 for ; Tue, 28 Apr 2009 21:17:08 -0700 (PDT) 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 n3T4H78P018548; Tue, 28 Apr 2009 21:17:08 -0700 (PDT) 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 <0KIU00C0DH8J9500@brm-avmta-1.central.sun.com>; Tue, 28 Apr 2009 22:17:07 -0600 (MDT) Received: from dm-singapore-02.singapore.sun.com ([129.158.71.102]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KIU00EJAH8H1TC0@brm-avmta-1.central.sun.com>; Tue, 28 Apr 2009 22:17:06 -0600 (MDT) Received: from sin-eb-smtp-2.singapore (sineb-smtp-1.Singapore.Sun.COM [129.158.123.4]) by dm-singapore-02.singapore.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3T4H5ex017734; Wed, 29 Apr 2009 12:17:05 +0800 (SGT) Received: from phys-sedge1-1.singapore.sun.com (phys-sedge1-1.Singapore.Sun.COM [129.158.123.8]) by sin-eb-smtp-2.singapore (8.13.8+Sun/8.13.8) with ESMTP id n3T4GxbL005309; Wed, 29 Apr 2009 04:17:00 +0000 (GMT) Received: from [129.158.218.196] ([unknown] [129.158.218.196]) by sedge1-mail1.singapore.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPA id <0KIU004XXH8AZZ80@sedge1-mail1.singapore.sun.com>; Wed, 29 Apr 2009 12:17:00 +0800 (SGT) Date: Wed, 29 Apr 2009 12:13:34 +0800 From: guoqing zhu - Sun Microsystems - Beijing China Subject: Re: PSARC/2009/266 Edgeport USB serial mode configuration In-reply-to: <49F78814.3020309@sun.com> To: Andrew Gabriel Cc: Artem Kachitchkine , PSARC-ext@sun.com, usb-tech@sun.com Message-id: <49F7D3EE.3020606@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <49F77E31.6080204@sun.com> <49F78814.3020309@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080825) Status: RO Content-Length: 2431 Andrew Gabriel 写道: > I'm not a great fan of .conf configuration files. > > What about using an ioctl to select the mode after opening the device? There are some reasons why it does not use ioctl: 1. The mode configuration is a electric(physical) characteristics, which is transparent to software layer. All existing software APIs don't differentiate underlying physical transfer mode(RS232/422/485). 2. The mode configuration is dedicated to a special kind device(now is only for Edgeport), and it won't become a common property like other serial port device modes in software layer. 3. It is simple and easy to use, and don't need modify any existing software. If we use ioctl, all applications or drivers about USB serial perhaps need add a new ioctl and must set correct RS232/422/485 mode before transfering. > Are there any already existing API's in other OS's to allow the > application to select the mode it requires? It seems to me like that's > the sort of thing an application might well pick out of its own config > file (things like MASTER, SLAVE), and use to configure the port > appropriately, which it wouldn't be able to do with .conf file > configuration. > > An alternative might be providing additional minor unit number bits > and suitable /dev entries (a bit like the /dev/cua no-modem-control > devices, or the zs/zsh devices)? > > What does the API for a RS422/485 port look like? Is it the same as an > RS232 port? Does having ldterm and ttcompat autopushed on make sense? This mode configuration does not affect ldterm and ttcompat. Hope I described it clearly. Thanks Guoqing > > Artem Kachitchkine wrote: >> >> I'm sponsoring this fasttrack for Guoqing Zhu. The timer is set for >> 05/06/2009. >> >> My understanding is that even though the initial delivery is for >> usbser_edge driver, the proposed interface can be adopted by other >> USB serial drivers and new modes added in the future. >> >> -Artem >> >> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >> This information is Copyright 2009 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> Edgeport USB serial mode configuration >> 1.2. Name of Document Author/Supplier: >> Author: Guoqing Zhu >> 1.3 Date of This Document: >> 28 April, 2009 >> 4. Technical Description >> 4.1. Summary >> >> Support Edgeport USB serial devices RS232/422/485 mode switching mode >> via usbser_edge.conf. > From gdamore@sun.com Tue Apr 28 21:42:42 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3T4gfq7017685 for ; Tue, 28 Apr 2009 21:42:41 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3T4gf3g024950; Tue, 28 Apr 2009 21:42:41 -0700 (PDT) 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 <0KIU0050NIF1ZE00@nwk-avmta-2.sfbay.sun.com>; Tue, 28 Apr 2009 21:42:37 -0700 (PDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KIU0098MIF06KE0@nwk-avmta-2.sfbay.sun.com>; Tue, 28 Apr 2009 21:42:36 -0700 (PDT) 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 n3T4gaSp013574; Tue, 28 Apr 2009 21:42:36 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KIU00I00I9AD000@fe-sfbay-10.sun.com>; Tue, 28 Apr 2009 21:42:36 -0700 (PDT) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KIU00G1FIEZBR10@fe-sfbay-10.sun.com>; Tue, 28 Apr 2009 21:42:36 -0700 (PDT) Date: Tue, 28 Apr 2009 21:42:35 -0700 From: "Garrett D'Amore" Subject: Re: PSARC/2009/266 Edgeport USB serial mode configuration In-reply-to: <49F7D3EE.3020606@sun.com> Sender: Garrett.Damore@sun.com To: guoqing zhu - Sun Microsystems - Beijing China Cc: Andrew Gabriel , Artem Kachitchkine , PSARC-ext@sun.com, usb-tech@sun.com Message-id: <49F7DABB.9060001@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <49F77E31.6080204@sun.com> <49F78814.3020309@sun.com> <49F7D3EE.3020606@sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 3537 Didn't we just see a different case for usb configuration using .conf properties? I'm *really* not a fan of inconsistent property handling -- magic encoded strings like what is proposed here for portflag seems,... ugly. Is there a reason why driver/instance number are inadequate to properly identify a usb device in driver.conf? (usb(4) sheds no light on how usb properties work.) It does seem that perhaps an SMF property or something like what Brussels does for NIC drivers is called for here. "portflag" as specified looks like a call generator, and a "hack". Perhaps another approach would be to have a utility that can issue ioctls against the driver to change its "mode". This can be done once at start of day (or before first use by other applications) without requiring other consuming applications to be changed. (Although this might pose challenges for uses where the device is the serial console for the system in question.) -- Garrett guoqing zhu - Sun Microsystems - Beijing China wrote: > Andrew Gabriel 写道: >> I'm not a great fan of .conf configuration files. >> >> What about using an ioctl to select the mode after opening the device? > There are some reasons why it does not use ioctl: > 1. The mode configuration is a electric(physical) characteristics, > which is transparent to software layer. All existing software APIs > don't differentiate underlying physical transfer mode(RS232/422/485). > 2. The mode configuration is dedicated to a special kind device(now is > only for Edgeport), and it won't become a common property like other > serial port device modes in software layer. > 3. It is simple and easy to use, and don't need modify any existing > software. If we use ioctl, all applications or drivers about USB > serial perhaps need add a new ioctl and must set correct RS232/422/485 > mode before transfering. >> Are there any already existing API's in other OS's to allow the >> application to select the mode it requires? It seems to me like >> that's the sort of thing an application might well pick out of its >> own config file (things like MASTER, SLAVE), and use to configure the >> port appropriately, which it wouldn't be able to do with .conf file >> configuration. >> >> An alternative might be providing additional minor unit number bits >> and suitable /dev entries (a bit like the /dev/cua no-modem-control >> devices, or the zs/zsh devices)? >> >> What does the API for a RS422/485 port look like? Is it the same as >> an RS232 port? Does having ldterm and ttcompat autopushed on make sense? > This mode configuration does not affect ldterm and ttcompat. > Hope I described it clearly. > > Thanks > Guoqing >> >> Artem Kachitchkine wrote: >>> >>> I'm sponsoring this fasttrack for Guoqing Zhu. The timer is set for >>> 05/06/2009. >>> >>> My understanding is that even though the initial delivery is for >>> usbser_edge driver, the proposed interface can be adopted by other >>> USB serial drivers and new modes added in the future. >>> >>> -Artem >>> >>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>> This information is Copyright 2009 Sun Microsystems >>> 1. Introduction >>> 1.1. Project/Component Working Name: >>> Edgeport USB serial mode configuration >>> 1.2. Name of Document Author/Supplier: >>> Author: Guoqing Zhu >>> 1.3 Date of This Document: >>> 28 April, 2009 >>> 4. Technical Description >>> 4.1. Summary >>> >>> Support Edgeport USB serial devices RS232/422/485 mode switching mode >>> via usbser_edge.conf. >> > From Artem.Kachitchkin@sun.com Wed Apr 29 08:46:11 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3TFkBu0021392 for ; Wed, 29 Apr 2009 08:46:11 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3TFk7U7007052; Wed, 29 Apr 2009 08:46:11 -0700 (PDT) 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 <0KIV00M1LD4VAT00@nwk-avmta-2.sfbay.sun.com>; Wed, 29 Apr 2009 08:46:07 -0700 (PDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KIV00DFMD4VSVD0@nwk-avmta-2.sfbay.sun.com>; Wed, 29 Apr 2009 08:46:07 -0700 (PDT) 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 n3TFk7mH014968; Wed, 29 Apr 2009 08:46:07 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KIV00F00CPZWE00@fe-sfbay-10.sun.com>; Wed, 29 Apr 2009 08:46:07 -0700 (PDT) Received: from [192.168.1.100] ([unknown] [75.6.230.171]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KIV002LGD4N7C70@fe-sfbay-10.sun.com>; Wed, 29 Apr 2009 08:46:04 -0700 (PDT) Date: Wed, 29 Apr 2009 08:45:30 -0700 From: Artem Kachitchkine Subject: Re: PSARC/2009/266 Edgeport USB serial mode configuration In-reply-to: <49F7DABB.9060001@sun.com> Sender: Artem.Kachitchkin@sun.com To: "Garrett D'Amore" Cc: guoqing zhu - Sun Microsystems - Beijing China , Andrew Gabriel , PSARC-ext@sun.com, usb-tech@sun.com Message-id: <49F8761A.2050805@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49F77E31.6080204@sun.com> <49F78814.3020309@sun.com> <49F7D3EE.3020606@sun.com> <49F7DABB.9060001@sun.com> User-Agent: Mozilla/5.0 Gecko/20040113 Status: RO Content-Length: 1446 > I'm *really* not a fan of inconsistent property handling -- magic > encoded strings like what is proposed here for portflag seems,... ugly. I've heard of magic numbers, but this is the first time I'm hearing of magic strings. What's wrong with descriptive names? Would it help if they were in lower case or camel case? > Is there a reason why driver/instance number are inadequate to properly > identify a usb device in driver.conf? (usb(4) sheds no light on how usb > properties work.) Moving device to another USB port can change instance number. Pointing your finger and assigning a property to "this" device needs a better definition of "this", some sort of UUID, and serial number is the closest thing USB has to offer. > Didn't we just see a different case for usb configuration using .conf > properties? That case simply promoted stability of existing properties. It has been noted in the discussion that instance-based properties have limitations. This case makes it possible to add a new mode for "ignore-cd" in the future. > "portflag" as specified looks like a call generator, and a "hack". "portflag" as specified looks very similar to sd.conf sd-config-list - PSARC/2008/465, eagerly approved by this committee. > It does seem that perhaps an SMF property or something like what > Brussels does for NIC drivers is called for here. driver.conf is not perfect, but improving on it is not this case. -Artem From gdamore@sun.com Wed Apr 29 09:05:08 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 n3TG57ht022962 for ; Wed, 29 Apr 2009 09:05:08 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3TG5438025971; Thu, 30 Apr 2009 00:05:06 +0800 (SGT) 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 <0KIV0001VE0GP900@nwk-avmta-1.sfbay.Sun.COM>; Wed, 29 Apr 2009 09:05:04 -0700 (PDT) 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 <0KIV00EY8E0E9L70@nwk-avmta-1.sfbay.Sun.COM>; Wed, 29 Apr 2009 09:05:02 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n3TG52OW017529; Wed, 29 Apr 2009 09:05:02 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KIV00300DKRB800@fe-sfbay-09.sun.com>; Wed, 29 Apr 2009 09:05:02 -0700 (PDT) Received: from [192.168.251.11] ([unknown] [76.93.15.33]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KIV00KP8E0BH4C0@fe-sfbay-09.sun.com>; Wed, 29 Apr 2009 09:05:00 -0700 (PDT) Date: Wed, 29 Apr 2009 09:04:59 -0700 From: "Garrett D'Amore" Subject: Re: PSARC/2009/266 Edgeport USB serial mode configuration In-reply-to: <49F8761A.2050805@sun.com> Sender: Garrett.Damore@sun.com To: Artem Kachitchkine Cc: guoqing zhu - Sun Microsystems - Beijing China , Andrew Gabriel , PSARC-ext@sun.com, usb-tech@sun.com Message-id: <49F87AAB.4090605@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49F77E31.6080204@sun.com> <49F78814.3020309@sun.com> <49F7D3EE.3020606@sun.com> <49F7DABB.9060001@sun.com> <49F8761A.2050805@sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20081201) Status: RO Content-Length: 2565 Artem Kachitchkine wrote: > >> I'm *really* not a fan of inconsistent property handling -- magic >> encoded strings like what is proposed here for portflag seems,... ugly. > > I've heard of magic numbers, but this is the first time I'm hearing of > magic strings. What's wrong with descriptive names? Would it help if > they were in lower case or camel case? > >> Is there a reason why driver/instance number are inadequate to >> properly identify a usb device in driver.conf? (usb(4) sheds no >> light on how usb properties work.) > > Moving device to another USB port can change instance number. Pointing > your finger and assigning a property to "this" device needs a better > definition of "this", some sort of UUID, and serial number is the > closest thing USB has to offer. I misread serial number thinking it was a "serial device port number" or somesuch magic value from the USB enumeration. Not an actual mfgr's serial number. Given that you're using the latter and not the former, I'm much happier. > > > Didn't we just see a different case for usb configuration using .conf > > properties? > > That case simply promoted stability of existing properties. It has > been noted in the discussion that instance-based properties have > limitations. This case makes it possible to add a new mode for > "ignore-cd" in the future. Hmmm.... the concern I have here is inconsistency between the two schemes. > >> "portflag" as specified looks like a call generator, and a "hack". > > "portflag" as specified looks very similar to sd.conf sd-config-list - > PSARC/2008/465, eagerly approved by this committee. OK, I was not familiar with that case. > >> It does seem that perhaps an SMF property or something like what >> Brussels does for NIC drivers is called for here. > > driver.conf is not perfect, but improving on it is not this case. Maybe not in the general case, but I think it is fair to recommend that the project team consider alternative, perhaps superior, methods to configure such tunables. driver.conf has so many problems that IMO it ought be strongly discouraged for normal kinds of tunables. (For tunables that will rarely, or never, be used, such as interrupt frequencies of audio devices, I'm OK with it. But for "typically" used values that may be required in order to allow the device to operate *correctly*, I'd really prefer to see a better solution.) I feel strongly enough about this to recommend it and withhold a +1, but not strongly enough to derail the case over it. -- Garrett > > -Artem From Artem.Kachitchkin@sun.com Tue May 5 12:37:17 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 n45JbGoU009373 for ; Tue, 5 May 2009 12:37:16 -0700 (PDT) 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 n45JbGKb031721; Tue, 5 May 2009 13:37:16 -0600 (MDT) 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 <0KJ600E07RU2YP00@brm-avmta-1.central.sun.com>; Tue, 05 May 2009 13:37:14 -0600 (MDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJ600MCFRU2TDA0@brm-avmta-1.central.sun.com>; Tue, 05 May 2009 13:37:14 -0600 (MDT) 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 n45JbErS005864; Tue, 05 May 2009 12:37:14 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KJ600K00RFVY700@fe-sfbay-10.sun.com>; Tue, 05 May 2009 12:37:14 -0700 (PDT) Received: from [129.146.104.83] ([unknown] [129.146.104.83]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KJ600FAVRU1BYC0@fe-sfbay-10.sun.com>; Tue, 05 May 2009 12:37:13 -0700 (PDT) Date: Tue, 05 May 2009 12:37:07 -0700 From: Artem Kachitchkine Subject: Re: PSARC/2009/266 Edgeport USB serial mode configuration In-reply-to: <49F77E31.6080204@sun.com> Sender: Artem.Kachitchkin@sun.com To: PSARC-ext@sun.com Cc: usb-tech@sun.com Message-id: <4A009563.3080109@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: <49F77E31.6080204@sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20081215) Status: RO Content-Length: 2709 Timeout is approaching: there's been a bit of discussion and so far we've got one abstain (Garrett) and no other votes. -Artem On 04/28/09 15:07, Artem Kachitchkine wrote: > > I'm sponsoring this fasttrack for Guoqing Zhu. The timer is set for > 05/06/2009. > > My understanding is that even though the initial delivery is for > usbser_edge driver, the proposed interface can be adopted by other USB > serial drivers and new modes added in the future. > > -Artem > > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > Edgeport USB serial mode configuration > 1.2. Name of Document Author/Supplier: > Author: Guoqing Zhu > 1.3 Date of This Document: > 28 April, 2009 > 4. Technical Description > 4.1. Summary > > Support Edgeport USB serial devices RS232/422/485 mode switching mode > via usbser_edge.conf. > > Requested binding: patch. > > > 4.2 Details > > Most Edgeport USBSerial devices only work in RS232 mode, except that two > Edgeport devices, Edgeport 4S and Edgeport 8S, can work in RS232/422/485 > mode. But current usbser_edge driver only supports RS232 mode. There > needs to be a way to configure which mode the device should operate in. > > We propose to create a new usbser_edge.conf property called portflag, > a comma-separated string array, each string in the following format: > > "serialnumber=SerNum portnumber=PortNum mode=Mode" > > where: > > SerNum: USB serial number, can be obtained from the 'usb-serialno' > property from prtconf(1M) output. > > PortNum: serial port number > > Mode - could be following strings corresponding to the modes > supported by the device's firmware: > > RS232 > RS422_NOTERM > RS422_TERM > RS485_HALF_ECHO_ENDUNIT > RS485_HALF_NOECHO_ENDUNIT > RS485_HALF_ECHO_MIDDLE > RS485_HALF_NOECHO_MIDDLE > RS485_FULL_MASTER_ENDUNIT > RS485_FULL_SLAVE_ENDUNIT > RS485_FULL_MASTER_MIDDLE > RS485_FULL_SLAVE_MIDDLE > > For example, set device (SN: W84662767-0) port 0 to RS422_NOTERM mode: > > portflag= > "serialnumber=W84662767-0 portnumber=0 mode=RS422_NOTERM"; > > > 5. Interfaces > > Name | Classification | Description > ----------+----------------+------------------------------- > portflag | Stable | driver.conf property > ----------+----------------+------------------------------- > > Requested binding: patch. > > 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 carlsonj@phorcys.east.sun.com Tue May 5 12:56:25 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 n45JuO0D010254 for ; Tue, 5 May 2009 12:56:24 -0700 (PDT) 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 n45JuG9Q021511; Wed, 6 May 2009 03:56:23 +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 <0KJ600I0DSPW3B00@nwk-avmta-2.sfbay.sun.com>; Tue, 05 May 2009 12:56:20 -0700 (PDT) Received: from dm-east-01.east.sun.com ([129.148.9.192]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJ600F3SSPVRD40@nwk-avmta-2.sfbay.sun.com>; Tue, 05 May 2009 12:56:19 -0700 (PDT) Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143]) by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n45JuIBH039278; Tue, 05 May 2009 15:56:18 -0400 (EDT) Received: from phorcys.east.sun.com (phorcys.local [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n45JtWoN020844; Tue, 05 May 2009 15:55:32 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n45JtWjG020841; Tue, 05 May 2009 15:55:32 -0400 (EDT) Date: Tue, 05 May 2009 15:55:32 -0400 From: James Carlson Subject: Re: PSARC/2009/266 Edgeport USB serial mode configuration In-reply-to: <4A009563.3080109@sun.com> To: Artem Kachitchkine Cc: PSARC-ext@sun.com, usb-tech@sun.com Message-id: <18944.39348.860412.318372@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49F77E31.6080204@sun.com> <4A009563.3080109@sun.com> Status: RO Content-Length: 930 Artem Kachitchkine writes: > > Timeout is approaching: there's been a bit of discussion and so far > we've got one abstain (Garrett) and no other votes. I don't buy the argument that because this is electrical configuration, it's not subject to ioctls. We have other interfaces where electrical configuration (e.g., sync clocking) is configured by ioctl. And I'm not sure I buy the argument that nobody else will want to do this, so having it a special for Edgeport makes sense. And I definitely agree that the portflag method is ugly. If you'd be willing to change that portflag string from "Stable" (which isn't one of the current stability levels anyway) to "Uncommitted", then I'd give it a +1. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Artem.Kachitchkin@Sun.COM Tue May 5 18:52:23 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 n461qMkS014806 for ; Tue, 5 May 2009 18:52:22 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n461qKEk008143; Tue, 5 May 2009 19:52:22 -0600 (MDT) 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 <0KJ700H059793P00@nwk-avmta-2.sfbay.sun.com>; Tue, 05 May 2009 18:52:21 -0700 (PDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJ7002F7979L3C0@nwk-avmta-2.sfbay.sun.com>; Tue, 05 May 2009 18:52:21 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n461qL1L014560; Tue, 05 May 2009 18:52:21 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KJ7006008WNFB00@fe-sfbay-09.sun.com>; Tue, 05 May 2009 18:52:21 -0700 (PDT) Received: from [192.168.1.100] ([unknown] [75.6.230.171]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KJ7006X0971NQE0@fe-sfbay-09.sun.com>; Tue, 05 May 2009 18:52:18 -0700 (PDT) Date: Tue, 05 May 2009 18:51:46 -0700 From: Artem Kachitchkine Subject: Re: PSARC/2009/266 Edgeport USB serial mode configuration In-reply-to: <18944.39348.860412.318372@gargle.gargle.HOWL> Sender: Artem.Kachitchkin@Sun.COM To: James Carlson , PSARC-ext@Sun.COM Cc: usb-tech@Sun.COM Message-id: <4A00ED32.6080202@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: <49F77E31.6080204@sun.com> <4A009563.3080109@sun.com> <18944.39348.860412.318372@gargle.gargle.HOWL> User-Agent: Mozilla/5.0 Gecko/20040113 Status: RO Content-Length: 264 > If you'd be willing to change that portflag string from "Stable" > (which isn't one of the current stability levels anyway) to > "Uncommitted", then I'd give it a +1. The project team informed me that they decided to change stability to Uncommitted. -Artem From carlsonj@phorcys.east.sun.com Wed May 6 06:09:00 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 n46D8xx0018671 for ; Wed, 6 May 2009 06:08:59 -0700 (PDT) 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 n46D8iPi011582; Wed, 6 May 2009 14:08:58 +0100 (BST) 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 <0KJ800J0T4IW4800@nwk-avmta-1.sfbay.Sun.COM>; Wed, 06 May 2009 06:08:56 -0700 (PDT) Received: from dm-east-02.east.sun.com ([129.148.13.5]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJ800I464IU2B60@nwk-avmta-1.sfbay.Sun.COM>; Wed, 06 May 2009 06:08:55 -0700 (PDT) Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143]) by dm-east-02.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n46D8rY6061729; Wed, 06 May 2009 09:08:53 -0400 (EDT) Received: from phorcys.east.sun.com (phorcys.local [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n46D871d022483; Wed, 06 May 2009 09:08:07 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n46D87Vm022480; Wed, 06 May 2009 09:08:07 -0400 (EDT) Date: Wed, 06 May 2009 09:08:07 -0400 From: James Carlson Subject: Re: PSARC/2009/266 Edgeport USB serial mode configuration In-reply-to: <4A00ED32.6080202@sun.com> To: Artem Kachitchkine Cc: PSARC-ext@sun.com, usb-tech@sun.com Message-id: <18945.35767.64928.576451@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49F77E31.6080204@sun.com> <4A009563.3080109@sun.com> <18944.39348.860412.318372@gargle.gargle.HOWL> <4A00ED32.6080202@sun.com> Status: RO Content-Length: 537 Artem Kachitchkine writes: > > > If you'd be willing to change that portflag string from "Stable" > > (which isn't one of the current stability levels anyway) to > > "Uncommitted", then I'd give it a +1. > > The project team informed me that they decided to change stability to > Uncommitted. Then "+1". ;-} -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Andrew.Gabriel@sun.com Wed May 6 06:34:53 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 n46DYq1u019015 for ; Wed, 6 May 2009 06:34:53 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n46DYjFS028110; Wed, 6 May 2009 14:34:51 +0100 (BST) 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 <0KJ800E015Q1MV00@nwk-avmta-2.sfbay.sun.com>; Wed, 06 May 2009 06:34:49 -0700 (PDT) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJ8005ZR5Q0SCD0@nwk-avmta-2.sfbay.sun.com>; Wed, 06 May 2009 06:34:49 -0700 (PDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n46DYmMX009142; Wed, 06 May 2009 13:34:48 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KJ800K0045AC700@fe-emea-09.sun.com>; Wed, 06 May 2009 14:34:48 +0100 (BST) Received: from [81.187.162.109] ([unknown] [81.187.162.109]) by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KJ8006XS5PK4S30@fe-emea-09.sun.com>; Wed, 06 May 2009 14:34:32 +0100 (BST) Date: Wed, 06 May 2009 14:34:37 +0100 From: Andrew Gabriel Subject: Re: PSARC/2009/266 Edgeport USB serial mode configuration In-reply-to: <4A009563.3080109@sun.com> Sender: Andrew.Gabriel@sun.com To: Artem Kachitchkine Cc: PSARC-ext@sun.com, usb-tech@sun.com Message-id: <4A0191ED.1050106@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: <49F77E31.6080204@sun.com> <4A009563.3080109@sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090323) Status: RO Content-Length: 364 I'd like to see a better design for the configuration, along the lines Garrett and/or I described. The justification for using the proposed inferior scheme is too weak in my view. Artem Kachitchkine wrote: > > Timeout is approaching: there's been a bit of discussion and so far > we've got one abstain (Garrett) and no other votes. > > -Artem > -- Andrew From Artem.Kachitchkin@sun.com Thu May 7 11:26:39 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 n47IQc40014682 for ; Thu, 7 May 2009 11:26:39 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n47IQUoM026523; Thu, 7 May 2009 19:26:37 +0100 (BST) 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 <0KJA00N0TDWB0M00@nwk-avmta-2.sfbay.sun.com>; Thu, 07 May 2009 11:26:35 -0700 (PDT) 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 <0KJA00DB2DWBEQF0@nwk-avmta-2.sfbay.sun.com>; Thu, 07 May 2009 11:26:35 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n47IQZi9020363; Thu, 07 May 2009 11:26:35 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KJA00000DRBVY00@fe-sfbay-10.sun.com>; Thu, 07 May 2009 11:26:35 -0700 (PDT) Received: from [129.146.104.83] ([unknown] [129.146.104.83]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KJA0071PDW7DM70@fe-sfbay-10.sun.com>; Thu, 07 May 2009 11:26:31 -0700 (PDT) Date: Thu, 07 May 2009 11:26:29 -0700 From: Artem Kachitchkine Subject: Re: PSARC/2009/266 Edgeport USB serial mode configuration In-reply-to: <49F77E31.6080204@sun.com> Sender: Artem.Kachitchkin@sun.com To: PSARC-ext@sun.com Cc: usb-tech@sun.com Message-id: <4A0327D5.3010101@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: <49F77E31.6080204@sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20081215) Status: RO Content-Length: 105 With the Uncommitted stability level, this proposal was approved at yesterday's PSARC meeting. -Artem