I'm cross-posting this at V4L mailing list, since this subject is
better handled at V4L list.
The basic idea for shapshot is to provide a stable snapshot of V4L
from my point of view. It doesn't mean that it will works with every
kernel release.
If you guys are willing to
On Tue, Nov 08, 2005 at 07:06:17PM +0100, Hans Verkuil wrote:
Once the audio/video drivers are moved to v4l then they are promptly
removed from ivtv 0.5.0.
I just checked v4l and it only build for kernels = 2.6.12. Or do we
want to have that as a minimal kernel for ivtv, too?
I'd like to be
Axel Thimm wrote:
On Tue, Nov 08, 2005 at 07:06:17PM +0100, Hans Verkuil wrote:
Once the audio/video drivers are moved to v4l then they are promptly
removed from ivtv 0.5.0.
I just checked v4l and it only build for kernels = 2.6.12. Or do we
want to have that as a minimal kernel for
On Wed, Nov 09, 2005 at 01:32:18PM +0100, Hans Verkuil wrote:
On Tue, Nov 08, 2005 at 07:06:17PM +0100, Hans Verkuil wrote:
Once the audio/video drivers are moved to v4l then they are promptly
removed from ivtv 0.5.0.
I just checked v4l and it only build for kernels = 2.6.12. Or do we
On Wed, Nov 09, 2005 at 08:07:49AM -0500, Michael Krufky wrote:
Axel Thimm wrote:
On Tue, Nov 08, 2005 at 07:06:17PM +0100, Hans Verkuil wrote:
Once the audio/video drivers are moved to v4l then they are promptly
removed from ivtv 0.5.0.
I just checked v4l and it only build for
Axel Thimm wrote:
On Wed, Nov 09, 2005 at 08:07:49AM -0500, Michael Krufky wrote:
Axel Thimm wrote:
On Tue, Nov 08, 2005 at 07:06:17PM +0100, Hans Verkuil wrote:
Once the audio/video drivers are moved to v4l then they are promptly
removed from ivtv 0.5.0.
I just checked v4l and it
On Wed, Nov 09, 2005 at 08:43:01AM -0500, Michael Krufky wrote:
Axel Thimm wrote:
On Wed, Nov 09, 2005 at 08:07:49AM -0500, Michael Krufky wrote:
Axel Thimm wrote:
On Tue, Nov 08, 2005 at 07:06:17PM +0100, Hans Verkuil wrote:
Once the audio/video drivers are moved to v4l then they are
On Wed, Nov 09, 2005 at 08:20:07AM -0500, Axel Thimm wrote:
On Wed, Nov 09, 2005 at 01:32:18PM +0100, Hans Verkuil wrote:
v4l should build on anything from 2.4 onwards.
Maybe with the latest 2.4 kernel which got some v4l2 treatment, but
not 2.4.20-22, or does it?
I know that ivtv and
Axel Thimm wrote:
On Wed, Nov 09, 2005 at 08:43:01AM -0500, Michael Krufky wrote:
We are compatible with Vanilla 2.6.X kernels, through the use of #IF
KERNEL_VERSION and compat.h magic HOWEVER, some non-standard
kernels have backported newer features into older kernels, and our
tests
So surely what we need then is a statement that as of
0.6 (or whatever it's called when it is released) ivtv
is compatible with kernel 2.6.xx (15?) or requires
this release of v4l2.
This would of course mean that probably we would want
a kernel v4l2 release to happen before we can
release ivtv
That's correct. It won't be released until either 2.6.15 is released
and/or a stable v4l2 is released. The video4linux project makes regular
releases, so we pick one that works and recommend that one to build
against.
Remember: 0.4.x will remain for quite some time as the branch to use for
On Wed, Nov 09, 2005 at 10:39:25AM -0500, Michael Krufky wrote:
Axel Thimm wrote:
On Wed, Nov 09, 2005 at 08:43:01AM -0500, Michael Krufky wrote:
What *is* relevant to ivtv is the dependency to the state of v4l
cvs. The current model w/o keeping copies of migrated drivers in ivtv
means that
On Mon, Nov 07, 2005 at 08:13:51AM +0100, Hans Verkuil wrote:
A lot of work is going into 0.5.0 in order to move the saa7115, saa7127
and cx25840 modules to the v4l repository and then to the 2.6.15
kernel. The wm8775 and cs53l32a are already moved over.
Since there is only a relatively
On Tuesday 08 November 2005 11:07, Axel Thimm wrote:
On Mon, Nov 07, 2005 at 08:13:51AM +0100, Hans Verkuil wrote:
A lot of work is going into 0.5.0 in order to move the saa7115,
saa7127 and cx25840 modules to the v4l repository and then to the
2.6.15 kernel. The wm8775 and cs53l32a are
14 matches
Mail list logo
