CONFIG_PROVIDE_OHCI1394_DMA_INIT: Remote debugging over FireWire early on boot

General informations

The Linux kernel configuration item CONFIG_PROVIDE_OHCI1394_DMA_INIT has multiple definitions:

Remote debugging over FireWire early on boot found in lib/Kconfig.debug

The configuration item CONFIG_PROVIDE_OHCI1394_DMA_INIT:

• prompt: Remote debugging over FireWire early on boot
• type: bool
• depends on: CONFIG_PCI && CONFIG_X86
• defined in lib/Kconfig.debug
• found in Linux kernels: 2.6.26–2.6.39, 3.0–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.8, 6.9-rc+HEAD

Help text

If you want to debug problems which hang or crash the kernel early on boot and the crashing machine has a FireWire port, you can use this feature to remotely access the memory of the crashed machine over FireWire. This employs remote DMA as part of the OHCI1394 specification which is now the standard for FireWire controllers.

With remote DMA, you can monitor the printk buffer remotely using firescope and access all memory below 4GB using fireproxy from gdb. Even controlling a kernel debugger is possible using remote DMA.

Usage:

If ohci1394_dma=early is used as boot parameter, it will initialize all OHCI1394 controllers which are found in the PCI config space.

As all changes to the FireWire bus such as enabling and disabling devices cause a bus reset and thereby disable remote DMA for all devices, be sure to have the cable plugged and FireWire enabled on the debugging host before booting the debug target for debugging.

This code (~1k) is freed after boot. By then, the firewire stack in charge of the OHCI-1394 controllers should be used instead.

See Documentation/core-api/debugging-via-ohci1394.rst for more information.

Provide code for enabling DMA over FireWire early on boot found in lib/Kconfig.debug

The configuration item CONFIG_PROVIDE_OHCI1394_DMA_INIT:

• prompt: Provide code for enabling DMA over FireWire early on boot
• type: bool
• depends on: CONFIG_PCI && CONFIG_X86
• defined in lib/Kconfig.debug
• found in Linux kernels: 2.6.25

Help text

If you want to debug problems which hang or crash the kernel early on boot and the crashing machine has a FireWire port, you can use this feature to remotely access the memory of the crashed machine over FireWire. This employs remote DMA as part of the OHCI1394 specification which is now the standard for FireWire controllers.

With remote DMA, you can monitor the printk buffer remotely using firescope and access all memory below 4GB using fireproxy from gdb. Even controlling a kernel debugger is possible using remote DMA.

Usage:

If ohci1394_dma=early is used as boot parameter, it will initialize all OHCI1394 controllers which are found in the PCI config space.

As all changes to the FireWire bus such as enabling and disabling devices cause a bus reset and thereby disable remote DMA for all devices, be sure to have the cable plugged and FireWire enabled on the debugging host before booting the debug target for debugging.

This code (~1k) is freed after boot. By then, the firewire stack in charge of the OHCI-1394 controllers should be used instead.

See Documentation/debugging-via-ohci1394.txt for more information.

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: