isodump(5)
πΎ isodump(5) β the manual page, but make it cute β¨
okay so bestie, welcome to isodump(5), a Linux IEEE 1394 situation π β specifically, the format of the IEEE 1394 isochronous packets dump file. Yes, that's a whole vibe. Let's get into it π
πΈ NAME πΈ
isodump</purg> β the format of the IEEE 1394 isochronous packets dump file π¦
β¨ DESCRIPTION β¨
So the isodump format is literally just a place where a whole series of IEEE 1394 isochronous stream packets get stored β possibly from multiple channels at once, no cap β and it keeps their headers too, because of course it does, the headers are the moment π
Its main character energy comes from being:
- the output format of
dumpiso(1)π«Ά - the input format of
sendiso(1)β¨
π The header (yes, it has a header, she's structured) π
The 32 byte header starts at offset 0 with the string "1394 isodump v1" followed by a zero byte. Iconic. Very signature-move of it π
Then the next 8 bytes form a 64 bit big endian integer, which is a bit mask of the channels that were dumped. A set bit at position (1 << x) signifies that channel x was being listened on πβ¨
The following 8 bytes are set to zero. Periodt. Just zero. Nothing to see there π
π¦ The packets π¦
The iso packets follow the header and get appended to the data stream in the order they were received. Slay, chronological queen β
Each packet consists of:
- the header quadlet as originally received
- the data quadlets following directly after it
The CRC quadlets after header and data do not appear π (they said not today) and everything is in big endian, as seen on the bus. Fr fr. π
π Finding packet boundaries π
There is no further framing of the packets in the format β so don't go looking for a cute little separator, it's not there. Packet boundaries can be found by looking at the data size field in the header quadlet of each packet π
And that data size field? It appears in the most significant 16 bits of the header quadlet, it contains the size in bytes (and btw the actual packet is padded to a multiple of four bytes), and it does not include the header packet. Write that down bestie, iykyk π
π COMPATIBILITY π
This format was introduced with the iso send and dump tools distributed with libraw1394. And... no one else uses it so far. π It's giving niche. It's giving exclusive. It's giving only-us-core π
π SEE ALSO π
π AUTHOR π
Andreas Bombe <aeb@debian.org> β thank you for your service, legend π«‘π
and that's the whole page bestie!! this manual came to you from libraw1394 2.1.2, and it's the isodump v1 era of isodump(5) β so go dump some iso packets and be the main character of your own bus π¦β¨π
π¦ where this page comes from
- alpine 3.24: libraw1394-doc 2.1.2-r5 Β· LGPL-2.1-or-later
- arch rolling: libraw1394 2.1.2-4 Β· LGPL-2.1-only
- debian bookworm: libraw1394-tools 2.1.2-2
- debian trixie: libraw1394-tools 2.1.2-2+b2
- epel 10: libraw1394 2.1.2-21.el10_0 Β· LGPLv2+
- epel 9: libraw1394 2.1.2-14.el9 Β· LGPLv2+
- fedora 43: libraw1394 2.1.2-24.fc43 Β· LicenseRef-Callaway-LGPLv2+
- fedora 43: libraw1394 2.1.2-24.fc43 Β· LicenseRef-Callaway-LGPLv2+
- fedora 44: libraw1394 2.1.2-25.fc44 Β· LicenseRef-Callaway-LGPLv2+
- fedora 44: libraw1394 2.1.2-25.fc44 Β· LicenseRef-Callaway-LGPLv2+
- nixos 26.05: libraw1394 2.1.2
- nixpkgs unstable: libraw1394 2.1.2
- ubuntu jammy: libraw1394-tools 2.1.2-2build2
- ubuntu noble: libraw1394-tools 2.1.2-2build3
- ubuntu questing: libraw1394-tools 2.1.2-2build3
- ubuntu resolute: libraw1394-tools 2.1.2-2build4
- ubuntu stonking: libraw1394-tools 2.1.2-2.1 Β· LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms