public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Pawel Osciak <pawel@osciak.com>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [GIT PATCHES FOR 2.6.38] Videbuf2 framework, NOON010PC30 sensor driver and s5p-fimc updates
Date: Tue, 11 Jan 2011 17:06:27 -0200	[thread overview]
Message-ID: <4D2CAA33.9020508@redhat.com> (raw)
In-Reply-To: <AANLkTimovx-bhpV-1bRn=KvvH4ZtvAsSmnJB5_bjn6xX@mail.gmail.com>

Em 11-01-2011 14:42, Pawel Osciak escreveu:
> Hi Mauro,
> 
> On Tue, Jan 11, 2011 at 10:23, Mauro Carvalho Chehab <mchehab@redhat.com> wrote:
>>> Pawel Osciak (8):
>>>       v4l: Add multi-planar API definitions to the V4L2 API
>>>       v4l: Add multi-planar ioctl handling code
>>
>>>       v4l: Add compat functions for the multi-planar API
>>>       v4l: fix copy sizes in compat32 for ext controls
>>
>> Are you sure that we need to add compat32 stuff for the multi-planar definitions?
>> Had you test if the compat32 code is actually working? Except if you use things
>> that have different sizes on 32 and 64 bit architectures, there's no need to add
>> anything for compat.
>>
> 
> v4l2_buffer and v4l2_plane contain pointers to buffers and/or arrays
> of planes. In fact buffer conversion was already there, I only added
> the new planes field. I believe those additions to the compat code are
> needed...

Ok.
> 
>> Anyway, I'll be merging the two compat functions into just one patch, as it will
>> help to track any regressions there, if ever needed. They are at my temporary
>> branch, but, if they are not needed, I'll drop when merging upstream.
>>
>>>       v4l: v4l2-ioctl: add buffer type conversion for multi-planar-aware ioctls
>>
>> NACK.
>>
>> We shouldn't be doing those videobuf memcpy operations inside the kernel.
>> If you want such feature, please implement it on libv4l.
>>
> 
> I can see your point. We don't really use it. It was to prevent
> applications from using two versions of API and thus being
> overcomplicated. It allowed using old drivers with the new API. If you
> think it is a bad idea, the patch can just be dropped without
> affecting anything else. I will fix the documentation if you decide to
> do so.

Yeah, I prefer to not have such conversions in Kernel. We've made already a lot of 
efforts to remove V4L1 compat conversion from kernel. It is interesting to add
it to libv4l, together with other conversions that are already done there.


Cheers,
Mauro

  reply	other threads:[~2011-01-11 17:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03 16:48 [GIT PATCHES FOR 2.6.38] Videbuf2 framework, NOON010PC30 sensor driver and s5p-fimc updates Sylwester Nawrocki
2011-01-11 18:23 ` Mauro Carvalho Chehab
2011-01-11 16:42   ` Pawel Osciak
2011-01-11 19:06     ` Mauro Carvalho Chehab [this message]
2011-01-11 20:19 ` Mauro Carvalho Chehab
2011-01-12 10:25   ` Marek Szyprowski
2011-01-12 18:49     ` Mauro Carvalho Chehab
2011-01-13  3:05       ` Pawel Osciak
2011-01-13 12:18         ` Mauro Carvalho Chehab
2011-01-12 20:23     ` Mauro Carvalho Chehab
2011-01-13  8:46       ` Andrzej Pietrasiewicz
2011-01-13 12:13         ` Andrzej Pietrasiewicz
2011-01-13 13:04           ` Mauro Carvalho Chehab
2011-01-13 12:58         ` Mauro Carvalho Chehab
2011-01-16 15:11           ` Mauro Carvalho Chehab
2011-01-11 21:31 ` Mauro Carvalho Chehab
2011-01-11 21:57 ` Mauro Carvalho Chehab
2011-01-12  2:47   ` Pawel Osciak
2011-01-12 16:19   ` Sylwester Nawrocki
2011-01-11 22:08 ` Mauro Carvalho Chehab

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=4D2CAA33.9020508@redhat.com \
    --to=mchehab@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=pawel@osciak.com \
    --cc=s.nawrocki@samsung.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