From: Hans Verkuil <hverkuil@xs4all.nl>
To: Ran Shalit <ranshalit@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: vivid - add support for YUV420
Date: Mon, 11 Jan 2016 17:19:18 +0100 [thread overview]
Message-ID: <5693D606.1080801@xs4all.nl> (raw)
In-Reply-To: <CAJ2oMhLP5F=6JBi9S4SsuZ=L1GecuV694md7mgqfKR2uEGTr2A@mail.gmail.com>
On 01/11/2016 04:55 PM, Ran Shalit wrote:
> On Mon, Jan 11, 2016 at 1:58 PM, Ran Shalit <ranshalit@gmail.com> wrote:
>> On Mon, Jan 11, 2016 at 1:33 PM, Hans Verkuil <hverkuil@xs4all.nl> wrote:
>>> On 01/09/2016 10:58 AM, Ran Shalit wrote:
>>>> Hello,
>>>>
>>>> I've been doing some tests with capturing video from virtual driver (vivid).
>>>> I've tried to force it to YUV420, but it ignores that, becuase it does
>>>> not support this format.
>>>
>>> Yes, it does. What kernel are you using? Something old? Support for 4:2:0 was
>>> added to vivid in March 2015.
>>>
>>>> I would please like to ask if there is some way I can output YUV420
>>>> format with vivi.
>>>
>>> Upgrade your kernel :-)
>>
>> Right.
>> The kernel in Cent0S 7.2 (last release) is 3.10.0.
>> I am not sure I can update CentOS with kernel.org last release because
>> of probably many dependencies ( Is it possible ?)
>> Anyway, vivid , is life saving tool for newcomers. Absolutely.
>>
>> Regards,
>> Ran
>>
>
>
> Hi,
>
> Do you think it worth trying to upgrade vivid package only from 3.10
> (vivi) to 3.18 (vivid),
> or is it too complex to try and depend on many other files ?
>
> Thanks,
> Ran
>
A quick google gave me this:
http://linoxide.com/linux-how-to/upgrade-linux-kernel-stable-3-18-4-centos/
Most distros can be upgraded to newer kernels if you look around a bit.
Regards,
Hans
prev parent reply other threads:[~2016-01-11 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 9:58 vivid - add support for YUV420 Ran Shalit
2016-01-11 11:33 ` Hans Verkuil
2016-01-11 11:58 ` Ran Shalit
2016-01-11 15:55 ` Ran Shalit
2016-01-11 16:19 ` Hans Verkuil [this message]
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=5693D606.1080801@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=ranshalit@gmail.com \
/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