Kconfig.char 4.5 KB

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