Result for 197F9AAAD29DEF130ACB0E49D2E66E570E81F791

Query result

Key Value
FileName./usr/lib64/libv4l/ov518-decomp
FileSize28216
MD509E5D49560E997D8196D644DACF015C0
SHA-1197F9AAAD29DEF130ACB0E49D2E66E570E81F791
SHA-256D02889C65FAEABA9F9DC8D714AD3D361A427161A83AD7FBA05DB1687A0CFC705
SSDEEP768:EuhpzpHUmCiUZUCSk5SX+7YNyK4fy5h9zhYzHOEKzr:EUHUVi2gr0KGp0r
TLSHT1CFC2E7CE32040856E84F9330FD4B54F98B62BE96EE15D207B6CE765E71B3C9CB592908
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5F8DC5E8A6805582E437C9FFF85B7D624
PackageArchppc64
PackageDescriptionlibv4l is a collection of libraries which adds a thin abstraction layer on top of video4linux2 devices. The purpose of this (thin) layer is to make it easy for application writers to support a wide variety of devices without having to write separate code for different devices in the same class. libv4l consists of 3 different libraries: libv4lconvert, libv4l1 and libv4l2. libv4lconvert offers functions to convert from any (known) pixel-format to V4l2_PIX_FMT_BGR24 or V4l2_PIX_FMT_YUV420. libv4l1 offers the (deprecated) v4l1 API on top of v4l2 devices, independent of the drivers for those devices supporting v4l1 compatibility (which many v4l2 drivers do not). libv4l2 offers the v4l2 API on top of v4l2 devices, while adding for the application transparent libv4lconvert conversion where necessary.
PackageMaintainerKoji
PackageNamelibv4l
PackageRelease1.fc15
PackageVersion0.8.3
SHA-1D0A409A812E141506B07F6673741B7D6B039C93A
SHA-256F60CF470ACE1481329A42422E51A1A8C4CD769FE2D5E32224D6E548851F0340C