sendiso(1) Linux IEEE 1394 sendiso(1)NAME
sendiso - send IEEE 1394 isochronous packets from dump file
SYNOPSIS
sendiso [ options ] FILE
DESCRIPTION
sendiso takes the dump file FILE as generated by dumpiso(1), extracts the packets and sends them as they were received (in the same order,
with the same channel numbers) as fast as possible - timing of the original dump is not preserved.
This program does not allocate any isochronous resources but just starts sending. It should not be used in live environments where it
might interfere with properly set up isochronous transmissions, it is a debug and performance benchmarking tool.
OPTIONS -l, --loop=COUNT
Send dump file COUNT times. Defaults to 1.
-i, --infinite
Send dump file in an endless loop.
-s, --speed=SPEED
Send packets at speed SPEED, which can be given as 100, 200 and 400 (in Mbit/s) or abbreviated as 1, 2 and 4. Defaults to 100.
-p, --port=PORT
Choose port PORT for sending. A port is a 1394 card or chip and represents one connected bus, therefore this is only relevant when
you have multiple of these. Defaults to 0.
-h, --help
Show help text and exit.
BUGS
None known.
SEE ALSO dumpiso(1), isodump(5)AUTHOR
Andreas Bombe <aeb@debian.org>
libraw1394 2.0.9 sendiso(1)
Check Out this Related Man Page
isodump(5) Linux IEEE 1394 isodump(5)NAME
isodump - format of IEEE 1394 isochronous packets dump file
DESCRIPTION
The isodump format stores a series of IEEE 1394 isochronous stream packets (possibly from multiple channels), including their headers. Its
main use is as the output format of dumpiso(1) and the input format of sendiso(1).
The 32 byte header starts at offset 0 with the string "1394 isodump v1" followed by a zero byte. The next 8 bytes form a 64 bit big endian
integer, which represents 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.
The iso packets follow the header and are appended to the data stream in the order they were received. The packets consist of the header
quadlet as originally received and the data quadlets following directly. The CRC quadlets after header and data do not appear and every-
thing is in big endian, as seen on the bus.
There is no further framing of the packets in the format, packet boundaries can be found by looking at the data size field in the header
quadlet of each packet. The data size field appears in the most significant 16 bits of the header quadlet, contain the size in bytes (the
actual packet is padded to a multiple of four bytes) and do not include the header packet.
COMPATIBILITY
This format was introduced with the iso send and dump tools distributed with libraw1394. No one else uses it so far.
SEE ALSO sendiso(1), dumpiso(1)AUTHOR
Andreas Bombe <aeb@debian.org>
libraw1394 2.1.0 isodump v1 isodump(5)
Here it wont terminate unless i take the not of my statement
#!/bin/bash
grabXML
parseXML
TAIL=5
#"$(cat dailyCasLog | tail -n 1)"
COUNT=200
LINE=5
#"$(cat dailyCasLog | head -n $COUNT | tail -n 1)"
echo $TAIL
echo $LINE
while ($LINE!=)
do
#$LINE">>currentLine
folderMaker
... (0 Replies)
can anyone help me fix this? what command should I use to bring them back to "TRUE"?
Interface Speed Duplex Autoneg
--------- ----- ------ -------
ce0 100 Mbit/s FULL FALSE
ce5 100 Mbit/s FULL ... (3 Replies)
hi All, is there a way in linux to loop thru all variables sourced?
i have a set configs like
A=100
b=200
c=400
i can add the above lines to a file and source - so that $A will be 100 .. like wise
now when i do a cut -c 1-2 file.txt |sort | uniq -c on a file it returns me
A 100
B 50
c... (1 Reply)
First time post. I did a search so I didn’t see this specific issue. It seems to be a head scratcher for me.
I have an hourly job that on rare occasions, gets into an endless loop.
I’ve tried different scenarios but the current version does basically the following.
Find all the *.arc files and... (18 Replies)