linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: mchehab@osg.samsung.com, linux-media@vger.kernel.org,
	laurent.pinchart@ideasonboard.com, hans.verkuil@cisco.com,
	ulrich.hecht@gmail.com, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCHv2] [media] rcar-vin: add Renesas R-Car VIN driver
Date: Fri, 11 Mar 2016 21:55:23 +0100	[thread overview]
Message-ID: <20160311205523.GG1111@bigcity.dyn.berto.se> (raw)
In-Reply-To: <56E2A90E.6080806@xs4all.nl>

On 2016-03-11 12:16:30 +0100, Hans Verkuil wrote:
> On 03/11/2016 12:03 PM, Niklas Söderlund wrote:
> > Hi Hans,
> > 
> > On 2016-03-11 09:26:48 +0100, Hans Verkuil wrote:
> >> Hi Niklas,
> >>
> >> On 02/29/2016 10:52 AM, Hans Verkuil wrote:
> >>> Hi Niklas,
> >>>
> >>> Thanks for your patch! Much appreciated.
> >>>
> >>> I have more comments for the v2, but nothing really big :-)
> >>>
> >>
> >> Just checking, you are working on a v3, right? I'd really like to get this in
> >> for kernel 4.7.
> > 
> > Yes I had to switch focus for a bit but now I'm back working on this 
> > again today.
> > 
> > I have some trouble getting NV16 to work. I can't get it to work using 
> > soc_camera driver either, or more accurate I get the same output broken 
> > rendering in qv4l2. What would you say is better drop NV16 support form 
> > the driver or keep it as is since it is compatible with the soc_camera 
> > drivers implementation? I would like to keep it in the driver for now 
> > since it at least works as good as in soc_camera.
> 
> I would have the NV16 support as a separate patch so we can decide on this
> later.
> 
> I don't really like having to support a broken format.
> 
> Do you know in what way the format is broken?

Turns out it was my fault all along for assuming qv4l2 could render NV16 
out-of-the-box. If one decodes the format correctly it works fine both 
with this driver and the one in soc_camera.

-- 
Regards,
Niklas Söderlund

  reply	other threads:[~2016-03-11 20:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  2:58 [PATCHv2] [media] rcar-vin: add Renesas R-Car VIN driver Niklas Söderlund
2016-02-27 11:32 ` Hans Verkuil
2016-02-27 17:21   ` Niklas Söderlund
2016-02-27 17:24     ` Hans Verkuil
2016-02-29  9:52 ` Hans Verkuil
2016-03-11  8:26   ` Hans Verkuil
2016-03-11 11:03     ` Niklas Söderlund
2016-03-11 11:16       ` Hans Verkuil
2016-03-11 20:55         ` Niklas Söderlund [this message]
2016-03-11 21:04           ` Hans Verkuil
2016-03-11 22:59             ` Niklas Söderlund
2016-04-02 18:01   ` Niklas Söderlund

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=20160311205523.GG1111@bigcity.dyn.berto.se \
    --to=niklas.soderlund@ragnatech.se \
    --cc=hans.verkuil@cisco.com \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=ulrich.hecht@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;
as well as URLs for NNTP newsgroup(s).