public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Thomas van Kleef <thomas@vitsch.nl>
Cc: Giulio Benetti <giulio.benetti@micronovasrl.com>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Andreas Baierl <list@imkreisrum.de>,
	linux-sunxi <linux-sunxi@googlegroups.com>,
	linux@armlinux.org.uk, wens@csie.org,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [linux-sunxi] Cedrus driver
Date: Tue, 28 Nov 2017 13:26:48 +0100	[thread overview]
Message-ID: <20171128122648.akxe7ro2mxmliedw@flea.home> (raw)
In-Reply-To: <5d1cad5b-7d36-71fd-2e23-3bfe05f6e56f@vitsch.nl>

[-- Attachment #1: Type: text/plain, Size: 2075 bytes --]

On Tue, Nov 28, 2017 at 12:20:59PM +0100, Thomas van Kleef wrote:
> > So, I have been rebasing to 4.14.0 and have the cedrus driver working.
> I have pulled linux-mainline 4.14.0. Then pulled the requests2 branch from Hans
> Verkuil's media_tree. I have a patch available of the merge between these 2
> branches.
> After this I pulled the sunxi-cedrus repository from Florent Revests github. I
> believe this one is the same as the ones you are cloning right now.
> I have merged this and have a patch available for this as well.
> 
> So to summarize:
>  o pulled linux 4.14 from:
>     https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>  o pulled requests2 from:
>     https://git.linuxtv.org/hverkuil/media_tree.git?h=requests2
>     will be replaced with the work, when it is done, in:
>      https://git.linuxtv.org/hverkuil/media_tree.git?h=ctrl-req-v2
>  o pulled linux-sunxi-cedrus from:
>     https://github.com/FlorentRevest/linux-sunxi-cedrus
> 
>  o merged and made patch between linux4.14 and requests2
>  o merged and made patch with linux-sunxi-cedrus
>  o Verified that the video-engine is decofing mpeg-2 on the Allwinner A20.
> 
> So maybe if someone is interested in this, I could place the patches somewhere?
> Just let me know.

Please create a pull request on the github repo. The point we set it
up was to share code. Forking repos and so on is kind of pointless.

> It would be nice to be able to play a file, so I would have to prepare our
> custom player and make a patch between the current sunxi-cedrus-drv-video and
> the one on https://github.com/FlorentRevest/sunxi-cedrus-drv-video.
> So I will start with this if there is any interest.
> 
> Should I be working in sunxi-next I wonder?

I'd rather stick on 4.14. sunxi-next wouldn't bring any benefit, and
we want to provide something that works first, and always merging next
will always distract us from the actual code.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-11-28 12:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1510059543-7064-1-git-send-email-giulio.benetti@micronovasrl.com>
     [not found] ` <1b12fa21-bfe6-9ba7-ae1d-8131ac6f4668@micronovasrl.com>
     [not found]   ` <6fcdc0d9-d0f8-785a-bb00-b1b41c684e59@imkreisrum.de>
     [not found]     ` <693e8786-af83-9d77-0fd4-50fa1f6a135f@micronovasrl.com>
2017-11-16 11:02       ` [linux-sunxi] Cedrus driver Maxime Ripard
2017-11-16 12:30         ` Giulio Benetti
2017-11-16 12:53           ` Maxime Ripard
2017-11-16 12:57             ` Giulio Benetti
2017-11-16 13:12               ` Hans Verkuil
2017-11-16 13:17                 ` Giulio Benetti
2017-11-16 13:39                   ` Maxime Ripard
2017-11-16 13:42                     ` Giulio Benetti
2017-11-28  0:03                       ` Giulio Benetti
2017-11-28  8:35                         ` Maxime Ripard
2017-11-28  9:50                           ` Giulio Benetti
2017-11-28 11:20                             ` Thomas van Kleef
2017-11-28 11:26                               ` Giulio Benetti
2017-11-28 11:29                                 ` Thomas van Kleef
2017-11-28 11:54                                   ` Giulio Benetti
2017-11-28 12:31                                     ` Thomas van Kleef
2017-11-28 12:52                                     ` Maxime Ripard
2017-11-28 13:03                                       ` Giulio Benetti
2017-11-28 13:07                                         ` Maxime Ripard
2017-11-28 13:12                                           ` Giulio Benetti
2017-11-28 15:17                                             ` Maxime Ripard
2017-11-28 15:19                                               ` Giulio Benetti
2017-11-28 12:26                               ` Maxime Ripard [this message]
2017-11-28 14:51                                 ` Thomas van Kleef
2017-11-28 15:35                                   ` Maxime Ripard
2017-11-29 15:36                                     ` Thomas van Kleef
2017-11-30 15:24                                       ` Maxime Ripard
2017-11-16 13:39                   ` Hans Verkuil
2017-11-16 19:59         ` Nicolas Dufresne
2017-11-17  8:01           ` Maxime Ripard

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=20171128122648.akxe7ro2mxmliedw@flea.home \
    --to=maxime.ripard@free-electrons.com \
    --cc=giulio.benetti@micronovasrl.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=linux@armlinux.org.uk \
    --cc=list@imkreisrum.de \
    --cc=thomas@vitsch.nl \
    --cc=wens@csie.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