Training courses

Kernel and Embedded Linux

Bootlin training courses

Embedded Linux, kernel,
Yocto Project, Buildroot, real-time,
graphics, boot time, debugging...

Bootlin logo

Elixir Cross Referencer

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
# SPDX-License-Identifier: GPL-2.0
config CONFIG_TTY
	bool "Enable TTY" if CONFIG_EXPERT
	default y
	---help---
	  Allows you to remove CONFIG_TTY support which can save space, and
	  blocks features that require CONFIG_TTY from inclusion in the kernel.
	  CONFIG_TTY is required for any text terminals or serial port
	  communication. Most users should leave this enabled.

if CONFIG_TTY

config CONFIG_VT
	bool "Virtual terminal" if CONFIG_EXPERT
	depends on !CONFIG_UML
	select CONFIG_INPUT
	default y
	---help---
	  If you say Y here, you will get support for terminal devices with
	  display and keyboard devices. These are called "virtual" because you
	  can run several virtual terminals (also called virtual consoles) on
	  one physical terminal. This is rather useful, for example one
	  virtual terminal can collect system messages and warnings, another
	  one can be used for a text-mode user session, and a third could run
	  an X session, all in parallel. Switching between virtual terminals
	  is done with certain key combinations, usually Alt-<function key>.

	  The setterm command ("man setterm") can be used to change the
	  properties (such as colors or beeping) of a virtual terminal. The
	  man page console_codes(4) ("man console_codes") contains the special
	  character sequences that can be used to change those properties
	  directly. The fonts used on virtual terminals can be changed with
	  the setfont ("man setfont") command and the key bindings are defined
	  with the loadkeys ("man loadkeys") command.

	  You need at least one virtual terminal device in order to make use
	  of your keyboard and monitor. Therefore, only people configuring an
	  embedded system would want to say N here in order to save some
	  memory; the only way to log into such a system is then via a serial
	  or network connection.

	  If unsure, say Y, or else you won't be able to do much with your new
	  shiny Linux system :-)

config CONFIG_CONSOLE_TRANSLATIONS
	depends on CONFIG_VT
	default y
	bool "Enable character translations in console" if CONFIG_EXPERT
	---help---
	  This enables support for font mapping and Unicode translation
	  on virtual consoles.

config CONFIG_VT_CONSOLE
	bool "Support for console on virtual terminal" if CONFIG_EXPERT
	depends on CONFIG_VT
	default y
	---help---
	  The system console is the device which receives all kernel messages
	  and warnings and which allows logins in single user mode. If you
	  answer Y here, a virtual terminal (the device used to interact with
	  a physical terminal) can be used as system console. This is the most
	  common mode of operations, so you should say Y here unless you want
	  the kernel messages be output only to a serial port (in which case
	  you should say Y to "Console on serial port", below).

	  If you do say Y here, by default the currently visible virtual
	  terminal (/dev/tty0) will be used as system console. You can change
	  that with a kernel command line option such as "console=tty3" which
	  would use the third virtual terminal as system console. (Try "man
	  bootparam" or see the documentation of your boot loader (lilo or
	  loadlin) about how to pass options to the kernel at boot time.)

	  If unsure, say Y.

config CONFIG_VT_CONSOLE_SLEEP
	def_bool y
	depends on CONFIG_VT_CONSOLE && CONFIG_PM_SLEEP

config CONFIG_HW_CONSOLE
	bool
	depends on CONFIG_VT && !CONFIG_UML
	default y

config CONFIG_VT_HW_CONSOLE_BINDING
       bool "Support for binding and unbinding console drivers"
       depends on CONFIG_HW_CONSOLE
       ---help---
         The virtual terminal is the device that interacts with the physical
         terminal through console drivers. On these systems, at least one
         console driver is loaded. In other configurations, additional console
         drivers may be enabled, such as the framebuffer console. If more than
         1 console driver is enabled, setting this to 'y' will allow you to
         select the console driver that will serve as the backend for the
         virtual terminals.

	 See <file:Documentation/driver-api/console.rst> for more
	 information. For framebuffer console users, please refer to
	 <file:Documentation/fb/fbcon.rst>.

config CONFIG_UNIX98_PTYS
	bool "Unix98 PTY support" if CONFIG_EXPERT
	default y
	---help---
	  CONFIG_A pseudo terminal (PTY) is a software device consisting of two
	  halves: a master and a slave. The slave device behaves identical to
	  a physical terminal; the master device is used by a process to
	  read data from and write data to the slave, thereby emulating a
	  terminal. Typical programs for the master side are telnet servers
	  and xterms.

	  Linux has traditionally used the BSD-like names /dev/ptyxx for
	  masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
	  has a number of problems. The GNU CONFIG_C library glibc 2.1 and later,
	  however, supports the Unix98 naming standard: in order to acquire a
	  pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
	  terminal is then made available to the process and the pseudo
	  terminal slave can be accessed as /dev/pts/<number>. What was
	  traditionally /dev/ttyp2 will then be /dev/pts/2, for example.

	  All modern Linux systems use the Unix98 ptys.  Say Y unless
	  you're on an embedded system and want to conserve memory.

config CONFIG_LEGACY_PTYS
	bool "Legacy (BSD) PTY support"
	default y
	---help---
	  CONFIG_A pseudo terminal (PTY) is a software device consisting of two
	  halves: a master and a slave. The slave device behaves identical to
	  a physical terminal; the master device is used by a process to
	  read data from and write data to the slave, thereby emulating a
	  terminal. Typical programs for the master side are telnet servers
	  and xterms.

	  Linux has traditionally used the BSD-like names /dev/ptyxx
	  for masters and /dev/ttyxx for slaves of pseudo
	  terminals. This scheme has a number of problems, including
	  security.  This option enables these legacy devices; on most
	  systems, it is safe to say N.


config CONFIG_LEGACY_PTY_COUNT
	int "Maximum number of legacy PTY in use"
	depends on CONFIG_LEGACY_PTYS
	range 0 256
	default "256"
	---help---
	  The maximum number of legacy PTYs that can be used at any one time.
	  The default is 256, and should be more than enough.  Embedded
	  systems may want to reduce this to save memory.

	  When not in use, each legacy PTY occupies 12 bytes on 32-bit
	  architectures and 24 bytes on 64-bit architectures.

config CONFIG_SERIAL_NONSTANDARD
	bool "Non-standard serial port support"
	depends on CONFIG_HAS_IOMEM
	---help---
	  Say Y here if you have any non-standard serial boards -- boards
	  which aren't supported using the standard "dumb" serial driver.
	  This includes intelligent serial boards such as Cyclades,
	  Digiboards, etc. These are usually used for systems that need many
	  serial ports because they serve many terminals or dial-in
	  connections.

	  Note that the answer to this question won't directly affect the
	  kernel: saying N will just cause the configurator to skip all
	  the questions about non-standard serial boards.

	  Most people can say N here.

config CONFIG_ROCKETPORT
	tristate "Comtrol RocketPort support"
	depends on CONFIG_SERIAL_NONSTANDARD && (CONFIG_ISA || CONFIG_EISA || CONFIG_PCI)
	help
	  This driver supports Comtrol RocketPort and RocketModem CONFIG_PCI boards.   
          These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
          modems.  For information about the RocketPort/RocketModem  boards
          and this driver read <file:Documentation/driver-api/serial/rocket.rst>.

	  To compile this driver as a module, choose CONFIG_M here: the
	  module will be called rocket.

	  If you want to compile this driver into the kernel, say Y here.  If
          you don't have a Comtrol RocketPort/RocketModem card installed, say N.

