Visible to Intel only — GUID: mbe1642675386706
Ixiasoft
2.2.1. TDATA Pixel Packing
2.2.2. RGB Pixel Packing
2.2.3. YCbCr 444 Pixel Packing
2.2.4. YCbCr 422 Pixel Packing
2.2.5. YCbCr 420 Pixel Packing
2.2.6. Four-Channel Video Pixel Packing
2.2.7. Packing with Multiple Pixels in Parallel
2.2.8. Multiple Pixels in Parallel and Empty Pixels
2.2.9. YCbCr 422 Video with Multiple Pixels in Parallel
2.2.10. Packing RGB444 onto an RGB888 Interface
2.2.11. Packing with Less than 8 bits per Symbol Natively
2.2.12. Interlaced Fields
Visible to Intel only — GUID: mbe1642675386706
Ixiasoft
2.2.8. Multiple Pixels in Parallel and Empty Pixels
The Intel FPGA video streaming protocol does not use the AXI-S TKEEP or TSTRB signals, so all bytes within a packet are valid. Where video lines are not an integer multiple of the numbers of pixels in parallel, and empty pixels exist, the final beat of video packets is padded with unused data.
Figure 31. End-of-field pixel packing 4 pixels in parallel, 30 bit YCbCr, empty last pixel. The figure shows an example 4 pixels in parallel system where a line of 1920x1080p HD video has had the final pixel cropped and is now 1919 pixels wide. The final beat of the packet (beat n) is padded with unused data.
Padding because of empty pixels always occurs in the last beat of the packet. The first beat of the packet is always full of pixels, apart from the case of very short lines where the first beat is also the last beat. In the full variant of the protocol, the expected width of each video line is transmitted via image information control packets and so a receiving IP disregards the top bits of the final beat of the packet.