€•ŠtŒsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”(hhŒparent”hubaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ3/translations/zh_CN/core-api/debugging-via-ohci1394”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”(hhhh2ubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ3/translations/zh_TW/core-api/debugging-via-ohci1394”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”(hhhhFubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ3/translations/it_IT/core-api/debugging-via-ohci1394”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”(hhhhZubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ3/translations/ja_JP/core-api/debugging-via-ohci1394”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”(hhhhnubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ3/translations/ko_KR/core-api/debugging-via-ohci1394”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”(hhhh‚ubah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ3/translations/sp_SP/core-api/debugging-via-ohci1394”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒKUsing physical DMA provided by OHCI-1394 FireWire controllers for debugging”h]”hŒKUsing physical DMA provided by OHCI-1394 FireWire controllers for debugging”…””}”(hhªhh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒM/var/lib/git/docbuild/linux/Documentation/core-api/debugging-via-ohci1394.rst”h Kubh¢)”}”(hhh]”(h§)”}”(hŒ Introduction”h]”hŒ Introduction”…””}”(hh¼hhºhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh·hžhhŸh¶h KubhŒ paragraph”“”)”}”(hXlBasically all FireWire controllers which are in use today are compliant to the OHCI-1394 specification which defines the controller to be a PCI bus master which uses DMA to offload data transfers from the CPU and has a "Physical Response Unit" which executes specific requests by employing PCI-Bus master DMA after applying filters defined by the OHCI-1394 driver.”h]”hXpBasically all FireWire controllers which are in use today are compliant to the OHCI-1394 specification which defines the controller to be a PCI bus master which uses DMA to offload data transfers from the CPU and has a “Physical Response Unit†which executes specific requests by employing PCI-Bus master DMA after applying filters defined by the OHCI-1394 driver.”…””}”(hhÌhhÊhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubhÉ)”}”(hŒùOnce properly configured, remote machines can send these requests to ask the OHCI-1394 controller to perform read and write requests on physical system memory and, for read requests, send the result of the physical memory read back to the requester.”h]”hŒùOnce properly configured, remote machines can send these requests to ask the OHCI-1394 controller to perform read and write requests on physical system memory and, for read requests, send the result of the physical memory read back to the requester.”…””}”(hhÚhhØhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubhÉ)”}”(hŒŽWith that, it is possible to debug issues by reading interesting memory locations such as buffers like the printk buffer or the process table.”h]”hŒŽWith that, it is possible to debug issues by reading interesting memory locations such as buffers like the printk buffer or the process table.”…””}”(hhèhhæhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubhÉ)”}”(hŒ‚Retrieving a full system memory dump is also possible over the FireWire, using data transfer rates in the order of 10MB/s or more.”h]”hŒ‚Retrieving a full system memory dump is also possible over the FireWire, using data transfer rates in the order of 10MB/s or more.”…””}”(hhöhhôhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubhÉ)”}”(hX With most FireWire controllers, memory access is limited to the low 4 GB of physical address space. This can be a problem on machines where memory is located mostly above that limit, but it is rarely a problem on more common hardware such as x86, x86-64 and PowerPC.”h]”hX With most FireWire controllers, memory access is limited to the low 4 GB of physical address space. This can be a problem on machines where memory is located mostly above that limit, but it is rarely a problem on more common hardware such as x86, x86-64 and PowerPC.”…””}”(hjhjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubhÉ)”}”(hŒAt least LSI FW643e and FW643e2 controllers are known to support access to physical addresses above 4 GB, but this feature is currently not enabled by Linux.”h]”hŒAt least LSI FW643e and FW643e2 controllers are known to support access to physical addresses above 4 GB, but this feature is currently not enabled by Linux.”…””}”(hjhjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khh·hžhubhÉ)”}”(hX€Together with a early initialization of the OHCI-1394 controller for debugging, this facility proved most useful for examining long debugs logs in the printk buffer on to debug early boot problems in areas like ACPI where the system fails to boot and other means for debugging (serial port) are either not available (notebooks) or too slow for extensive debug information (like ACPI).”h]”hX€Together with a early initialization of the OHCI-1394 controller for debugging, this facility proved most useful for examining long debugs logs in the printk buffer on to debug early boot problems in areas like ACPI where the system fails to boot and other means for debugging (serial port) are either not available (notebooks) or too slow for extensive debug information (like ACPI).”…””}”(hj hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K"hh·hžhubeh}”(h]”Œ introduction”ah ]”h"]”Œ introduction”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒDrivers”h]”hŒDrivers”…””}”(hj9hj7hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj4hžhhŸh¶h K)ubhÉ)”}”(hŒÝThe firewire-ohci driver in drivers/firewire uses filtered physical DMA by default, which is more secure but not suitable for remote debugging. Pass the remote_dma=1 parameter to the driver to get unfiltered physical DMA.”h]”hŒÝThe firewire-ohci driver in drivers/firewire uses filtered physical DMA by default, which is more secure but not suitable for remote debugging. Pass the remote_dma=1 parameter to the driver to get unfiltered physical DMA.”…””}”(hjGhjEhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K+hj4hžhubhÉ)”}”(hXBecause the firewire-ohci driver depends on the PCI enumeration to be completed, an initialization routine which runs pretty early has been implemented for x86. This routine runs long before console_init() can be called, i.e. before the printk buffer appears on the console.”h]”hXBecause the firewire-ohci driver depends on the PCI enumeration to be completed, an initialization routine which runs pretty early has been implemented for x86. This routine runs long before console_init() can be called, i.e. before the printk buffer appears on the console.”…””}”(hjUhjShžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K/hj4hžhubhÉ)”}”(hŒÉTo activate it, enable CONFIG_PROVIDE_OHCI1394_DMA_INIT (Kernel hacking menu: Remote debugging over FireWire early on boot) and pass the parameter "ohci1394_dma=early" to the recompiled kernel on boot.”h]”hŒÍTo activate it, enable CONFIG_PROVIDE_OHCI1394_DMA_INIT (Kernel hacking menu: Remote debugging over FireWire early on boot) and pass the parameter “ohci1394_dma=early†to the recompiled kernel on boot.”…””}”(hjchjahžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K4hj4hžhubeh}”(h]”Œdrivers”ah ]”h"]”Œdrivers”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K)ubh¢)”}”(hhh]”(h§)”}”(hŒTools”h]”hŒTools”…””}”(hj|hjzhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjwhžhhŸh¶h K9ubhÉ)”}”(hŒèfirescope - Originally developed by Benjamin Herrenschmidt, Andi Kleen ported it from PowerPC to x86 and x86_64 and added functionality, firescope can now be used to view the printk buffer of a remote machine, even with live update.”h]”hŒèfirescope - Originally developed by Benjamin Herrenschmidt, Andi Kleen ported it from PowerPC to x86 and x86_64 and added functionality, firescope can now be used to view the printk buffer of a remote machine, even with live update.”…””}”(hjŠhjˆhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K;hjwhžhubhÉ)”}”(hŒ‘Bernhard Kaindl enhanced firescope to support accessing 64-bit machines from 32-bit firescope and vice versa: - http://v3.sk/~lkundrak/firescope/”h]”(hŒpBernhard Kaindl enhanced firescope to support accessing 64-bit machines from 32-bit firescope and vice versa: - ”…””}”(hŒpBernhard Kaindl enhanced firescope to support accessing 64-bit machines from 32-bit firescope and vice versa: - ”hj–hžhhŸNh NubhŒ reference”“”)”}”(hŒ!http://v3.sk/~lkundrak/firescope/”h]”hŒ!http://v3.sk/~lkundrak/firescope/”…””}”(hhhj¡hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j£uh1jŸhj–ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K?hjwhžhubhÉ)”}”(hŒzand he implemented fast system dump (alpha version - read README.txt): - http://halobates.de/firewire/firedump-0.1.tar.bz2”h]”(hŒIand he implemented fast system dump (alpha version - read README.txt): - ”…””}”(hŒIand he implemented fast system dump (alpha version - read README.txt): - ”hj¶hžhhŸNh Nubj )”}”(hŒ1http://halobates.de/firewire/firedump-0.1.tar.bz2”h]”hŒ1http://halobates.de/firewire/firedump-0.1.tar.bz2”…””}”(hhhj¿hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jÁuh1jŸhj¶ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KChjwhžhubhÉ)”}”(hŒÁThere is also a gdb proxy for firewire which allows to use gdb to access data which can be referenced from symbols found by gdb in vmlinux: - http://halobates.de/firewire/fireproxy-0.33.tar.bz2”h]”(hŒŽThere is also a gdb proxy for firewire which allows to use gdb to access data which can be referenced from symbols found by gdb in vmlinux: - ”…””}”(hŒŽThere is also a gdb proxy for firewire which allows to use gdb to access data which can be referenced from symbols found by gdb in vmlinux: - ”hjÔhžhhŸNh Nubj )”}”(hŒ3http://halobates.de/firewire/fireproxy-0.33.tar.bz2”h]”hŒ3http://halobates.de/firewire/fireproxy-0.33.tar.bz2”…””}”(hhhjÝhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jßuh1jŸhjÔubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KFhjwhžhubhÉ)”}”(hŒ”The latest version of this gdb proxy (fireproxy-0.34) can communicate (not yet stable) with kgdb over an memory-based communication module (kgdbom).”h]”hŒ”The latest version of this gdb proxy (fireproxy-0.34) can communicate (not yet stable) with kgdb over an memory-based communication module (kgdbom).”…””}”(hjôhjòhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KJhjwhžhubeh}”(h]”Œtools”ah ]”h"]”Œtools”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K9ubh¢)”}”(hhh]”(h§)”}”(hŒGetting Started”h]”hŒGetting Started”…””}”(hj hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjhžhhŸh¶h KNubhÉ)”}”(hŒtThe OHCI-1394 specification regulates that the OHCI-1394 controller must disable all physical DMA on each bus reset.”h]”hŒtThe OHCI-1394 specification regulates that the OHCI-1394 controller must disable all physical DMA on each bus reset.”…””}”(hjhjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KPhjhžhubhÉ)”}”(hX3This means that if you want to debug an issue in a system state where interrupts are disabled and where no polling of the OHCI-1394 controller for bus resets takes place, you have to establish any FireWire cable connections and fully initialize all FireWire hardware __before__ the system enters such state.”h]”hX3This means that if you want to debug an issue in a system state where interrupts are disabled and where no polling of the OHCI-1394 controller for bus resets takes place, you have to establish any FireWire cable connections and fully initialize all FireWire hardware __before__ the system enters such state.”…””}”(hj)hj'hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KShjhžhubhÉ)”}”(hŒMStep-by-step instructions for using firescope with early OHCI initialization:”h]”hŒMStep-by-step instructions for using firescope with early OHCI initialization:”…””}”(hj7hj5hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KYhjhžhubhŒenumerated_list”“”)”}”(hhh]”(hŒ list_item”“”)”}”(hXQVerify that your hardware is supported: Load the firewire-ohci module and check your kernel logs. You should see a line similar to:: firewire_ohci 0000:15:00.1: added OHCI v1.0 device as card 2, 4 IR + 4 IT ... contexts, quirks 0x11 when loading the driver. If you have no supported controller, many PCI, CardBus and even some Express cards which are fully compliant to OHCI-1394 specification are available. If it requires no driver for Windows operating systems, it most likely is. Only specialized shops have cards which are not compliant, they are based on TI PCILynx chips and require drivers for Windows operating systems. The mentioned kernel log message contains the string "physUB" if the controller implements a writable Physical Upper Bound register. This is required for physical DMA above 4 GB (but not utilized by Linux yet). ”h]”(hÉ)”}”(hŒ'Verify that your hardware is supported:”h]”hŒ'Verify that your hardware is supported:”…””}”(hjPhjNhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K[hjJubhÉ)”}”(hŒ\Load the firewire-ohci module and check your kernel logs. You should see a line similar to::”h]”hŒ[Load the firewire-ohci module and check your kernel logs. You should see a line similar to:”…””}”(hŒ[Load the firewire-ohci module and check your kernel logs. You should see a line similar to:”hj\hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K]hjJubhŒ literal_block”“”)”}”(hŒcfirewire_ohci 0000:15:00.1: added OHCI v1.0 device as card 2, 4 IR + 4 IT ... contexts, quirks 0x11”h]”hŒcfirewire_ohci 0000:15:00.1: added OHCI v1.0 device as card 2, 4 IR + 4 IT ... contexts, quirks 0x11”…””}”(hhhjmubah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1jkhŸh¶h K`hjJubhÉ)”}”(hX‹when loading the driver. If you have no supported controller, many PCI, CardBus and even some Express cards which are fully compliant to OHCI-1394 specification are available. If it requires no driver for Windows operating systems, it most likely is. Only specialized shops have cards which are not compliant, they are based on TI PCILynx chips and require drivers for Windows operating systems.”h]”hX‹when loading the driver. If you have no supported controller, many PCI, CardBus and even some Express cards which are fully compliant to OHCI-1394 specification are available. If it requires no driver for Windows operating systems, it most likely is. Only specialized shops have cards which are not compliant, they are based on TI PCILynx chips and require drivers for Windows operating systems.”…””}”(hjhj}hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KchjJubhÉ)”}”(hŒÓThe mentioned kernel log message contains the string "physUB" if the controller implements a writable Physical Upper Bound register. This is required for physical DMA above 4 GB (but not utilized by Linux yet).”h]”hŒ×The mentioned kernel log message contains the string “physUB†if the controller implements a writable Physical Upper Bound register. This is required for physical DMA above 4 GB (but not utilized by Linux yet).”…””}”(hjhj‹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KjhjJubeh}”(h]”h ]”h"]”h$]”h&]”uh1jHhjEhžhhŸh¶h NubjI)”}”(hXÝEstablish a working FireWire cable connection: Any FireWire cable, as long at it provides electrically and mechanically stable connection and has matching connectors (there are small 4-pin and large 6-pin FireWire ports) will do. If an driver is running on both machines you should see a line like:: firewire_core 0000:15:00.1: created device fw1: GUID 00061b0020105917, S400 on both machines in the kernel log when the cable is plugged in and connects the two machines. ”h]”(hÉ)”}”(hŒ.Establish a working FireWire cable connection:”h]”hŒ.Establish a working FireWire cable connection:”…””}”(hj¥hj£hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KnhjŸubhÉ)”}”(hŒ¶Any FireWire cable, as long at it provides electrically and mechanically stable connection and has matching connectors (there are small 4-pin and large 6-pin FireWire ports) will do.”h]”hŒ¶Any FireWire cable, as long at it provides electrically and mechanically stable connection and has matching connectors (there are small 4-pin and large 6-pin FireWire ports) will do.”…””}”(hj³hj±hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KphjŸubhÉ)”}”(hŒEIf an driver is running on both machines you should see a line like::”h]”hŒDIf an driver is running on both machines you should see a line like:”…””}”(hŒDIf an driver is running on both machines you should see a line like:”hj¿hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KthjŸubjl)”}”(hŒKfirewire_core 0000:15:00.1: created device fw1: GUID 00061b0020105917, S400”h]”hŒKfirewire_core 0000:15:00.1: created device fw1: GUID 00061b0020105917, S400”…””}”(hhhjÎubah}”(h]”h ]”h"]”h$]”h&]”j{j|uh1jkhŸh¶h KvhjŸubhÉ)”}”(hŒ^on both machines in the kernel log when the cable is plugged in and connects the two machines.”h]”hŒ^on both machines in the kernel log when the cable is plugged in and connects the two machines.”…””}”(hjÞhjÜhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KxhjŸubeh}”(h]”h ]”h"]”h$]”h&]”uh1jHhjEhžhhŸh¶h NubjI)”}”(hXRTest physical DMA using firescope: On the debug host, make sure that /dev/fw* is accessible, then start firescope:: $ firescope Port 0 (/dev/fw1) opened, 2 nodes detected FireScope --------- Target : Gen : 1 [Ctrl-T] choose target [Ctrl-H] this menu [Ctrl-Q] quit ------> Press Ctrl-T now, the output should be similar to: 2 nodes available, local node is: 0 0: ffc0, uuid: 00000000 00000000 [LOCAL] 1: ffc1, uuid: 00279000 ba4bb801 Besides the [LOCAL] node, it must show another node without error message. ”h]”(hÉ)”}”(hŒ"Test physical DMA using firescope:”h]”hŒ"Test physical DMA using firescope:”…””}”(hjöhjôhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K{hjðubhÉ)”}”(hŒPOn the debug host, make sure that /dev/fw* is accessible, then start firescope::”h]”hŒOOn the debug host, make sure that /dev/fw* is accessible, then start firescope:”…””}”(hŒOOn the debug host, make sure that /dev/fw* is accessible, then start firescope:”hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K}hjðubjl)”}”(hX‚ $ firescope Port 0 (/dev/fw1) opened, 2 nodes detected FireScope --------- Target : Gen : 1 [Ctrl-T] choose target [Ctrl-H] this menu [Ctrl-Q] quit ------> Press Ctrl-T now, the output should be similar to: 2 nodes available, local node is: 0 0: ffc0, uuid: 00000000 00000000 [LOCAL] 1: ffc1, uuid: 00279000 ba4bb801”h]”hX‚ $ firescope Port 0 (/dev/fw1) opened, 2 nodes detected FireScope --------- Target : Gen : 1 [Ctrl-T] choose target [Ctrl-H] this menu [Ctrl-Q] quit ------> Press Ctrl-T now, the output should be similar to: 2 nodes available, local node is: 0 0: ffc0, uuid: 00000000 00000000 [LOCAL] 1: ffc1, uuid: 00279000 ba4bb801”…””}”(hhhjubah}”(h]”h ]”h"]”h$]”h&]”j{j|uh1jkhŸh¶h K€hjðubhÉ)”}”(hŒJBesides the [LOCAL] node, it must show another node without error message.”h]”hŒJBesides the [LOCAL] node, it must show another node without error message.”…””}”(hj!hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K‘hjðubeh}”(h]”h ]”h"]”h$]”h&]”uh1jHhjEhžhhŸh¶h NubjI)”}”(hX&Prepare for debugging with early OHCI-1394 initialization: 4.1) Kernel compilation and installation on debug target Compile the kernel to be debugged with CONFIG_PROVIDE_OHCI1394_DMA_INIT (Kernel hacking: Provide code for enabling DMA over FireWire early on boot) enabled and install it on the machine to be debugged (debug target). 4.2) Transfer the System.map of the debugged kernel to the debug host Copy the System.map of the kernel be debugged to the debug host (the host which is connected to the debugged machine over the FireWire cable). ”h]”(hÉ)”}”(hŒ:Prepare for debugging with early OHCI-1394 initialization:”h]”hŒ:Prepare for debugging with early OHCI-1394 initialization:”…””}”(hj9hj7hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K“hj3ubhÉ)”}”(hŒ84.1) Kernel compilation and installation on debug target”h]”hŒ84.1) Kernel compilation and installation on debug target”…””}”(hjGhjEhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K•hj3ubhÉ)”}”(hŒØCompile the kernel to be debugged with CONFIG_PROVIDE_OHCI1394_DMA_INIT (Kernel hacking: Provide code for enabling DMA over FireWire early on boot) enabled and install it on the machine to be debugged (debug target).”h]”hŒØCompile the kernel to be debugged with CONFIG_PROVIDE_OHCI1394_DMA_INIT (Kernel hacking: Provide code for enabling DMA over FireWire early on boot) enabled and install it on the machine to be debugged (debug target).”…””}”(hjUhjShžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K—hj3ubhÉ)”}”(hŒE4.2) Transfer the System.map of the debugged kernel to the debug host”h]”hŒE4.2) Transfer the System.map of the debugged kernel to the debug host”…””}”(hjchjahžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K›hj3ubhÉ)”}”(hŒŽCopy the System.map of the kernel be debugged to the debug host (the host which is connected to the debugged machine over the FireWire cable).”h]”hŒŽCopy the System.map of the kernel be debugged to the debug host (the host which is connected to the debugged machine over the FireWire cable).”…””}”(hjqhjohžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khj3ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jHhjEhžhhŸh¶h NubjI)”}”(hX,Retrieving the printk buffer contents: With the FireWire cable connected, the OHCI-1394 driver on the debugging host loaded, reboot the debugged machine, booting the kernel which has CONFIG_PROVIDE_OHCI1394_DMA_INIT enabled, with the option ohci1394_dma=early. Then, on the debugging host, run firescope, for example by using -A:: firescope -A System.map-of-debug-target-kernel Note: -A automatically attaches to the first non-local node. It only works reliably if only connected two machines are connected using FireWire. After having attached to the debug target, press Ctrl-D to view the complete printk buffer or Ctrl-U to enter auto update mode and get an updated live view of recent kernel messages logged on the debug target. Call "firescope -h" to get more information on firescope's options. ”h]”(hÉ)”}”(hŒ&Retrieving the printk buffer contents:”h]”hŒ&Retrieving the printk buffer contents:”…””}”(hj‰hj‡hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K hjƒubhÉ)”}”(hŒÝWith the FireWire cable connected, the OHCI-1394 driver on the debugging host loaded, reboot the debugged machine, booting the kernel which has CONFIG_PROVIDE_OHCI1394_DMA_INIT enabled, with the option ohci1394_dma=early.”h]”hŒÝWith the FireWire cable connected, the OHCI-1394 driver on the debugging host loaded, reboot the debugged machine, booting the kernel which has CONFIG_PROVIDE_OHCI1394_DMA_INIT enabled, with the option ohci1394_dma=early.”…””}”(hj—hj•hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K¢hjƒubhÉ)”}”(hŒEThen, on the debugging host, run firescope, for example by using -A::”h]”hŒDThen, on the debugging host, run firescope, for example by using -A:”…””}”(hŒDThen, on the debugging host, run firescope, for example by using -A:”hj£hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K¦hjƒubjl)”}”(hŒ.firescope -A System.map-of-debug-target-kernel”h]”hŒ.firescope -A System.map-of-debug-target-kernel”…””}”(hhhj²ubah}”(h]”h ]”h"]”h$]”h&]”j{j|uh1jkhŸh¶h K¨hjƒubhÉ)”}”(hŒNote: -A automatically attaches to the first non-local node. It only works reliably if only connected two machines are connected using FireWire.”h]”hŒNote: -A automatically attaches to the first non-local node. It only works reliably if only connected two machines are connected using FireWire.”…””}”(hjÂhjÀhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KªhjƒubhÉ)”}”(hŒÑAfter having attached to the debug target, press Ctrl-D to view the complete printk buffer or Ctrl-U to enter auto update mode and get an updated live view of recent kernel messages logged on the debug target.”h]”hŒÑAfter having attached to the debug target, press Ctrl-D to view the complete printk buffer or Ctrl-U to enter auto update mode and get an updated live view of recent kernel messages logged on the debug target.”…””}”(hjÐhjÎhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K­hjƒubhÉ)”}”(hŒCCall "firescope -h" to get more information on firescope's options.”h]”hŒICall “firescope -h†to get more information on firescope’s options.”…””}”(hjÞhjÜhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K±hjƒubeh}”(h]”h ]”h"]”h$]”h&]”uh1jHhjEhžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”hŒsuffix”Œ)”uh1jChjhžhhŸh¶h K[ubeh}”(h]”Œgetting-started”ah ]”h"]”Œgetting started”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KNubh¢)”}”(hhh]”(h§)”}”(hŒNotes”h]”hŒNotes”…””}”(hjhjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjhžhhŸh¶h K´ubhÉ)”}”(hŒ?Documentation and specifications: http://halobates.de/firewire/”h]”(hŒ"Documentation and specifications: ”…””}”(hŒ"Documentation and specifications: ”hjhžhhŸNh Nubj )”}”(hŒhttp://halobates.de/firewire/”h]”hŒhttp://halobates.de/firewire/”…””}”(hhhjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”juh1jŸhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K¶hjhžhubhÉ)”}”(hŒtFireWire is a trademark of Apple Inc. - for more information please refer to: https://en.wikipedia.org/wiki/FireWire”h]”(hŒNFireWire is a trademark of Apple Inc. - for more information please refer to: ”…””}”(hŒNFireWire is a trademark of Apple Inc. - for more information please refer to: ”hj2hžhhŸNh Nubj )”}”(hŒ&https://en.wikipedia.org/wiki/FireWire”h]”hŒ&https://en.wikipedia.org/wiki/FireWire”…””}”(hhhj;hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j=uh1jŸhj2ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K¸hjhžhubeh}”(h]”Œnotes”ah ]”h"]”Œnotes”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K´ubeh}”(h]”ŒKusing-physical-dma-provided-by-ohci-1394-firewire-controllers-for-debugging”ah ]”h"]”ŒKusing physical dma provided by ohci-1394 firewire controllers for debugging”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jƒŒerror_encoding”ŒUTF-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œ embed_images”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j]jZj1j.jtjqjjjjýjUjRuŒ nametypes”}”(j]Nj1NjtNjNjNjUNuh}”(jZh£j.h·jqj4jjwjýjjRjuŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nhžhub.