PageRenderTime 20ms CodeModel.GetById 17ms app.highlight 1ms RepoModel.GetById 1ms app.codeStats 0ms

/net/irda/Kconfig

http://github.com/mirrors/linux
#! | 96 lines | 77 code | 19 blank | 0 comment | 0 complexity | 4ea5adbe31349a0ae90d53fbbe73fe0a MD5 | raw file
 1#
 2# IrDA protocol configuration
 3#
 4
 5menuconfig IRDA
 6	depends on NET && !S390
 7	tristate "IrDA (infrared) subsystem support"
 8	select CRC_CCITT
 9	---help---
10	  Say Y here if you want to build support for the IrDA (TM) protocols.
11	  The Infrared Data Associations (tm) specifies standards for wireless
12	  infrared communication and is supported by most laptops and PDA's.
13
14	  To use Linux support for the IrDA (tm) protocols, you will also need
15	  some user-space utilities like irattach.  For more information, see
16	  the file <file:Documentation/networking/irda.txt>.  You also want to
17	  read the IR-HOWTO, available at
18	  <http://www.tldp.org/docs.html#howto>.
19
20	  If you want to exchange bits of data (vCal, vCard) with a PDA, you
21	  will need to install some OBEX application, such as OpenObex :
22	  <http://sourceforge.net/projects/openobex/>
23
24	  To compile this support as a module, choose M here: the module will
25	  be called irda.
26
27comment "IrDA protocols"
28	depends on IRDA
29
30source "net/irda/irlan/Kconfig"
31
32source "net/irda/irnet/Kconfig"
33
34source "net/irda/ircomm/Kconfig"
35
36config IRDA_ULTRA
37	bool "Ultra (connectionless) protocol"
38	depends on IRDA
39	help
40	  Say Y here to support the connectionless Ultra IRDA protocol.
41	  Ultra allows to exchange data over IrDA with really simple devices
42	  (watch, beacon) without the overhead of the IrDA protocol (no handshaking,
43	  no management frames, simple fixed header).
44	  Ultra is available as a special socket : socket(AF_IRDA, SOCK_DGRAM, 1);
45
46comment "IrDA options"
47	depends on IRDA
48
49config IRDA_CACHE_LAST_LSAP
50	bool "Cache last LSAP"
51	depends on IRDA
52	help
53	  Say Y here if you want IrLMP to cache the last LSAP used.  This
54	  makes sense since most frames will be sent/received on the same
55	  connection.  Enabling this option will save a hash-lookup per frame.
56
57	  If unsure, say Y.
58
59config IRDA_FAST_RR
60	bool "Fast RRs (low latency)"
61	depends on IRDA
62	---help---
63	  Say Y here is you want IrLAP to send fast RR (Receive Ready) frames
64	  when acting as a primary station.
65	  Disabling this option will make latency over IrDA very bad. Enabling
66	  this option will make the IrDA stack send more packet than strictly
67	  necessary, thus reduce your battery life (but not that much).
68
69	  Fast RR will make IrLAP send out a RR frame immediately when
70	  receiving a frame if its own transmit queue is currently empty. This
71	  will give a lot of speed improvement when receiving much data since
72	  the secondary station will not have to wait the max. turn around
73	  time (usually 500ms) before it is allowed to transmit the next time.
74	  If the transmit queue of the secondary is also empty, the primary will
75	  start backing-off before sending another RR frame, waiting longer
76	  each time until the back-off reaches the max. turn around time.
77	  This back-off increase in controlled via
78	  /proc/sys/net/irda/fast_poll_increase
79
80	  If unsure, say Y.
81
82config IRDA_DEBUG
83	bool "Debug information"
84	depends on IRDA
85	help
86	  Say Y here if you want the IrDA subsystem to write debug information
87	  to your syslog. You can change the debug level in
88	  /proc/sys/net/irda/debug .
89	  When this option is enabled, the IrDA also perform many extra internal
90	  verifications which will usually prevent the kernel to crash in case of
91	  bugs.
92
93	  If unsure, say Y (since it makes it easier to find the bugs).
94
95source "drivers/net/irda/Kconfig"
96