config CONFIG_CYCLADES
	tristate "Cyclades async mux support"
	depends on CONFIG_SERIAL_NONSTANDARD && (CONFIG_PCI || CONFIG_ISA)
	select CONFIG_FW_LOADER
	---help---
	  This driver supports Cyclades Z and Y multiserial boards.
	  You would need something like this to connect more than two modems to
	  your Linux box, for instance in order to become a dial-in server.

	  For information about the Cyclades-Z card, read
	  <file:Documentation/driver-api/serial/cyclades_z.rst>.

	  To compile this driver as a module, choose CONFIG_M here: the
	  module will be called cyclades.

	  If you haven't heard about it, it's safe to say N.

config CONFIG_CYZ_INTR
	bool "Cyclades-Z interrupt mode operation"
	depends on CONFIG_CYCLADES && CONFIG_PCI
	help
	  The Cyclades-Z family of multiport cards allows 2 (two) driver op
	  modes: polling and interrupt. In polling mode, the driver will check
	  the status of the Cyclades-Z ports every certain amount of time
	  (which is called polling cycle and is configurable). In interrupt
	  mode, it will use an interrupt line (IRQ) in order to check the
	  status of the Cyclades-Z ports. The default op mode is polling. If
	  unsure, say N.

config CONFIG_MOXA_INTELLIO
	tristate "Moxa Intellio support"
	depends on CONFIG_SERIAL_NONSTANDARD && (CONFIG_ISA || CONFIG_EISA || CONFIG_PCI)
	select CONFIG_FW_LOADER
	help
	  Say Y here if you have a Moxa Intellio multiport serial card.

	  To compile this driver as a module, choose CONFIG_M here: the
	  module will be called moxa.

config CONFIG_MOXA_SMARTIO
	tristate "Moxa SmartIO support v. 2.0"
	depends on CONFIG_SERIAL_NONSTANDARD && (CONFIG_PCI || CONFIG_EISA || CONFIG_ISA)
	help
	  Say Y here if you have a Moxa SmartIO multiport serial card and/or
	  want to help develop a new version of this driver.

	  This is upgraded (1.9.1) driver from original Moxa drivers with
	  changes finally resulting in CONFIG_PCI probing.

	  This driver can also be built as a module. The module will be called
	  mxser. If you want to do that, say CONFIG_M here.

config CONFIG_SYNCLINK
	tristate "Microgate SyncLink card support"
	depends on CONFIG_SERIAL_NONSTANDARD && CONFIG_PCI && CONFIG_ISA_DMA_API
	help
	  Provides support for the SyncLink CONFIG_ISA and CONFIG_PCI multiprotocol serial
	  adapters. These adapters support asynchronous and CONFIG_HDLC bit
	  synchronous communication up to 10Mbps (CONFIG_PCI adapter).

	  This driver can only be built as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
	  The module will be called synclink.  If you want to do that, say CONFIG_M
	  here.

config CONFIG_SYNCLINKMP
	tristate "SyncLink Multiport support"
	depends on CONFIG_SERIAL_NONSTANDARD && CONFIG_PCI
	help
	  Enable support for the SyncLink Multiport (2 or 4 ports)
	  serial adapter, running asynchronous and CONFIG_HDLC communications up
	  to 2.048Mbps. Each ports is independently selectable for
	  RS-232, V.35, RS-449, RS-530, and X.21

	  This driver may be built as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
	  The module will be called synclinkmp.  If you want to do that, say CONFIG_M
	  here.

config CONFIG_SYNCLINK_GT
	tristate "SyncLink GT/AC support"
	depends on CONFIG_SERIAL_NONSTANDARD && CONFIG_PCI
	help
	  Support for SyncLink GT and SyncLink AC families of
	  synchronous and asynchronous serial adapters
	  manufactured by Microgate Systems, Ltd. (www.microgate.com)

config CONFIG_NOZOMI
	tristate "HSDPA Broadband Wireless Data Card - Globe Trotter"
	depends on CONFIG_PCI
	help
	  If you have a HSDPA driver Broadband Wireless Data Card -
	  Globe Trotter CONFIG_PCMCIA card, say Y here.

	  To compile this driver as a module, choose CONFIG_M here, the module
	  will be called nozomi.

