| ufoma.4 (154223) | ufoma.4 (154238) |
|---|---|
| 1.\" Copyright (c) 2006 Takanori Watanabe. 2.\" All rights reserved. 3.\" 4.\" This code is derived from software contributed to The NetBSD Foundation 5.\" by Lennart Augustsson. 6.\" 7.\" Redistribution and use in source and binary forms, with or without 8.\" modification, are permitted provided that the following conditions --- 11 unchanged lines hidden (view full) --- 20.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 21.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 22.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 23.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 24.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 25.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 26.\" POSSIBILITY OF SUCH DAMAGE. 27.\" | 1.\" Copyright (c) 2006 Takanori Watanabe. 2.\" All rights reserved. 3.\" 4.\" This code is derived from software contributed to The NetBSD Foundation 5.\" by Lennart Augustsson. 6.\" 7.\" Redistribution and use in source and binary forms, with or without 8.\" modification, are permitted provided that the following conditions --- 11 unchanged lines hidden (view full) --- 20.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 21.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 22.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 23.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 24.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 25.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 26.\" POSSIBILITY OF SUCH DAMAGE. 27.\" |
| 28.\" $FreeBSD: head/share/man/man4/ufoma.4 154223 2006-01-11 13:51:03Z takawata $ | 28.\" $FreeBSD: head/share/man/man4/ufoma.4 154238 2006-01-11 21:46:15Z takawata $ |
| 29.\" 30.Dd January 10, 2006 31.Dt UFOMA 4 32.Os 33.Sh NAME 34.Nm ufoma 35.Nd USB mobile phone support 36.Sh SYNOPSIS 37.Cd "device ufoma" 38.Cd "device ucom" 39.Sh DESCRIPTION 40The 41.Nm | 29.\" 30.Dd January 10, 2006 31.Dt UFOMA 4 32.Os 33.Sh NAME 34.Nm ufoma 35.Nd USB mobile phone support 36.Sh SYNOPSIS 37.Cd "device ufoma" 38.Cd "device ucom" 39.Sh DESCRIPTION 40The 41.Nm |
| 42driver provides support for USB mobile phone terminal in the subset of 43Mobile Computing Promotion Consortium USB Implementation Guideline, | 42driver provides support for USB mobile phone terminals in the subset of 43the Mobile Computing Promotion Consortium USB Implementation Guideline, |
| 44which is adopted by FOMA, the NTT DoCoMo 3G system, terminal. | 44which is adopted by FOMA, the NTT DoCoMo 3G system, terminal. |
| 45These are partly like CDC ACM model based modem, which is supported | 45These are partly like CDC ACM model based modems, which are supported |
| 46by | 46by |
| 47.Xr umodem 4 . 48But this recognizes specific usb descriptor that describes its role and | 47.Xr umodem 4 , 48but the 49.Nm 50driver recognizes a specific usb descriptor that describes its role and |
| 49interface structure, and it will negotiate its role when the device is open. | 51interface structure, and it will negotiate its role when the device is open. |
| 50 51They support a regular AT command set. 52The commands can either be multiplexed with the data stream | 52They support a regular AT command set and 53the commands can either be multiplexed with the data stream |
| 53or handled through separate pipes. 54In the latter case the AT 55commands have to be given on a device separate from the data device. 56.Pp 57The device is accessed through the 58.Xr ucom 4 59driver which makes it behave like a 60.Xr tty 4 . | 54or handled through separate pipes. 55In the latter case the AT 56commands have to be given on a device separate from the data device. 57.Pp 58The device is accessed through the 59.Xr ucom 4 60driver which makes it behave like a 61.Xr tty 4 . |
| 61 | |
| 62.Sh SYSCTLS 63This device often have a few interface sets and these interfaces 64have its role, sometimes multiplexed. | 62.Sh SYSCTLS 63This device often have a few interface sets and these interfaces 64have its role, sometimes multiplexed. |
| 65These roles are identified with following sysctl MIB. | 65These roles are identified with the following sysctl MIB's: |
| 66.Bl -tag -width indent 67.It Va dev.ucom.%d.supportmode | 66.Bl -tag -width indent 67.It Va dev.ucom.%d.supportmode |
| 68The modes which is supprted by the interface. | 68The modes which are supported by the interface. |
| 69.It Va dev.ucom.%d.currentmode 70Current mode of the interface. 71.It Va dev.ucom.%d.openmode 72Mode to transit when the device is open next. 73.El | 69.It Va dev.ucom.%d.currentmode 70Current mode of the interface. 71.It Va dev.ucom.%d.openmode 72Mode to transit when the device is open next. 73.El |
| 74The mode is as follows. | 74The modes are as follows: |
| 75.Bl -tag -width indent 76.It modem 77Accepts AT commands and go and pass packet communication data. 78.It handsfree 79Accepts AT commands but it does not pass data. 80.It obex 81Accepts OBEX frame which is used to exchange telephone book, etc. 82.It vendor1 83.It vendor2 84Vendor specific data may passed. 85.It deactivated 86When a interface is recognized to the system and not used, the interface | 75.Bl -tag -width indent 76.It modem 77Accepts AT commands and go and pass packet communication data. 78.It handsfree 79Accepts AT commands but it does not pass data. 80.It obex 81Accepts OBEX frame which is used to exchange telephone book, etc. 82.It vendor1 83.It vendor2 84Vendor specific data may passed. 85.It deactivated 86When a interface is recognized to the system and not used, the interface |
| 87will set to this mode. | 87will set to this mode. |
| 88.It unlinked 89When a interface is not yet negotiated, the interface is in this mode. 90.El 91.Sh HARDWARE 92Devices supported by the 93.Nm 94driver include: 95.Pp --- 6 unchanged lines hidden (view full) --- 102SANYO Vodafone3G V801SA 103.El 104.Sh SEE ALSO 105specification can be found at: 106.Pp 107http://www.nttdocomo.co.jp/corporate/technology/document/foma/index.html 108http://www.mcpc-jp.org/doclist.htm 109.Pp | 88.It unlinked 89When a interface is not yet negotiated, the interface is in this mode. 90.El 91.Sh HARDWARE 92Devices supported by the 93.Nm 94driver include: 95.Pp --- 6 unchanged lines hidden (view full) --- 102SANYO Vodafone3G V801SA 103.El 104.Sh SEE ALSO 105specification can be found at: 106.Pp 107http://www.nttdocomo.co.jp/corporate/technology/document/foma/index.html 108http://www.mcpc-jp.org/doclist.htm 109.Pp |
| 110 | |
| 111.Xr tty 4 , 112.Xr ucom 4 , 113.Xr umodem 4 , 114.Xr usb 4 115.Sh HISTORY 116The 117.Nm 118driver 119appeared in 120.Fx 7-CURRENT, partly from 121.Xr umodem 4 122code. 123.Sh BUGS 124Interfaces with multiplexed commands and data and interfaces with 125commands only are supported. | 110.Xr tty 4 , 111.Xr ucom 4 , 112.Xr umodem 4 , 113.Xr usb 4 114.Sh HISTORY 115The 116.Nm 117driver 118appeared in 119.Fx 7-CURRENT, partly from 120.Xr umodem 4 121code. 122.Sh BUGS 123Interfaces with multiplexed commands and data and interfaces with 124commands only are supported. |