Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753487AbbGNPmy (ORCPT ); Tue, 14 Jul 2015 11:42:54 -0400 Received: from mail-yk0-f180.google.com ([209.85.160.180]:33404 "EHLO mail-yk0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752743AbbGNPmx (ORCPT ); Tue, 14 Jul 2015 11:42:53 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 14 Jul 2015 18:42:52 +0300 Message-ID: Subject: Re: tw5864 driver development, help needed From: Andrey Utkin To: Linux Media , "kernel-mentors@selenic.com" , "linux-kernel@vger.kernel.org" , Steven Toth , Ezequiel Garcia Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1429 Lines: 31 An update with a request for help. Asking for help with h264 headers generation. Both copying headers from similar videos and porting headers generation code from reference driver don't work for me (ref driver is weird and very complicated, so porting involved importing of lots of code, but still in my case the generated header differs from the one produced by reference driver, and resulting files are not decodable). Wireshark seems not able to dissect raw h264 files, so that I could compare headers bitfield-wise. I have dumped 64 first encoded frames as they appear from hardware, so that you could look at it. This is archive: http://lizard.bluecherry.net/~autkin/vlc.tar.gz and this is contents list of archive http://lizard.bluecherry.net/~autkin/vlc.contents Only one camera is attached to this multi-channel video grabber and encoder, and i don't know which chip has it (4, 5, 6 or 7). The produced frames should have the same settings as this file: http://lizard.bluecherry.net/~autkin/test_main.h264 This is PAL D1, 720x576. Thanks in advance for any help. At last, the ability to look at visualization of those h264 streams would be great. -- Bluecherry developer. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/