config CONFIG_ISI
	tristate "Multi-Tech multiport card support"
	depends on CONFIG_SERIAL_NONSTANDARD && CONFIG_PCI
	select CONFIG_FW_LOADER
	help
	  This is a driver for the Multi-Tech cards which provide several
	  serial ports.  The driver is experimental and can currently only be
	  built as a module. The module will be called isicom.
	  If you want to do that, choose CONFIG_M here.

config CONFIG_N_HDLC
	tristate "HDLC line discipline support"
	depends on CONFIG_SERIAL_NONSTANDARD
	help
	  Allows synchronous CONFIG_HDLC communications with tty device drivers that
	  support synchronous CONFIG_HDLC such as the Microgate SyncLink adapter.

	  This driver can be built as a module ( = code which can be
	  inserted in and removed from the running kernel whenever you want).
	  The module will be called n_hdlc. If you want to do that, say CONFIG_M
	  here.

config CONFIG_N_GSM
	tristate "GSM MUX line discipline support (EXPERIMENTAL)"
	depends on CONFIG_NET
	help
	  This line discipline provides support for the GSM MUX protocol and
	  presents the mux as a set of 61 individual tty devices.

config CONFIG_TRACE_ROUTER
	tristate "Trace data router for MIPI P1149.7 cJTAG standard"
	depends on CONFIG_TRACE_SINK
	help
	  The trace router uses the Linux tty line discipline framework to
	  route trace data coming from a tty port (say UART for example) to
	  the trace sink line discipline driver and to another tty port (say
	  CONFIG_USB). This is part of a solution for the MIPI P1149.7, compact JTAG,
	  standard, which is for debugging mobile devices. The PTI driver in
	  drivers/misc/pti.c defines the majority of this MIPI solution.

	  You should select this driver if the target kernel is meant for
	  a mobile device containing a modem.  Then you will need to select
	  "Trace data sink for MIPI P1149.7 cJTAG standard" line discipline
	  driver.

config CONFIG_TRACE_SINK
	tristate "Trace data sink for MIPI P1149.7 cJTAG standard"
	help
	  The trace sink uses the Linux line discipline framework to receive
	  trace data coming from the trace router line discipline driver
	  to a user-defined tty port target, like CONFIG_USB.
	  This is to provide a way to extract modem trace data on
	  devices that do not have a PTI HW module, or just need modem
	  trace data to come out of a different HW output port.
	  This is part of a solution for the P1149.7, compact JTAG, standard.

	  If you select this option, you need to select
	  "Trace data router for MIPI P1149.7 cJTAG standard".

config CONFIG_PPC_EPAPR_HV_BYTECHAN
	bool "ePAPR hypervisor byte channel driver"
	depends on CONFIG_PPC
	select CONFIG_EPAPR_PARAVIRT
	help
	  This driver creates /dev entries for each ePAPR hypervisor byte
	  channel, thereby allowing applications to communicate with byte
	  channels as if they were serial ports.

config CONFIG_PPC_EARLY_DEBUG_EHV_BC
	bool "Early console (udbg) support for ePAPR hypervisors"
	depends on CONFIG_PPC_EPAPR_HV_BYTECHAN=y
	help
	  Select this option to enable early console (a.k.a. "udbg") support
	  via an ePAPR byte channel.  You also need to choose the byte channel
	  handle below.

config CONFIG_PPC_EARLY_DEBUG_EHV_BC_HANDLE
	int "Byte channel handle for early console (udbg)"
	depends on CONFIG_PPC_EARLY_DEBUG_EHV_BC
	default 0
	help
	  If you want early console (udbg) output through a byte channel,
	  specify the handle of the byte channel to use.

	  For this to work, the byte channel driver must be compiled
	  in-kernel, not as a module.

	  Note that only one early console driver can be enabled, so don't
	  enable any others if you enable this one.

	  If the number you specify is not a valid byte channel handle, then
	  there simply will be no early console output.  This is true also
	  if you don't boot under a hypervisor at all.

