From: Jean Delvare <khali@linux-fr.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Trent Piepho <xyzzy@speakeasy.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
urishk@yahoo.com, linux-media@vger.kernel.org
Subject: Re: Minimum kernel version supported by v4l-dvb
Date: Sat, 21 Feb 2009 14:56:15 +0100 [thread overview]
Message-ID: <20090221145615.324c4cb7@hyperion.delvare> (raw)
In-Reply-To: <200902211428.31814.hverkuil@xs4all.nl>
On Sat, 21 Feb 2009 14:28:31 +0100, Hans Verkuil wrote:
> On Saturday 21 February 2009 14:11:30 Jean Delvare wrote:
> > Well, that's basically what Hans has been doing with
> > v4l2-i2c-drv-legacy.h for months now, isn't it? This is the easy part
> > (even though even this wasn't exactly trivial...)
>
> Sorry, that's not quite true. v4l2-i2c-drv-legacy.h is for i2c modules that
> are either called new-style (by converted adapter drivers) or old-style (by
> not-yet converted adapter drivers). It does that by creating two i2c_driver
> instances, one for each variant. By contrast, i2c modules that include
> v4l2-i2c-drv.h can only be called by converted adapter drivers. This has
> nothing to do with detect(). I'm not using that at all.
>
> It was always the intention that the legacy.h header would disappear once
> all adapter drivers are converted. But v4l2-i2c-drv.h still has to support
> kernels < 2.6.22 were the new API doesn't exist at all. That's the sticking
> point that prevents us from dropping this header as well and go back to a
> normally written i2c module without all this nonsense.
>
> You may have meant the same thing, Jean, but I thought I should clarify it
> yet a bit more :-)
Thanks for the clarification. This just shows one thing: this
compatibility layer has become so complex that even I lose track of what
is what...
> (...)
> The point is not how easy or complicated these headers are, the point is
> that we shouldn't have them at all since they make no sense in the upstream
> kernel.
True...
--
Jean Delvare
next prev parent reply other threads:[~2009-02-21 13:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 8:55 Minimum kernel version supported by v4l-dvb Hans Verkuil
2009-02-18 10:10 ` Mauro Carvalho Chehab
2009-02-18 13:01 ` Jean Delvare
2009-02-20 3:57 ` hermann pitton
2009-02-20 6:53 ` Hans Verkuil
2009-02-20 9:49 ` Jean Delvare
2009-02-20 10:39 ` hermann pitton
2009-02-21 0:23 ` Mauro Carvalho Chehab
2009-02-21 1:12 ` Hans Verkuil
2009-02-21 2:13 ` Mauro Carvalho Chehab
2009-02-21 2:40 ` hermann pitton
2009-02-21 7:28 ` Hans Verkuil
2009-02-21 11:58 ` Mauro Carvalho Chehab
2009-02-21 12:45 ` Hans Verkuil
2009-02-21 12:56 ` Mauro Carvalho Chehab
2009-02-21 16:20 ` hermann pitton
2009-02-21 14:26 ` Jean Delvare
2009-02-21 12:06 ` Trent Piepho
2009-02-21 13:01 ` Mauro Carvalho Chehab
2009-02-21 13:11 ` Jean Delvare
2009-02-21 13:28 ` Hans Verkuil
2009-02-21 13:56 ` Jean Delvare [this message]
2009-02-21 13:58 ` Trent Piepho
2009-02-22 10:09 ` Jean Delvare
2009-02-21 1:30 ` kilgota
2009-02-21 2:18 ` Mauro Carvalho Chehab
2009-02-21 16:42 ` kilgota
2009-02-21 20:04 ` Jean Delvare
2009-02-21 9:32 ` Jean Delvare
-- strict thread matches above, loose matches on Subject: below --
2009-02-18 10:54 Hans Verkuil
2009-02-18 11:54 ` Mauro Carvalho Chehab
2009-02-17 13:23 Jean Delvare
2009-02-17 22:24 ` Laurent Pinchart
2009-02-17 23:06 ` Hans Verkuil
2009-02-21 11:50 ` Mauro Carvalho Chehab
2009-02-21 12:01 ` Hans Verkuil
2009-02-18 0:08 ` Mauro Carvalho Chehab
2009-02-18 0:18 ` Hans Verkuil
2009-02-18 2:08 ` Mauro Carvalho Chehab
2009-02-18 7:36 ` Hans Verkuil
2009-02-18 8:30 ` Uri Shkolnik
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=20090221145615.324c4cb7@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=urishk@yahoo.com \
--cc=xyzzy@speakeasy.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