From: Greg KH <greg@kroah.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: linux-next: v4l-dvb tree build failure
Date: Wed, 12 Nov 2008 14:45:29 -0800 [thread overview]
Message-ID: <20081112224529.GC27479@kroah.com> (raw)
In-Reply-To: <20081111225430.6966b37b@pedra.chehab.org>
On Tue, Nov 11, 2008 at 10:54:30PM -0200, Mauro Carvalho Chehab wrote:
> 1) There were two ioctls that weren't supported by video_ioctl2(). This
> changeset provides the proper implementation:
>
> http://git.kernel.org/?p=linux/kernel/git/mchehab/linux-next.git;a=commit;h=b35e0c6035369de9f3273b6a3fbb1c67f830cf49
>
> You'll need this patch in order to compile go7007. It is currently at
> linux-next. It is safe to add this upstream, but this is not a bug fix
> patch. So, it seems a little late to add this there...
>
> Maybe we can just add an #if 0 for the two functions that implement those
> ioctls upstream.
Thanks, I've done this to this patch.
> 2) go7007 used to implement his own proprietary code to allow controlling mpeg
> encoding parameters. At the time go7007 driver were written, there weren't any
> other options, but, since kernel 2.6.18, 3 newer ioctls were added, in
> order to support ivtv driver. So, I can't see any reason to keep those proprietary userpspace API, when we
>
> Those ioctls allows a proper setup for encoding and decoding parameters for
> mpeg, mpeg2, mpeg4 (and are extensive to allow other formats).
>
> The conversion to use those ioctls would be more complex, and I was too lazy
> for doing this conversion right now ;)
>
> So, on this patch, I just commented the affected code with #if 0. Hopefully,
> someone with more time may implement VIDIOC_G_EXT_CTRLS, VIDIOC_S_EXT_CTRLS and
> VIDIOC_TRY_EXT_CTRLS.
>
> If nobody volunteer to do it, I may seek for sometime later to do it.
I think I already have this converted in my tree now from one of the
original authors.
thanks a lot for the patch, I appreciate it.
greg k-h
next prev parent reply other threads:[~2008-11-12 23:19 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 3:30 linux-next: v4l-dvb tree build failure Stephen Rothwell
2008-11-07 17:43 ` Harvey Harrison
2008-11-07 18:41 ` Greg KH
2008-11-07 23:02 ` Stephen Rothwell
2008-11-12 0:54 ` Mauro Carvalho Chehab
2008-11-12 22:45 ` Greg KH [this message]
2008-11-07 22:59 ` Stephen Rothwell
2008-11-07 23:06 ` Greg KH
2008-11-08 3:05 ` Sam Ravnborg
2008-11-08 4:38 ` Greg KH
2008-11-08 5:08 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-01-27 6:59 Stephen Rothwell
2010-01-27 23:24 ` Andy Walls
2010-01-28 1:54 ` Mauro Carvalho Chehab
2010-01-28 5:24 ` Stephen Rothwell
2009-04-07 0:58 Stephen Rothwell
2009-04-07 1:20 ` Mauro Carvalho Chehab
2009-04-07 4:47 ` Stephen Rothwell
2009-03-27 0:40 Stephen Rothwell
2009-03-27 11:28 ` Mauro Carvalho Chehab
2009-03-27 14:03 ` Stephen Rothwell
2009-03-05 0:35 Stephen Rothwell
2009-03-05 21:51 ` Mauro Carvalho Chehab
2009-03-06 0:05 ` Stephen Rothwell
2009-03-06 1:15 ` Mauro Carvalho Chehab
2009-03-02 0:05 Stephen Rothwell
2009-03-02 0:08 ` Michael Krufky
2009-03-02 0:30 ` Stephen Rothwell
2009-03-02 2:52 ` Mauro Carvalho Chehab
2008-12-08 2:07 Stephen Rothwell
2008-12-01 23:37 Stephen Rothwell
2008-12-02 10:03 ` Mauro Carvalho Chehab
2008-12-02 22:23 ` Stephen Rothwell
2008-12-03 22:48 ` Mauro Carvalho Chehab
2008-12-03 0:08 ` Stephen Rothwell
2008-12-03 22:49 ` Mauro Carvalho Chehab
2008-11-25 4:41 Stephen Rothwell
2008-10-29 2:20 Stephen Rothwell
2008-10-29 12:26 ` Andreas Oberritter
2008-11-03 1:52 ` Stephen Rothwell
2008-11-05 1:57 ` Stephen Rothwell
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=20081112224529.GC27479@kroah.com \
--to=greg@kroah.com \
--cc=harvey.harrison@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).