This selects whether you want to include the driver for the standard serial ports. The standard answer is Y. People who might say N here are those that are setting up dedicated Ethernet WWW/FTP servers, or users that have one of the various bus mice instead of a serial mouse and don't intend to use their machine's standard serial port for anything. (Note that the Cyclades and Stallion multi serial port drivers do not need this driver built in for them to work.) To compile this driver as a module, choose M here: the module will be called 8250. [WARNING: Do not compile this driver as a module if you are using non-standard serial ports, since the configuration information will be lost when the driver is unloaded. This limitation may be lifted in the future.] BTW1: If you have a mouseman serial mouse which is not recognized by the X window system, try running gpm first. BTW2: If you intend to use a software modem (also called Winmodem) under Linux, forget it. These modems are crippled and require proprietary drivers which are only available under Windows. Most people will say Y or M here, so that they can use serial mice, modems and similar devices connecting to the standard serial ports.
If you say Y here, it will be possible to use a serial port as the system console (the system console is the device which receives all kernel messages and warnings and which allows logins in single user mode). This could be useful if some terminal or printer is connected to that serial port. Even if you say Y here, the currently visible virtual console (/dev/tty0) will still be used as the system console by default, but you can alter that using a kernel command line option such as "console=ttyS1". (Try "man bootparam" or see the documentation of your boot loader (grub or lilo or loadlin) about how to pass options to the kernel at boot time.) If you don't have a VGA card installed and you say Y here, the kernel will automatically use the first serial line, /dev/ttyS0, as system console. You can set that using a kernel command line option such as "console=uart8250,io,0x3f8,9600n8" "console=uart8250,mmio,0xff5e0000,115200n8". and it will switch to normal serial console when the corresponding port is ready. "earlycon=uart8250,io,0x3f8,9600n8" "earlycon=uart8250,mmio,0xff5e0000,115200n8". it will not only setup early console. If unsure, say N.
This builds standard PCI serial support. You may be able to disable this feature if you only need legacy serial support. Saves about 9K.
This builds standard PNP serial support. You may be able to disable this feature if you only need legacy serial support.
Say Y here to enable support for 16-bit PCMCIA serial devices, including serial port cards, modems, and the modem functions of multi-function Ethernet/modem cards. (PCMCIA- or PC-cards are credit-card size devices often used with laptops.) To compile this driver as a module, choose M here: the module will be called serial_cs. If unsure, say N.
Set this to the number of serial ports you want the driver to support. This includes any ports discovered via ACPI or PCI enumeration and any ports that may be added at run-time via hot-plug, or any ISA multi-port serial cards.
Set this to the maximum number of serial ports you want the kernel to register at boot time. This can be overridden with the module parameter "nr_uarts", or boot-time parameter 8250.nr_uarts
If you wish to use any non-standard features of the standard "dumb" driver, say Y here. This includes HUB6 support, shared serial interrupts, special multiport support, support for more than the four COM 1/2/3/4 boards, etc. 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 serial driver options. If unsure, say N.
Say Y here if you have dumb serial boards other than the four standard COM 1/2/3/4 ports. This may happen if you have an AST FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available from <http://www.tldp.org/docs.html#howto>), or other custom serial port hardware which acts similar to standard serial port hardware. If you only use the standard COM 1/2/3/4 ports, you can say N here to save some memory. You can also say Y if you have an "intelligent" multiport card such as Cyclades, Digiboards, etc.
Say Y here if you have an AST FourPort serial board. To compile this driver as a module, choose M here: the module will be called 8250_fourport.
Say Y here if you have an Accent Async serial board. To compile this driver as a module, choose M here: the module will be called 8250_accent.
Say Y here if you have a Boca serial board. Please read the Boca mini-HOWTO, available from <http://www.tldp.org/docs.html#howto> To compile this driver as a module, choose M here: the module will be called 8250_boca.
The Uplogix Envoy TU301 uses this Exar Quad UART. If you are tinkering with your Envoy TU301, or have a machine with this UART, say Y here. To compile this driver as a module, choose M here: the module will be called 8250_exar_st16c554.
Say Y here if you have a HUB6 serial board. To compile this driver as a module, choose M here: the module will be called 8250_hub6.
Some serial boards have hardware support which allows multiple dumb serial ports on the same board to share a single IRQ. To enable support for this in the serial driver, say Y here.
Say Y here if you want the kernel to try to guess which IRQ to use for your serial port. This is considered unsafe; it is far better to configure the IRQ in a boot script using the setserial command. If unsure, say N.
::: To be written :::
Say Y here if you have a MCA serial ports. To compile this driver as a module, choose M here: the module will be called 8250_mca.
If you have an Atomwide Serial card or Serial Port card for an Acorn system, say Y to this option. The driver can handle 1, 2, or 3 port cards. If unsure, say N.
Selecting this option will add support for the integrated serial port hardware found on MIPS RM9122 and similar processors. If unsure, say N.
This selects the ARM(R) AMBA(R) PrimeCell PL010 UART. If you have an Integrator/AP or Integrator/PP2 platform, or if you have a Cirrus Logic EP93xx CPU, say Y or M here. If unsure, say N.
Say Y here if you wish to use an AMBA PrimeCell UART as the system console (the system console is the device which receives all kernel messages and warnings and which allows logins in single user mode). Even if you say Y here, the currently visible framebuffer console (/dev/tty0) will still be used as the system console by default, but you can alter that using a kernel command line option such as "console=ttyAM0". (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.)
This selects the ARM(R) AMBA(R) PrimeCell PL011 UART. If you have an Integrator/PP2, Integrator/CP or Versatile platform, say Y or M here. If unsure, say N.
Say Y here if you wish to use an AMBA PrimeCell UART as the system console (the system console is the device which receives all kernel messages and warnings and which allows logins in single user mode). Even if you say Y here, the currently visible framebuffer console (/dev/tty0) will still be used as the system console by default, but you can alter that using a kernel command line option such as "console=ttyAMA0". (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.)
Support for the asynchronous serial interface (DUART) included in the BCM1250 and derived System-On-a-Chip (SOC) devices. Note that the letter D in DUART stands for "dual", which is how the device is implemented. Depending on the SOC configuration there may be one or more DUARTs available of which all are handled. If unsure, say Y. To compile this driver as a module, choose M here: the module will be called sb1250-duart.
If you say Y here, it will be possible to use a serial port as the system console (the system console is the device which receives all kernel messages and warnings and which allows logins in single user mode). If unsure, say Y.
This enables the driver for the on-chip UARTs of the Atmel AT91 and AT32 processors.
Say Y here if you wish to use an on-chip UART on a Atmel AT91 or AT32 processor as the system console (the system console is the device which receives all kernel messages and warnings and which allows logins in single user mode).
Say Y here if you wish to use the PDC to do DMA transfers to and from the Atmel AT91 / AT32 serial port. In order to actually use DMA transfers, make sure that the use_dma_tx and use_dma_rx members in the atmel_uart_data struct is set appropriately for each port. Note that break and error handling currently doesn't work properly when DMA is enabled. Make sure that ports where this matters don't use DMA.
Say Y here if you wish to have the internal AT91 / AT32 UARTs appear as /dev/ttyATn (major 204, minor starting at 154) instead of the normal /dev/ttySn (major 4, minor starting at 64). This is necessary if you also want other UARTs, such as external 8250/16C550 compatible UARTs. The ttySn nodes are legally reserved for the 8250 serial driver but are often misused by other serial drivers. To use this, you should create suitable ttyATn device nodes in /dev/, and pass "console=ttyATn" to the kernel. Say Y if you have an external 8250/16C550 UART. If unsure, say N.
This selects the Micrel Centaur KS8695 UART. Say Y here.
Say Y here if you wish to use a KS8695 (Centaur) UART as the system console (the system console is the device which receives all kernel messages and warnings and which allows logins in single user mode).
::: To be written :::
Even if you say Y here, the currently visible virtual console (/dev/tty0) will still be used as the system console by default, but you can alter that using a kernel command line option such as "console=ttyCL1". (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.)
Support for the on-chip UARTs on the Samsung S3C24XX series CPUs, providing /dev/ttySAC0, 1 and 2 (note, some machines may not provide all of these ports, depending on how the serial port pins are configured.
Internal node for the common case of 4 Samsung compatible UARTs
Select the number of available UART ports for the Samsung S3C serial driver
Add support for debugging the serial driver. Since this is generally being used as a console, we use our own output routines that go via the low-level debug printascii() function.
Allow selection of the S3C24XX on-board serial ports for use as an virtual console. Even if you say Y here, the currently visible virtual console (/dev/tty0) will still be used as the system console by default, but you can alter that using a kernel command line option such as "console=ttySACx". (Try "man bootparam" or see the documentation of your boot loader about how to pass options to the kernel at boot time.)
Serial port support for the Samsung S3C2400 SoC
Serial port support for the Samsung S3C2410 SoC
Serial port support for the Samsung S3C2412 and S3C2413 SoC
Serial port support for the Samsung S3C2440, S3C2416 and S3C2442 SoC
Serial port support for the Samsung S3C24A0 SoC
Serial port support for the Samsung S3C6400, S3C6410, S5P6440, S5P6450 and S5PC100 SoCs
Serial port support for Samsung's S5P Family of SoC's
MAX3100 chip support
MAX3107 chip support
Support for the MAX3107 chip configuration found on the AAVA platform. Includes the extra initialisation and GPIO support neded for this device.
DZ11-family serial controllers for DECstations and VAXstations, including the DC7085, M7814, and M7819.
If you say Y here, it will be possible to use a serial port as the system console (the system console is the device which receives all kernel messages and warnings and which allows logins in single user mode). Note that the firmware uses ttyS3 as the serial console on DECstations that use this driver. If unsure, say Y.
Support for the Zilog 85C350 serial communications controller used for serial ports in newer DECstation systems. These include the DECsystem 5900 and all models of the DECstation and DECsystem 5000 systems except from model 200. If unsure, say Y. To compile this driver as a module, choose M here: the module will be called zs.
If you say Y here, it will be possible to use a serial port as the system console (the system console is the device which receives all kernel messages and warnings and which allows logins in single user mode). Note that the firmware uses ttyS1 as the serial console on the Maxine and ttyS3 on the others using this driver. If unsure, say Y.
If you have a machine based on a 21285 (Footbridge) StrongARM(R)/ PCI bridge you can enable its onboard serial port by enabling this option.
If you have enabled the serial port on the 21285 footbridge you can make it the console by answering Y to this option. Even if you say Y here, the currently visible virtual console (/dev/tty0) will still be used as the system console by default, but you can alter that using a kernel command line option such as "console=ttyFB". (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.)
Say Y here if you want to use the Marvell MPSC serial controller.
Say Y here if you want to support a serial console on a Marvell MPSC.
If you have a machine based on an Intel XScale PXA2xx CPU you can enable its onboard serial ports by enabling this option.
If you have enabled the serial port on the Intel XScale PXA CPU you can make it the console by answering Y to this option. Even if you say Y here, the currently visible virtual console (/dev/tty0) will still be used as the system console by default, but you can alter that using a kernel command line option such as "console=ttySA0". (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 you have a machine based on a SA1100/SA1110 StrongARM(R) CPU you can enable its onboard serial port by enabling this option. Please read <file:Documentation/arm/SA1100/serial_UART> for further info.
If you have enabled the serial port on the SA1100/SA1110 StrongARM CPU you can make it the console by answering Y to this option. Even if you say Y here, the currently visible virtual console (/dev/tty0) will still be used as the system console by default, but you can alter that using a kernel command line option such as "console=ttySA0". (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.)
This is the UART protocol driver for the MAX3110 device on the Intel Moorestown platform. On other systems use the max3100 driver.
Add support for the built-in UARTs on the Blackfin. To compile this driver as a module, choose M here: the module will be called bfin_5xx.
This driver supports the built-in serial ports of the Blackfin family of CPUs
This driver works under DMA mode. If this option is selected, the blackfin simple dma driver is also enabled.
This driver works under PIO mode.
Enable UART0
Enable hardware flow control in the driver.
Enable UART1
Enable hardware flow control in the driver.
Enable UART2
Enable hardware flow control in the driver.
Enable UART3
Enable hardware flow control in the driver.
If you have a machine based on a Motorola IMX CPU you can enable its onboard serial port by enabling this option.
If you have enabled the serial port on the Motorola IMX CPU you can make it the console by answering Y to this option. Even if you say Y here, the currently visible virtual console (/dev/tty0) will still be used as the system console by default, but you can alter that using a kernel command line option such as "console=ttySA0". (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.)
Say Y here if you want to use the Xilinx uartlite serial controller. To compile this driver as a module, choose M here: the module will be called uartlite.
Say Y here if you wish to use a Xilinx uartlite as the system console (the system console is the device which receives all kernel messages and warnings and which allows logins in single user mode).
This driver supports the Zilog8530 serial ports found on many Sparc systems. Say Y or M if you want to be able to these serial ports.
If you would like to be able to use the Zilog8530 serial port on your Sparc system as the console, you can do so by answering Y to this option.
This driver supports the 8250 serial ports that run the keyboard and mouse on (PCI) UltraSPARC systems. Say Y or M if you want to be able to these serial ports.
If you would like to be able to use the SU serial port on your Sparc system as the console, you can do so by answering Y to this option.
Saying Y here will enable the hardware MUX serial driver for the Nova, K class systems and D class with a 'remote control card'. The hardware MUX is not 8250/16550 compatible therefore the /dev/ttyB0 device is shared between the Serial MUX and the PDC software console. The following steps need to be completed to use the Serial MUX: 1. create the device entry (mknod /dev/ttyB0 c 11 0) 2. Edit the /etc/inittab to start a getty listening on /dev/ttyB0 3. Add device ttyB0 to /etc/securetty (if you want to log on as root on this console.) 4. Change the kernel command console parameter to: console=ttyB0
Saying Y here will enable the software based PDC console to be used as the system console. This is useful for machines in which the hardware based console has not been written yet. The following steps must be competed to use the PDC console: 1. create the device entry (mknod /dev/ttyB0 c 11 0) 2. Edit the /etc/inittab to start a getty listening on /dev/ttyB0 3. Add device ttyB0 to /etc/securetty (if you want to log on as root on this console.) 4. Change the kernel command console parameter to: console=ttyB0
This driver supports the Siemens SAB82532 DUSCC serial ports on newer (PCI) UltraSPARC systems. Say Y or M if you want to be able to these serial ports.
If you would like to be able to use the SAB82532 serial port on your Sparc system as the console, you can do so by answering Y to this option.
This driver supports the console device found on SUN4V Sparc systems. Say Y if you want to be able to use this device.
This driver supports the Zilog8530 serial ports found on SGI systems. Say Y or M if you want to be able to these serial ports.
If you have a MIPS-based Philips SoC such as PNX8550 or PNX8330 and you want to use serial ports, say Y. Otherwise, say N.
If you have a MIPS-based Philips SoC such as PNX8550 or PNX8330 and you want to use serial console, say Y. Otherwise, say N.
This driver supports the built-in serial port of the Motorola 68328 (standard, EZ and VZ varieties).
This serial driver supports the Freescale Coldfire serial ports.
This setting lets you define what the default baudrate is for the ColdFire serial ports. The usual default varies from board to board, and this setting is a way of catering for that.
Enable a ColdFire internal serial port to be the system console.
This driver supports the SMC serial ports of the Motorola 68360 CPU.
This driver supports the SCC serial ports of the Motorola 68360 CPU.
This driver supports the Zilog z85C30 serial ports found on (Power)Mac machines. Say Y or M if you want to be able to these serial ports.
The pmac_zilog driver for the z85C30 chip on many powermacs historically used the device numbers for /dev/ttySn. The 8250 serial port driver also uses these numbers, which means the two drivers being unable to coexist; you could not use both z85C30 and 8250 type ports at the same time. If this option is not selected, the pmac_zilog driver will use the device numbers allocated for /dev/ttyPZn. This allows the pmac_zilog and 8250 drivers to co-exist, but may cause existing userspace setups to break. Programs that need to access the built-in serial ports on powermacs will need to be reconfigured to use /dev/ttyPZn instead of /dev/ttySn. If you enable this option, any z85c30 ports in the system will be registered as ttyS0 onwards as in the past, and you will be unable to use the 8250 module for PCMCIA or other 16C550-style UARTs. Say N unless you need the z85c30 ports on your (Power)Mac to appear as /dev/ttySn.
If you would like to be able to use the z85c30 serial port on your (Power)Mac as the console, you can do so by answering Y to this option.
This driver supports the SCC and SMC serial ports on Motorola embedded PowerPC that contain a CPM1 (8xx) or CPM2 (8xxx)
Say Y here if you wish to use a SCC or SMC CPM UART as the system console (the system console is the device which receives all kernel messages and warnings and which allows logins in single user mode). Even if you say Y here, the currently visible framebuffer console (/dev/tty0) will still be used as the system console by default, but you can alter that using a kernel command line option such as "console=ttyCPM0". (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 you have an SGI Altix and you would like to use the system controller serial port as your console (you want this!), say Y. Otherwise, say N.
This driver supports MPC52xx and MPC512x PSC serial ports. If you would like to use them, you must answer Y or M to this option. Note that for use as console, it must be included in kernel and not as a module.
Select this options if you'd like to use one of the PSC serial port of the Freescale MPC52xx family as a console.
Select the MPC52xx console baud rate. This value is only used if the bootloader doesn't pass in the console baudrate
This driver is for a family of multiport serial adapters including 2 port RVX, 2 port internal modem, 4 port internal modem and a split 1 port RVX and 1 port internal modem. This driver can also be built as a module. If so, the module will be called icom.
Say Y here if you want to use the M32R serial controller.
Say Y here if you want to support a serial console. If you use an M3T-M32700UT or an OPSPUT platform, please say also y for SERIAL_M32R_PLDSIO.
Say Y here if you want to use the M32R serial controller on a PLD (Programmable Logic Device). If you use an M3T-M32700UT or an OPSPUT platform, please say Y.
If you have a NEC VR4100 series processor and you want to use Serial Interface Unit(SIU) or Debug Serial Interface Unit(DSIU) (not include VR4111/VR4121 DSIU), say Y. Otherwise, say N.
If you have a NEC VR4100 series processor and you want to use a console on a serial port, say Y. Otherwise, say N.
This is a driver for Digi International's Neo series of cards which provide multiple serial ports. 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. This driver supports PCI boards only. If you have a card like this, say Y here, otherwise say N. To compile this driver as a module, choose M here: the module will be called jsm.
If you have an SGI Altix with an IOC4 based Base IO card and wish to use the serial ports on this card, say Y. Otherwise, say N.
If you have an SGI Altix with an IOC3 serial card, say Y or M. Otherwise, say N.
If you have a machine based on MSM family of SoCs, you can enable its onboard high speed serial port by enabling this option. Choose M here to compile it as a module. The module will be called msm_serial_hs.
If you have a machine based on a Hilscher NetX SoC you can enable its onboard serial port by enabling this option. To compile this driver as a module, choose M here: the module will be called netx-serial.
If you have enabled the serial port on the Hilscher NetX SoC you can make it the console by answering Y to this option.
If you have a PowerPC based system that has serial ports on a platform specific bus, you should enable this option. Currently, only 8250 compatible ports are supported, but others can easily be added.
If you have a machine based on an Texas Instruments OMAP CPU you can enable its onboard serial ports by enabling this option. By enabling this option you take advantage of dma feature available with the omap-serial driver. DMA support can be enabled from platform data.
Select this option if you would like to use omap serial port as console. Even if you say Y here, the currently visible virtual console (/dev/tty0) will still be used as the system console by default, but you can alter that using a kernel command line option such as "console=ttyOx". (Try "man bootparam" or see the documentation of your boot loader about how to pass options to the kernel at boot time.)
This driver supports the cell network processor nwp serial device.
Support for Console on the NWP serial ports.
Support for console and UART on Lantiq SoCs.
This driver supports the QE serial ports on Freescale embedded PowerPC that contain a QUICC Engine.
This is a driver for the onboard serial ports of older RM400 machines.
Support for Console on SC2681/SC2692 serial ports.
Enable SPORT emulate UART on Blackfin series. To compile this driver as a module, choose M here: the module will be called bfin_sport_uart.
Enable UART over SPORT0
Enable hardware flow control in the driver.
Enable UART over SPORT1
Enable hardware flow control in the driver.
Enable UART over SPORT2
Enable hardware flow control in the driver.
Enable UART over SPORT3
Enable hardware flow control in the driver.
Add support for UART controller on timberdale.
If you have a bcm63xx CPU, you can enable its onboard serial port by enabling this options. To compile this driver as a module, choose M here: the module will be called bcm963xx_uart.
If you have enabled the serial port on the bcm63xx CPU you can make it the console by answering Y to this option.
Add support for the GRLIB APBUART serial port.
Support for running a console on the GRLIB APBUART
This driver supports the Altera JTAG UART port.
Enable a Altera JTAG UART port to be the system console.
Bypass console output and keep going even if there is no JTAG terminal connection with the host.
This driver supports the Altera softcore UART port.
This setting lets you define the maximum number of the Altera UART ports. The usual default varies from board to board, and this setting is a way of catering for that.
This setting lets you define what the default baudrate is for the Altera UART ports. The usual default varies from board to board, and this setting is a way of catering for that.
Enable a Altera UART port to be the system console.
Support for the IFX6x60 modem devices on Intel MID platforms.
This driver is for PCH(Platform controller Hub) UART of Intel EG20T which is an IOH(Input/Output Hub) for x86 embedded processor. Enabling PCH_DMA, this PCH UART works as DMA mode. This driver also can be used for OKI SEMICONDUCTOR IOH(Input/ Output Hub), ML7213 and ML7223. ML7213 IOH is for IVI(In-Vehicle Infotainment) use and ML7223 IOH is for MP(Media Phone) use. ML7213/ML7223 is companion chip for Intel Atom E6xx series. ML7213/ML7223 is completely compatible for Intel EG20T PCH.
Enables userspace clients to read and write to some streaming SMD ports via tty device interface for MSM chipset.
This driver supports the MXS Application UART (AUART) port.
Enable a MXS AUART port to be the system console.
This driver supports the Xilinx PS UART port.
Enable a Xilinx PS UART port to be the system console.