[Q] What's preventing solo6x10 driver from moving out of staging

[Q] What's preventing solo6x10 driver from moving out of staging

[Ezequiel Garcia]

Hi all,

solo6x10 TODO file says this:

TODO (staging => main):

        * Motion detection flags need to be moved to v4l2
        * Some private CIDs need to be moved to v4l2

But I could not find any v4l2 motion detection flag. I guess it's a
new kind of flag that needs to be added.

Also, what happened with the mainline effort? (Assuming there was one :-)

Regards,
Ezequiel.

Re: [Q] What's preventing solo6x10 driver from moving out of staging

[Hans Verkuil]

On 21/06/12 17:08, Ezequiel Garcia wrote:
> Hi all,
>
> solo6x10 TODO file says this:
>
> TODO (staging =>  main):
>
>          * Motion detection flags need to be moved to v4l2
>          * Some private CIDs need to be moved to v4l2
>
> But I could not find any v4l2 motion detection flag. I guess it's a
> new kind of flag that needs to be added.

I don't know about the motion detection part, but I do know that any ioctls
and/or controls relating to video compression need to be reviewed in light of
the support for H264 etc. that was added some time ago.

I actually have a device, but I haven't had time to play with it and clean it
up.

> Also, what happened with the mainline effort? (Assuming there was one :-)

Well, when the new compression API was discussed I made sure that bluecherry
was CC-ed, but no action was taken from their side.

In other words, it seems unmaintained at the moment. Which is a shame, since
the code is actually fairly clean.

I've just scanned through the code and it looks like it wouldn't take too much
work to get it out of staging.

Regards,

	Hans

Re: [Q] What's preventing solo6x10 driver from moving out of staging

[Ezequiel Garcia]

Hi Hans,

Dropped Greg from Cc since it's not relevant (and that suse.de address
is broken).

On Thu, Jun 21, 2012 at 5:09 PM, Hans Verkuil <hverkuil@xs4all.nl> wrote:
> On 21/06/12 17:08, Ezequiel Garcia wrote:
>>
>> Hi all,
>>
>> solo6x10 TODO file says this:
>>
>> TODO (staging =>  main):
>>
>>         * Motion detection flags need to be moved to v4l2
>>         * Some private CIDs need to be moved to v4l2
>>
>> But I could not find any v4l2 motion detection flag. I guess it's a
>> new kind of flag that needs to be added.
>
>
> I don't know about the motion detection part, but I do know that any ioctls
> and/or controls relating to video compression need to be reviewed in light
> of
> the support for H264 etc. that was added some time ago.
>
> I actually have a device, but I haven't had time to play with it and clean
> it
> up.
>
>
>> Also, what happened with the mainline effort? (Assuming there was one :-)
>
>
> Well, when the new compression API was discussed I made sure that bluecherry
> was CC-ed, but no action was taken from their side.

Do you mean this api?

http://linuxtv.org/downloads/v4l-dvb-apis/extended-controls.html#mpeg-controls

>
> In other words, it seems unmaintained at the moment. Which is a shame, since
> the code is actually fairly clean.
>
> I've just scanned through the code and it looks like it wouldn't take too
> much
> work to get it out of staging.

Yes, does was my impression.

Regards,
Ezequiel.

Re: [Q] What's preventing solo6x10 driver from moving out of staging

[Hans Verkuil]

On 21/06/12 23:18, Ezequiel Garcia wrote:
>>> Also, what happened with the mainline effort? (Assuming there was one :-)
>>
>>
>> Well, when the new compression API was discussed I made sure that bluecherry
>> was CC-ed, but no action was taken from their side.
>
> Do you mean this api?
>
> http://linuxtv.org/downloads/v4l-dvb-apis/extended-controls.html#mpeg-controls

Yes.

	Hans