Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1235495 > unrolled thread

H264 headers generation for driver

Started byAndrey Utkin <andrey.utkin@corp.bluecherry.net>
First post2015-09-29 21:10 +0200
Last post2015-09-30 12:10 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel


Contents

  H264 headers generation for driver Andrey Utkin <andrey.utkin@corp.bluecherry.net> - 2015-09-29 21:10 +0200
    Re: H264 headers generation for driver khalasa@piap.pl (Krzysztof Hałasa) - 2015-09-30 12:10 +0200

#1235495 — H264 headers generation for driver

FromAndrey Utkin <andrey.utkin@corp.bluecherry.net>
Date2015-09-29 21:10 +0200
SubjectH264 headers generation for driver
Message-ID<qe8rM-6Xo-5@gated-at.bofh.it>
This is a new chapter of tw5864 video grabber & encoder driver
development drama.
Last state of code is here (tw5864 branch, drivers/staging/media/tw5864):
https://github.com/bluecherrydvr/linux/tree/tw5864/drivers/staging/media/tw5864

Currently I use a third-side LGPL library for H.264 headers generation
- SPS, PPS and slice headers (because device doesn't generate them).
It is included as a git submodule "h264bitstream". It is used from
tw5864-h264.c .
Of course we want our driver to get to upstream repository when it
matures enough, that's why we want to ask for advice regarding this.
I see that there is no similar case in upstream kernel repo - no
submodules and no libraries for H264 bitstreams.
Device datasheet
(http://lizard.bluecherry.net/~autkin/tw5864/tw5864b1-ds.pdf , page
47) shows that there's almost no variety of modes, so minimally an
implementation of bitstream writing functions ue() and se() will
suffice.
I guess that one acceptable way is to pre-generate all headers for all
needed cases and ship them inlined; for correctness checking purpose,
it is possible to ship also a script or additional source code file
which is able to generate same headers.
Please advise.

Thanks in advance for any kind reply.

-- 
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/

[toc] | [next] | [standalone]


#1236012

Fromkhalasa@piap.pl (Krzysztof Hałasa)
Date2015-09-30 12:10 +0200
Message-ID<qemuM-1NX-61@gated-at.bofh.it>
In reply to#1235495
Andrey Utkin <andrey.utkin@corp.bluecherry.net> writes:

[H.264 headers]
> I guess that one acceptable way is to pre-generate all headers for all
> needed cases and ship them inlined; for correctness checking purpose,
> it is possible to ship also a script or additional source code file
> which is able to generate same headers.

I think these are good ideas.
BTW the SOLO6110 at the moment also has pregenerated SPS/PPS headers
(whole NALs actually).
-- 
Krzysztof Halasa

Industrial Research Institute for Automation and Measurements PIAP
Al. Jerozolimskie 202, 02-486 Warsaw, Poland
--
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/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web