blob: 936361e5a2b66f109156d8ac646f01ee2ed88027 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
#
# CAIF net configurations
#
menuconfig CAIF
tristate "CAIF support"
select CRC_CCITT
default n
---help---
The "Communication CPU to Application CPU Interface" (CAIF) is a packet
based connection-oriented MUX protocol developed by ST-Ericsson for use
with its modems. It is accessed from user space as sockets (PF_CAIF).
Say Y (or M) here if you build for a phone product (e.g. Android or
MeeGo ) that uses CAIF as transport, if unsure say N.
If you select to build it as module then CAIF_NETDEV also needs to be
built as modules. You will also need to say yes to any CAIF physical
devices that your platform requires.
See Documentation/networking/caif for a further explanation on how to
use and configure CAIF.
config CAIF_DEBUG
bool "Enable Debug"
depends on CAIF
default n
--- help ---
Enable the inclusion of debug code in the CAIF stack.
Be aware that doing this will impact performance.
If unsure say N.
config CAIF_NETDEV
tristate "CAIF GPRS Network device"
depends on CAIF
default CAIF
---help---
Say Y if you will be using a CAIF based GPRS network device.
This can be either built-in or a loadable module,
If you select to build it as a built-in then the main CAIF device must
also be a built-in.
If unsure say Y.
config CAIF_USB
tristate "CAIF USB support"
depends on CAIF
default n
---help---
Say Y if you are using CAIF over USB CDC NCM.
This can be either built-in or a loadable module,
If you select to build it as a built-in then the main CAIF device must
also be a built-in.
If unsure say N.
|
