Kconfig 3.3 KB

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