From: khalasa@piap.pl (Krzysztof Hałasa)
To: linux-media@vger.kernel.org
Subject: Re: Subjective maturity of tw6869, cx25821, bluecherry/softlogic drivers
Date: Fri, 03 Jul 2015 12:46:15 +0200 [thread overview]
Message-ID: <m3vbe1plhk.fsf@t19.piap.pl> (raw)
In-Reply-To: 1435871672466752997@telcodata.us
Nathaniel Bezanson <myself@telcodata.us> writes:
> I found the intersil/techwell TW6869 chip on a very affordable card,
> and there's a nice looking driver here:
> https://github.com/igorizyumin/tw6869/
It didn't work for me. Probably because it uses large coherent
allocations (which aren't possible on ARM, and shouldn't be used
on any hardware). Other problems (not sure if in this very driver, or
another of its clones): not using DMA SG, using CPU to copy frame data
in DQBUF (or somewhere), apparent support for nonexistent hardware
features (tuners?).
This reminds me to post my own driver for these cards, a bit smaller and
lacking some features (like scaling and cropping) but working and using
SG DMA.
> Only trouble is there only
> seems to be the one card using it
There are at least Sensoray (8-port, a bit improved chip) and Commell
(4-port, based on older TW6864) cards.
These chips aren't ideal - but they work.
For example, in DMA SG mode, they can't produce a single continuous
interlaced frame in memory - they can only make two separate fields.
A limitation of their DMA engine, since in non-SG mode they can make
(pseudo)-progressive frames.
Also, they can't do YUV420 - they only do things like YUV422 and
RGB565/555 (well they can do YUV420 with custom encoding in a mode with
reduced vertical resolution - with field dropping or in field mode,
where each field is a different picture encoded with YUV420).
I'm using SOLO6110-based cards, too. They work. There are apparently
certain problems, but I wasn't able to reproduce them. My use is limited
to 4-channel operation, though (the chip can do up to 5 full D1 H.264
streams, but there are 16-channel versions which can do 16 simultaneous
H.264s with a reduced resolution and/or with frame dropping - I suspect
the latter could be the problem).
SOLO6110 doesn't produce a valid interlaced H.264 stream (with field
encoding) - only a (pseudo) progressive stream (frame mode). This is
actually what TW686x lacks :-)
Also, TW686x are (mini) PCIe while SOLO6110 (and earlier SOLO6010 which
produces MPEG4 part 2 instead of H.264) are (mini) PCI.
TW686x don't have hardware H.264 encoder (though I'm told certain
TW586x do have).
--
Krzysztof Halasa
Industrial Research Institute for Automation and Measurements PIAP
Al. Jerozolimskie 202, 02-486 Warsaw, Poland
next prev parent reply other threads:[~2015-07-03 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 21:14 Subjective maturity of tw6869, cx25821, bluecherry/softlogic drivers Nathaniel Bezanson
2015-07-03 7:38 ` Hans Verkuil
2015-07-03 10:46 ` Krzysztof Hałasa [this message]
2015-07-05 16:54 ` Andrey Utkin
2015-07-06 6:16 ` Krzysztof Hałasa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3vbe1plhk.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox