| ufoma.4 (154238) | ufoma.4 (162871) |
|---|---|
| 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 154238 2006-01-11 21:46:15Z takawata $ | 28.\" $FreeBSD: head/share/man/man4/ufoma.4 162871 2006-09-30 15:14:49Z ru $ |
| 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 --- 5 unchanged lines hidden (view full) --- 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. 45These are partly like CDC ACM model based modems, which are supported 46by 47.Xr umodem 4 , 48but the 49.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 --- 5 unchanged lines hidden (view full) --- 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. 45These are partly like CDC ACM model based modems, which are supported 46by 47.Xr umodem 4 , 48but the 49.Nm |
| 50driver recognizes a specific usb descriptor that describes its role and | 50driver recognizes a specific USB descriptor that describes its role and |
| 51interface structure, and it will negotiate its role when the device is open. 52They support a regular AT command set and 53the commands can either be multiplexed with the data stream 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 . 62.Sh SYSCTLS | 51interface structure, and it will negotiate its role when the device is open. 52They support a regular AT command set and 53the commands can either be multiplexed with the data stream 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 . 62.Sh SYSCTLS |
| 63This device often have a few interface sets and these interfaces 64have its role, sometimes multiplexed. 65These roles are identified with the following sysctl MIB's: | 63These devices often have a few interface sets and these interfaces 64have their role, sometimes multiplexed. 65These roles are identified with the following sysctl MIBs: |
| 66.Bl -tag -width indent 67.It Va dev.ucom.%d.supportmode 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 74The modes are as follows: 75.Bl -tag -width indent | 66.Bl -tag -width indent 67.It Va dev.ucom.%d.supportmode 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 74The modes are as follows: 75.Bl -tag -width indent |
| 76.It modem | 76.It Li modem |
| 77Accepts AT commands and go and pass packet communication data. | 77Accepts AT commands and go and pass packet communication data. |
| 78.It handsfree | 78.It Li handsfree |
| 79Accepts AT commands but it does not pass data. | 79Accepts AT commands but it does not pass data. |
| 80.It obex | 80.It Li obex |
| 81Accepts OBEX frame which is used to exchange telephone book, etc. | 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. 88.It unlinked 89When a interface is not yet negotiated, the interface is in this mode. | 82.It Li vendor1 , vendor2 83Vendor specific data may be passed. 84.It Li deactivated 85When an interface is recognized by the system but not used, the interface 86will be set to this mode. 87.It Li unlinked 88When an 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 96.Bl -bullet -compact 97.It 98SHARP FOMA SH902i 99.It 100KYOCERA PHS AH-K3001V (a.k.a Kyopon) 101.It 102SANYO Vodafone3G V801SA 103.El 104.Sh SEE ALSO | 89.El 90.Sh HARDWARE 91Devices supported by the 92.Nm 93driver include: 94.Pp 95.Bl -bullet -compact 96.It 97SHARP FOMA SH902i 98.It 99KYOCERA PHS AH-K3001V (a.k.a Kyopon) 100.It 101SANYO Vodafone3G V801SA 102.El 103.Sh SEE ALSO |
| 105specification can be found at: | 104Specification can be found at: |
| 106.Pp | 105.Pp |
| 107http://www.nttdocomo.co.jp/corporate/technology/document/foma/index.html 108http://www.mcpc-jp.org/doclist.htm | 106.Bl -item -compact 107.It 108.Pa http://www.nttdocomo.co.jp/corporate/technology/document/foma/index.html 109.It 110.Pa http://www.mcpc-jp.org/doclist.htm 111.El |
| 109.Pp 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 | 112.Pp 113.Xr tty 4 , 114.Xr ucom 4 , 115.Xr umodem 4 , 116.Xr usb 4 117.Sh HISTORY 118The 119.Nm 120driver 121appeared in |
| 119.Fx 7-CURRENT, partly from | 122.Fx 7.0 , 123partly derived from the |
| 120.Xr umodem 4 121code. 122.Sh BUGS 123Interfaces with multiplexed commands and data and interfaces with 124commands only are supported. | 124.Xr umodem 4 125code. 126.Sh BUGS 127Interfaces with multiplexed commands and data and interfaces with 128commands only are supported. |