config CONFIG_NULL_TTY
	tristate "NULL TTY driver"
	help
	  Say Y here if you want a NULL CONFIG_TTY which simply discards messages.

	  This is useful to allow userspace applications which expect a console
	  device to work without modifications even when no console is
	  available or desired.

	  In order to use this driver, you should redirect the console to this
	  CONFIG_TTY, or boot the kernel with console=ttynull.

	  If unsure, say N.

config CONFIG_GOLDFISH_TTY
	tristate "Goldfish TTY Driver"
	depends on CONFIG_GOLDFISH
	select CONFIG_SERIAL_CORE
	select CONFIG_SERIAL_CORE_CONSOLE
	help
	  Console and system CONFIG_TTY driver for the Goldfish virtual platform.

config CONFIG_GOLDFISH_TTY_EARLY_CONSOLE
	bool
	default y if CONFIG_GOLDFISH_TTY=y
	select CONFIG_SERIAL_EARLYCON

config CONFIG_MIPS_EJTAG_FDC_TTY
	bool "MIPS EJTAG Fast Debug Channel TTY"
	depends on CONFIG_MIPS_CDMM
	help
	  This enables a CONFIG_TTY and console on the CONFIG_MIPS EJTAG Fast Debug Channels,
	  if they are present. This can be useful when working with an EJTAG
	  probe which supports it, to get console output and a login prompt via
	  EJTAG without needing to connect a serial cable.

	  CONFIG_TTY devices are named e.g. ttyFDC3c2 (for FDC channel 2 of the FDC on
	  CPU3).

	  The console can be enabled with console=fdc1 (for FDC channel 1 on all
	  CPUs). Do not use the console unless there is a debug probe attached
	  to drain the FDC TX FIFO.

	  If unsure, say N.

config CONFIG_MIPS_EJTAG_FDC_EARLYCON
	bool "Early FDC console"
	depends on CONFIG_MIPS_EJTAG_FDC_TTY
	help
	  This registers a console on FDC channel 1 very early during boot (from
	  CONFIG_MIPS arch code). This is useful for bring-up and debugging early boot
	  issues.

	  Do not enable unless there is a debug probe attached to drain the FDC
	  TX FIFO.

	  If unsure, say N.

config CONFIG_MIPS_EJTAG_FDC_KGDB
	bool "Use KGDB over an FDC channel"
	depends on CONFIG_MIPS_EJTAG_FDC_TTY && CONFIG_KGDB
	default y
	help
          This enables the use of CONFIG_KGDB over an FDC channel, allowing CONFIG_KGDB to be
          used remotely or when a serial port isn't available.

config CONFIG_MIPS_EJTAG_FDC_KGDB_CHAN
	int "KGDB FDC channel"
	depends on CONFIG_MIPS_EJTAG_FDC_KGDB
	range 2 15
	default 3
	help
	  FDC channel number to use for CONFIG_KGDB.

config CONFIG_VCC
	tristate "Sun Virtual Console Concentrator"
	depends on CONFIG_SUN_LDOMS
	help
	  Support for Sun logical domain consoles.

config CONFIG_LDISC_AUTOLOAD
	bool "Automatically load TTY Line Disciplines"
	default y
	help
	  Historically the kernel has always automatically loaded any
	  line discipline that is in a kernel module when a user asks
	  for it to be loaded with the TIOCSETD ioctl, or through other
	  means.  This is not always the best thing to do on systems
	  where you know you will not be using some of the more
	  "ancient" line disciplines, so prevent the kernel from doing
	  this unless the request is coming from a process with the
	  CAP_SYS_MODULE permissions.

	  Say 'Y' here if you trust your userspace users to do the right
	  thing, or if you have only provided the line disciplines that
	  you know you will be using, or if you wish to continue to use
	  the traditional method of on-demand loading of these modules
	  by any user.

	  This functionality can be changed at runtime with the
	  dev.tty.ldisc_autoload sysctl, this configuration option will
	  only set the default value of this functionality.

endif # CONFIG_TTY