forked from ~ljy/RK356X_SDK_RELEASE
blame | history | patch | commit | commitdiff
hc
2023-12-11 6778948f9de86c3cfaf36725a7c87dcff9ba247f 
 kernel/arch/um/drivers/Kconfig
....@@ -11,58 +11,58 @@
1111 config SSL
1212 	bool "Virtual serial line"
1313 	help
14
-          The User-Mode Linux environment allows you to create virtual serial
15
-          lines on the UML that are usually made to show up on the host as
16
-          ttys or ptys.
14
+	  The User-Mode Linux environment allows you to create virtual serial
15
+	  lines on the UML that are usually made to show up on the host as
16
+	  ttys or ptys.
1717 
18
-          See <http://user-mode-linux.sourceforge.net/old/input.html> for more
19
-          information and command line examples of how to use this facility.
18
+	  See <http://user-mode-linux.sourceforge.net/old/input.html> for more
19
+	  information and command line examples of how to use this facility.
2020 
21
-          Unless you have a specific reason for disabling this, say Y.
21
+	  Unless you have a specific reason for disabling this, say Y.
2222 
2323 config NULL_CHAN
2424 	bool "null channel support"
2525 	help
26
-          This option enables support for attaching UML consoles and serial
27
-          lines to a device similar to /dev/null.  Data written to it disappears
28
-          and there is never any data to be read.
26
+	  This option enables support for attaching UML consoles and serial
27
+	  lines to a device similar to /dev/null.  Data written to it disappears
28
+	  and there is never any data to be read.
2929 
3030 config PORT_CHAN
3131 	bool "port channel support"
3232 	help
33
-          This option enables support for attaching UML consoles and serial
34
-          lines to host portals.  They may be accessed with 'telnet <host>
35
-          <port number>'.  Any number of consoles and serial lines may be
36
-          attached to a single portal, although what UML device you get when
37
-          you telnet to that portal will be unpredictable.
38
-          It is safe to say 'Y' here.
33
+	  This option enables support for attaching UML consoles and serial
34
+	  lines to host portals.  They may be accessed with 'telnet <host>
35
+	  <port number>'.  Any number of consoles and serial lines may be
36
+	  attached to a single portal, although what UML device you get when
37
+	  you telnet to that portal will be unpredictable.
38
+	  It is safe to say 'Y' here.
3939 
4040 config PTY_CHAN
4141 	bool "pty channel support"
4242 	help
43
-          This option enables support for attaching UML consoles and serial
44
-          lines to host pseudo-terminals.  Access to both traditional
45
-          pseudo-terminals (/dev/pty*) and pts pseudo-terminals are controlled
46
-          with this option.  The assignment of UML devices to host devices
47
-          will be announced in the kernel message log.
48
-          It is safe to say 'Y' here.
43
+	  This option enables support for attaching UML consoles and serial
44
+	  lines to host pseudo-terminals.  Access to both traditional
45
+	  pseudo-terminals (/dev/pty*) and pts pseudo-terminals are controlled
46
+	  with this option.  The assignment of UML devices to host devices
47
+	  will be announced in the kernel message log.
48
+	  It is safe to say 'Y' here.
4949 
5050 config TTY_CHAN
5151 	bool "tty channel support"
5252 	help
53
-          This option enables support for attaching UML consoles and serial
54
-          lines to host terminals.  Access to both virtual consoles
55
-          (/dev/tty*) and the slave side of pseudo-terminals (/dev/ttyp* and
56
-          /dev/pts/*) are controlled by this option.
57
-          It is safe to say 'Y' here.
53
+	  This option enables support for attaching UML consoles and serial
54
+	  lines to host terminals.  Access to both virtual consoles
55
+	  (/dev/tty*) and the slave side of pseudo-terminals (/dev/ttyp* and
56
+	  /dev/pts/*) are controlled by this option.
57
+	  It is safe to say 'Y' here.
5858 
5959 config XTERM_CHAN
6060 	bool "xterm channel support"
6161 	help
62
-          This option enables support for attaching UML consoles and serial
63
-          lines to xterms.  Each UML device so assigned will be brought up in
64
-          its own xterm.
65
-          It is safe to say 'Y' here.
62
+	  This option enables support for attaching UML consoles and serial
63
+	  lines to xterms.  Each UML device so assigned will be brought up in
64
+	  its own xterm.
65
+	  It is safe to say 'Y' here.
6666 
6767 config NOCONFIG_CHAN
6868 	bool
....@@ -72,43 +72,43 @@
7272 	string "Default main console channel initialization"
7373 	default "fd:0,fd:1"
7474 	help
75
-          This is the string describing the channel to which the main console
76
-          will be attached by default.  This value can be overridden from the
77
-          command line.  The default value is "fd:0,fd:1", which attaches the
78
-          main console to stdin and stdout.
79
-          It is safe to leave this unchanged.
75
+	  This is the string describing the channel to which the main console
76
+	  will be attached by default.  This value can be overridden from the
77
+	  command line.  The default value is "fd:0,fd:1", which attaches the
78
+	  main console to stdin and stdout.
79
+	  It is safe to leave this unchanged.
8080 
8181 config CON_CHAN
8282 	string "Default console channel initialization"
8383 	default "xterm"
8484 	help
85
-          This is the string describing the channel to which all consoles
86
-          except the main console will be attached by default.  This value can
87
-          be overridden from the command line.  The default value is "xterm",
88
-          which brings them up in xterms.
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 X or xterm available.
85
+	  This is the string describing the channel to which all consoles
86
+	  except the main console will be attached by default.  This value can
87
+	  be overridden from the command line.  The default value is "xterm",
88
+	  which brings them up in xterms.
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 X or xterm available.
9292 
9393 config SSL_CHAN
9494 	string "Default serial line channel initialization"
9595 	default "pty"
9696 	help
97
-          This is the string describing the channel to which the serial lines
98
-          will be attached by default.  This value can be overridden from the
99
-          command line.  The default value is "pty", which attaches them to
100
-          traditional pseudo-terminals.
101
-          It is safe to leave this unchanged, although you may wish to change
102
-          this if you expect the UML that you build to be run in environments
103
-          which don't have a set of /dev/pty* devices.
97
+	  This is the string describing the channel to which the serial lines
98
+	  will be attached by default.  This value can be overridden from the
99
+	  command line.  The default value is "pty", which attaches them to
100
+	  traditional pseudo-terminals.
101
+	  It is safe to leave this unchanged, although you may wish to change
102
+	  this if you expect the UML that you build to be run in environments
103
+	  which don't have a set of /dev/pty* devices.
104104 
105105 config UML_SOUND
106106 	tristate "Sound support"
107107 	help
108
-          This option enables UML sound support.  If enabled, it will pull in
109
-          soundcore and the UML hostaudio relay, which acts as a intermediary
110
-          between the host's dsp and mixer devices and the UML sound system.
111
-          It is safe to say 'Y' here.
108
+	  This option enables UML sound support.  If enabled, it will pull in
109
+	  soundcore and the UML hostaudio relay, which acts as a intermediary
110
+	  between the host's dsp and mixer devices and the UML sound system.
111
+	  It is safe to say 'Y' here.
112112 
113113 config SOUND
114114 	tristate
....@@ -131,111 +131,110 @@
131131 config UML_NET
132132 	bool "Virtual network device"
133133 	help
134
-        While the User-Mode port cannot directly talk to any physical
135
-        hardware devices, this choice and the following transport options
136
-        provide one or more virtual network devices through which the UML
137
-        kernels can talk to each other, the host, and with the host's help,
138
-        machines on the outside world.
134
+	  While the User-Mode port cannot directly talk to any physical
135
+	  hardware devices, this choice and the following transport options
136
+	  provide one or more virtual network devices through which the UML
137
+	  kernels can talk to each other, the host, and with the host's help,
138
+	  machines on the outside world.
139139 
140
-        For more information, including explanations of the networking and
141
-        sample configurations, see
142
-        <http://user-mode-linux.sourceforge.net/old/networking.html>.
140
+	  For more information, including explanations of the networking and
141
+	  sample configurations, see
142
+	  <http://user-mode-linux.sourceforge.net/old/networking.html>.
143143 
144
-        If you'd like to be able to enable networking in the User-Mode
145
-        linux environment, say Y; otherwise say N.  Note that you must
146
-        enable at least one of the following transport options to actually
147
-        make use of UML networking.
144
+	  If you'd like to be able to enable networking in the User-Mode
145
+	  linux environment, say Y; otherwise say N.  Note that you must
146
+	  enable at least one of the following transport options to actually
147
+	  make use of UML networking.
148148 
149149 config UML_NET_ETHERTAP
150
-	bool "Ethertap transport"
150
+	bool "Ethertap transport (obsolete)"
151151 	depends on UML_NET
152152 	help
153
-        The Ethertap User-Mode Linux network transport allows a single
154
-        running UML to exchange packets with its host over one of the
155
-        host's Ethertap devices, such as /dev/tap0.  Additional running
156
-        UMLs can use additional Ethertap devices, one per running UML.
157
-        While the UML believes it's on a (multi-device, broadcast) virtual
158
-        Ethernet network, it's in fact communicating over a point-to-point
159
-        link with the host.
153
+	  The Ethertap User-Mode Linux network transport allows a single
154
+	  running UML to exchange packets with its host over one of the
155
+	  host's Ethertap devices, such as /dev/tap0.  Additional running
156
+	  UMLs can use additional Ethertap devices, one per running UML.
157
+	  While the UML believes it's on a (multi-device, broadcast) virtual
158
+	  Ethernet network, it's in fact communicating over a point-to-point
159
+	  link with the host.
160160 
161
-        To use this, your host kernel must have support for Ethertap
162
-        devices.  Also, if your host kernel is 2.4.x, it must have
163
-        CONFIG_NETLINK_DEV configured as Y or M.
161
+	  To use this, your host kernel must have support for Ethertap
162
+	  devices.  Also, if your host kernel is 2.4.x, it must have
163
+	  CONFIG_NETLINK_DEV configured as Y or M.
164164 
165
-        For more information, see
166
-        <http://user-mode-linux.sourceforge.net/old/networking.html>  That site
167
-        has examples of the UML command line to use to enable Ethertap
168
-        networking.
165
+	  For more information, see
166
+	  <http://user-mode-linux.sourceforge.net/old/networking.html>  That site
167
+	  has examples of the UML command line to use to enable Ethertap
168
+	  networking.
169169 
170
-        If you'd like to set up an IP network with the host and/or the
171
-        outside world, say Y to this, the Daemon Transport and/or the
172
-        Slip Transport.  You'll need at least one of them, but may choose
173
-        more than one without conflict.  If you don't need UML networking,
174
-        say N.
170
+	  NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
171
+	  migrate to UML_NET_VECTOR.
172
+
173
+	  If unsure, say N.
175174 
176175 config UML_NET_TUNTAP
177
-	bool "TUN/TAP transport"
176
+	bool "TUN/TAP transport (obsolete)"
178177 	depends on UML_NET
179178 	help
180
-        The UML TUN/TAP network transport allows a UML instance to exchange
181
-        packets with the host over a TUN/TAP device.  This option will only
182
-        work with a 2.4 host, unless you've applied the TUN/TAP patch to
183
-        your 2.2 host kernel.
179
+	  The UML TUN/TAP network transport allows a UML instance to exchange
180
+	  packets with the host over a TUN/TAP device.  This option will only
181
+	  work with a 2.4 host, unless you've applied the TUN/TAP patch to
182
+	  your 2.2 host kernel.
184183 
185
-        To use this transport, your host kernel must have support for TUN/TAP
186
-        devices, either built-in or as a module.
184
+	  To use this transport, your host kernel must have support for TUN/TAP
185
+	  devices, either built-in or as a module.
186
+
187
+	  NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
188
+	  migrate to UML_NET_VECTOR.
189
+
190
+	  If unsure, say N.
187191 
188192 config UML_NET_SLIP
189
-	bool "SLIP transport"
193
+	bool "SLIP transport (obsolete)"
190194 	depends on UML_NET
191195 	help
192
-        The slip User-Mode Linux network transport allows a running UML to
193
-        network with its host over a point-to-point link.  Unlike Ethertap,
194
-        which can carry any Ethernet frame (and hence even non-IP packets),
195
-        the slip transport can only carry IP packets.
196
+	  The slip User-Mode Linux network transport allows a running UML to
197
+	  network with its host over a point-to-point link.  Unlike Ethertap,
198
+	  which can carry any Ethernet frame (and hence even non-IP packets),
199
+	  the slip transport can only carry IP packets.
196200 
197
-        To use this, your host must support slip devices.
201
+	  To use this, your host must support slip devices.
198202 
199
-        For more information, see
200
-        <http://user-mode-linux.sourceforge.net/old/networking.html>.
201
-        has examples of the UML command line to use to enable slip
202
-        networking, and details of a few quirks with it.
203
+	  For more information, see
204
+	  <http://user-mode-linux.sourceforge.net/old/networking.html>.
205
+	  has examples of the UML command line to use to enable slip
206
+	  networking, and details of a few quirks with it.
203207 
204
-        The Ethertap Transport is preferred over slip because of its
205
-        limitations.  If you prefer slip, however, say Y here.  Otherwise
206
-        choose the Multicast transport (to network multiple UMLs on
207
-        multiple hosts), Ethertap (to network with the host and the
208
-        outside world), and/or the Daemon transport (to network multiple
209
-        UMLs on a single host).  You may choose more than one without
210
-        conflict.  If you don't need UML networking, say N.
208
+	  NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
209
+	  migrate to UML_NET_VECTOR.
210
+
211
+	  If unsure, say N.
211212 
212213 config UML_NET_DAEMON
213
-	bool "Daemon transport"
214
+	bool "Daemon transport (obsolete)"
214215 	depends on UML_NET
215216 	help
216
-        This User-Mode Linux network transport allows one or more running
217
-        UMLs on a single host to communicate with each other, but not to
218
-        the host.
217
+	  This User-Mode Linux network transport allows one or more running
218
+	  UMLs on a single host to communicate with each other, but not to
219
+	  the host.
219220 
220
-        To use this form of networking, you'll need to run the UML
221
-        networking daemon on the host.
221
+	  To use this form of networking, you'll need to run the UML
222
+	  networking daemon on the host.
222223 
223
-        For more information, see
224
-        <http://user-mode-linux.sourceforge.net/old/networking.html>  That site
225
-        has examples of the UML command line to use to enable Daemon
226
-        networking.
224
+	  For more information, see
225
+	  <http://user-mode-linux.sourceforge.net/old/networking.html>  That site
226
+	  has examples of the UML command line to use to enable Daemon
227
+	  networking.
227228 
228
-        If you'd like to set up a network with other UMLs on a single host,
229
-        say Y.  If you need a network between UMLs on multiple physical
230
-        hosts, choose the Multicast Transport.  To set up a network with
231
-        the host and/or other IP machines, say Y to the Ethertap or Slip
232
-        transports.  You'll need at least one of them, but may choose
233
-        more than one without conflict.  If you don't need UML networking,
234
-        say N.
229
+	  NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
230
+	  migrate to UML_NET_VECTOR.
231
+
232
+	  If unsure, say N.
235233 
236234 config UML_NET_VECTOR
237235 	bool "Vector I/O high performance network devices"
238236 	depends on UML_NET
237
+	select MAY_HAVE_RUNTIME_DEPS
239238 	help
240239 	This User-Mode Linux network driver uses multi-message send
241240 	and receive functions. The host running the UML guest must have
....@@ -245,8 +244,9 @@
245244 	drivers.
246245 
247246 config UML_NET_VDE
248
-	bool "VDE transport"
247
+	bool "VDE transport (obsolete)"
249248 	depends on UML_NET
249
+	select MAY_HAVE_RUNTIME_DEPS
250250 	help
251251 	This User-Mode Linux network transport allows one or more running
252252 	UMLs on a single host to communicate with each other and also
....@@ -263,75 +263,86 @@
263263 	That site has a good overview of what VDE is and also examples
264264 	of the UML command line to use to enable VDE networking.
265265 
266
-	If you need UML networking with VDE,
267
-	say Y.
266
+	NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
267
+	migrate to UML_NET_VECTOR.
268
+
269
+	If unsure, say N.
268270 
269271 config UML_NET_MCAST
270
-	bool "Multicast transport"
272
+	bool "Multicast transport (obsolete)"
271273 	depends on UML_NET
272274 	help
273
-        This Multicast User-Mode Linux network transport allows multiple
274
-        UMLs (even ones running on different host machines!) to talk to
275
-        each other over a virtual ethernet network.  However, it requires
276
-        at least one UML with one of the other transports to act as a
277
-        bridge if any of them need to be able to talk to their hosts or any
278
-        other IP machines.
275
+	  This Multicast User-Mode Linux network transport allows multiple
276
+	  UMLs (even ones running on different host machines!) to talk to
277
+	  each other over a virtual ethernet network.  However, it requires
278
+	  at least one UML with one of the other transports to act as a
279
+	  bridge if any of them need to be able to talk to their hosts or any
280
+	  other IP machines.
279281 
280
-        To use this, your host kernel(s) must support IP Multicasting.
282
+	  To use this, your host kernel(s) must support IP Multicasting.
281283 
282
-        For more information, see
283
-        <http://user-mode-linux.sourceforge.net/old/networking.html>  That site
284
-        has examples of the UML command line to use to enable Multicast
285
-        networking, and notes about the security of this approach.
284
+	  For more information, see
285
+	  <http://user-mode-linux.sourceforge.net/old/networking.html>  That site
286
+	  has examples of the UML command line to use to enable Multicast
287
+	  networking, and notes about the security of this approach.
286288 
287
-        If you need UMLs on multiple physical hosts to communicate as if
288
-        they shared an Ethernet network, say Y.  If you need to communicate
289
-        with other IP machines, make sure you select one of the other
290
-        transports (possibly in addition to Multicast; they're not
291
-        exclusive).  If you don't need to network UMLs say N to each of
292
-        the transports.
289
+	  NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
290
+	  migrate to UML_NET_VECTOR.
291
+
292
+	  If unsure, say N.
293293 
294294 config UML_NET_PCAP
295
-	bool "pcap transport"
295
+	bool "pcap transport (obsolete)"
296296 	depends on UML_NET
297
+	select MAY_HAVE_RUNTIME_DEPS
297298 	help
298299 	The pcap transport makes a pcap packet stream on the host look
299300 	like an ethernet device inside UML.  This is useful for making
300301 	UML act as a network monitor for the host.  You must have libcap
301302 	installed in order to build the pcap transport into UML.
302303 
303
-        For more information, see
304
-        <http://user-mode-linux.sourceforge.net/old/networking.html>  That site
305
-        has examples of the UML command line to use to enable this option.
304
+	  For more information, see
305
+	  <http://user-mode-linux.sourceforge.net/old/networking.html>  That site
306
+	  has examples of the UML command line to use to enable this option.
306307 
307
-	If you intend to use UML as a network monitor for the host, say
308
-	Y here.  Otherwise, say N.
308
+	NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
309
+	migrate to UML_NET_VECTOR.
310
+
311
+	If unsure, say N.
309312 
310313 config UML_NET_SLIRP
311
-	bool "SLiRP transport"
314
+	bool "SLiRP transport (obsolete)"
312315 	depends on UML_NET
313316 	help
314
-        The SLiRP User-Mode Linux network transport allows a running UML
315
-        to network by invoking a program that can handle SLIP encapsulated
316
-        packets.  This is commonly (but not limited to) the application
317
-        known as SLiRP, a program that can re-socket IP packets back onto
318
-        the host on which it is run.  Only IP packets are supported,
319
-        unlike other network transports that can handle all Ethernet
320
-        frames.  In general, slirp allows the UML the same IP connectivity
321
-        to the outside world that the host user is permitted, and unlike
322
-        other transports, SLiRP works without the need of root level
323
-        privleges, setuid binaries, or SLIP devices on the host.  This
324
-        also means not every type of connection is possible, but most
325
-        situations can be accommodated with carefully crafted slirp
326
-        commands that can be passed along as part of the network device's
327
-        setup string.  The effect of this transport on the UML is similar
328
-        that of a host behind a firewall that masquerades all network
329
-        connections passing through it (but is less secure).
317
+	  The SLiRP User-Mode Linux network transport allows a running UML
318
+	  to network by invoking a program that can handle SLIP encapsulated
319
+	  packets.  This is commonly (but not limited to) the application
320
+	  known as SLiRP, a program that can re-socket IP packets back onto
321
+	  he host on which it is run.  Only IP packets are supported,
322
+	  unlike other network transports that can handle all Ethernet
323
+	  frames.  In general, slirp allows the UML the same IP connectivity
324
+	  to the outside world that the host user is permitted, and unlike
325
+	  other transports, SLiRP works without the need of root level
326
+	  privleges, setuid binaries, or SLIP devices on the host.  This
327
+	  also means not every type of connection is possible, but most
328
+	  situations can be accommodated with carefully crafted slirp
329
+	  commands that can be passed along as part of the network device's
330
+	  setup string.  The effect of this transport on the UML is similar
331
+	  that of a host behind a firewall that masquerades all network
332
+	  connections passing through it (but is less secure).
330333 
331
-        To use this you should first have slirp compiled somewhere
332
-        accessible on the host, and have read its documentation.  If you
333
-        don't need UML networking, say N.
334
+	  NOTE: THIS TRANSPORT IS DEPRECATED AND WILL BE REMOVED SOON!!! Please
335
+	  migrate to UML_NET_VECTOR.
334336 
335
-        Startup example: "eth0=slirp,FE:FD:01:02:03:04,/usr/local/bin/slirp"
337
+	  If unsure, say N.
338
+
339
+	  Startup example: "eth0=slirp,FE:FD:01:02:03:04,/usr/local/bin/slirp"
336340 
337341 endmenu
342
+
343
+config VIRTIO_UML
344
+	bool "UML driver for virtio devices"
345
+	select VIRTIO
346
+	help
347
+	  This driver provides support for virtio based paravirtual device
348
+	  drivers over vhost-user sockets.