Kconfig.char 4.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128
  1. menu "UML Character Devices"
  2. config STDERR_CONSOLE
  3. bool "stderr console"
  4. default y
  5. help
  6. console driver which dumps all printk messages to stderr.
  7. config STDIO_CONSOLE
  8. bool
  9. default y
  10. config SSL
  11. bool "Virtual serial line"
  12. help
  13. The User-Mode Linux environment allows you to create virtual serial
  14. lines on the UML that are usually made to show up on the host as
  15. ttys or ptys.
  16. See <http://user-mode-linux.sourceforge.net/old/input.html> for more
  17. information and command line examples of how to use this facility.
  18. Unless you have a specific reason for disabling this, say Y.
  19. config NULL_CHAN
  20. bool "null channel support"
  21. help
  22. This option enables support for attaching UML consoles and serial
  23. lines to a device similar to /dev/null. Data written to it disappears
  24. and there is never any data to be read.
  25. config PORT_CHAN
  26. bool "port channel support"
  27. help
  28. This option enables support for attaching UML consoles and serial
  29. lines to host portals. They may be accessed with 'telnet <host>
  30. <port number>'. Any number of consoles and serial lines may be
  31. attached to a single portal, although what UML device you get when
  32. you telnet to that portal will be unpredictable.
  33. It is safe to say 'Y' here.
  34. config PTY_CHAN
  35. bool "pty channel support"
  36. help
  37. This option enables support for attaching UML consoles and serial
  38. lines to host pseudo-terminals. Access to both traditional
  39. pseudo-terminals (/dev/pty*) and pts pseudo-terminals are controlled
  40. with this option. The assignment of UML devices to host devices
  41. will be announced in the kernel message log.
  42. It is safe to say 'Y' here.
  43. config TTY_CHAN
  44. bool "tty channel support"
  45. help
  46. This option enables support for attaching UML consoles and serial
  47. lines to host terminals. Access to both virtual consoles
  48. (/dev/tty*) and the slave side of pseudo-terminals (/dev/ttyp* and
  49. /dev/pts/*) are controlled by this option.
  50. It is safe to say 'Y' here.
  51. config XTERM_CHAN
  52. bool "xterm channel support"
  53. help
  54. This option enables support for attaching UML consoles and serial
  55. lines to xterms. Each UML device so assigned will be brought up in
  56. its own xterm.
  57. It is safe to say 'Y' here.
  58. config NOCONFIG_CHAN
  59. bool
  60. default !(XTERM_CHAN && TTY_CHAN && PTY_CHAN && PORT_CHAN && NULL_CHAN)
  61. config CON_ZERO_CHAN
  62. string "Default main console channel initialization"
  63. default "fd:0,fd:1"
  64. help
  65. This is the string describing the channel to which the main console
  66. will be attached by default. This value can be overridden from the
  67. command line. The default value is "fd:0,fd:1", which attaches the
  68. main console to stdin and stdout.
  69. It is safe to leave this unchanged.
  70. config CON_CHAN
  71. string "Default console channel initialization"
  72. default "xterm"
  73. help
  74. This is the string describing the channel to which all consoles
  75. except the main console will be attached by default. This value can
  76. be overridden from the command line. The default value is "xterm",
  77. which brings them up in xterms.
  78. It is safe to leave this unchanged, although you may wish to change
  79. this if you expect the UML that you build to be run in environments
  80. which don't have X or xterm available.
  81. config SSL_CHAN
  82. string "Default serial line channel initialization"
  83. default "pty"
  84. help
  85. This is the string describing the channel to which the serial lines
  86. will be attached by default. This value can be overridden from the
  87. command line. The default value is "pty", which attaches them to
  88. traditional pseudo-terminals.
  89. It is safe to leave this unchanged, although you may wish to change
  90. this if you expect the UML that you build to be run in environments
  91. which don't have a set of /dev/pty* devices.
  92. config UML_SOUND
  93. tristate "Sound support"
  94. help
  95. This option enables UML sound support. If enabled, it will pull in
  96. soundcore and the UML hostaudio relay, which acts as a intermediary
  97. between the host's dsp and mixer devices and the UML sound system.
  98. It is safe to say 'Y' here.
  99. config SOUND
  100. tristate
  101. default UML_SOUND
  102. config SOUND_OSS_CORE
  103. bool
  104. default UML_SOUND
  105. config HOSTAUDIO
  106. tristate
  107. default UML_SOUND
  108. endmenu