linux-kernel - Re: [linux-sunxi] Cedrus driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 16 Nov 2017 13:30:52 +0100
From:   Giulio Benetti <giulio.benetti@...ronovasrl.com>
To:     Maxime Ripard <maxime.ripard@...e-electrons.com>
Cc:     Andreas Baierl <list@...reisrum.de>,
        linux-sunxi <linux-sunxi@...glegroups.com>,
        linux@...linux.org.uk, wens@...e.org, linux-kernel@...r.kernel.org,
        thomas@...sch.nl, linux-media@...r.kernel.org
Subject: Re: [linux-sunxi] Cedrus driver

Hi,

Il 16/11/2017 12:02, Maxime Ripard ha scritto:
> Hi,
> 
> I'm not sure why there's so many recipients (Russell, Rob or Mark have
> a limited interest in this I assume), and why you're also missing some
> key ones (like the v4l2 list).

added in cc linux-media mailing list that appears to be the right one 
for v4l2 and removed Russell, Rob and Mark

> 
> On Thu, Nov 16, 2017 at 11:37:30AM +0100, Giulio Benetti wrote:
>> Il 16/11/2017 11:31, Andreas Baierl ha scritto:
>>> Am 16.11.2017 um 11:13 schrieb Giulio Benetti:
>>>> Hello,
>>>>
>>> Hello,
>>>> I'm wondering why cedrus
>>>> https://github.com/FlorentRevest/linux-sunxi-cedrus has never been
>>>> merged with linux-sunxi sunxi-next.
>>>>
>>> Because it is not ready to be merged. It depends on the v4l2 request
>>> API, which was not merged and which is re-worked atm.
>>> Also, sunxi-cedrus itself is not in a finished state and is not as
>>> feature-complete to be merged. Anyway it might be something for
>>> staging... Has there been a [RFC] on the mailing list at all?
>>
>> Where can I find a list of TODOs to get it ready to be merged?
> 
> Assuming that the request API is in, we'd need to:
>    - Finish the MPEG4 support
>    - Work on more useful codecs (H264 comes to my mind)
>    - Implement the DRM planes support for the custom frame format
>    - Implement the DRM planes support for scaling
>    - Test it on more SoCs
> 
> Or something along those lines.

Lot of work to do

> 
>>>> I see it seems to be dead, no commit in 1 year.
>>>
>>> Yes, because the author did this during an internship, which ended ...
>>> Afaik nobody picked up his work yet.
> 
> That's not entirely true. Some work has been done by Thomas (in CC),
> especially on the display engine side, but last time we talked his
> work was not really upstreamable.
> 
> We will also resume that effort starting next march.

Is it possible a preview on a separate Reporitory to start working on now?
Expecially to start porting everything done by FlorentRevest to mainline,
admitted you've not already done.

> 
>>>> since we need video acceleration on A20 and A33.
>>>>
>>> ack.
>>
>> By the way, when you answer to google group, is it right that all CC I
>> inserted are not inserted too?
>> Because this causes mess with mailing lists (seems to me).
> 
> Yes, that's one of the many brain-damaged thing happening on that
> list...

Who can I ask to modify it?
Most of all, is it possible?

> 
> Maxime
> 


-- 
Giulio Benetti
R&D Manager &
Advanced Research

MICRONOVA SRL
Sede: Via A. Niedda 3 - 35010 Vigonza (PD)
Tel. 049/8931563 - Fax 049/8931346
Cod.Fiscale - P.IVA 02663420285
Capitale Sociale € 26.000 i.v.
Iscritta al Reg. Imprese di Padova N. 02663420285
Numero R.E.A. 258642