CONFIG_DEBUG_IOVIRT: Memory mapped I/O debugging

General informations

The Linux kernel configuration item CONFIG_DEBUG_IOVIRT has multiple definitions:

Memory mapped I/O debugging found in arch/m32r/Kconfig

The configuration item CONFIG_DEBUG_IOVIRT:

• prompt: Memory mapped I/O debugging
• type: bool
• depends on: CONFIG_DEBUG_KERNEL
• defined in arch/m32r/Kconfig
• found in Linux kernels: 2.6.9

Help text

Say Y here to get warned whenever an attempt is made to do I/O on obviously invalid addresses such as those generated when ioremap() calls are forgotten. Memory mapped I/O will go through an extra check to catch access to unmapped ISA addresses, an access method that can still be used by old drivers that are being ported from 2.0/2.2.

Memory mapped I/O debugging found in arch/i386/Kconfig

The configuration item CONFIG_DEBUG_IOVIRT:

• prompt: Memory mapped I/O debugging
• type: bool
• depends on: CONFIG_DEBUG_KERNEL
• defined in arch/i386/Kconfig
• found in Linux kernels: 2.5.45–2.5.75, 2.6.0–2.6.4

Help text

Say Y here to get warned whenever an attempt is made to do I/O on obviously invalid addresses such as those generated when ioremap() calls are forgotten. Memory mapped I/O will go through an extra check to catch access to unmapped ISA addresses, an access method that can still be used by old drivers that are being ported from 2.0/2.2.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: