On Monday 05 February 2007 11:16, Axel Thimm wrote:
> On Sat, Feb 03, 2007 at 12:48:10PM +0100, Hans Verkuil wrote:
> > It took a long time (over 5 months) but here is the first release
> > candidate for the redesigned and cleaned up ivtv-0.10.0 driver.
>
> Thanks & congrats!
>
> > This driver will work with kernels 2.6.18 and 2.6.19.
>
> I'm building packages for RHEL and FC as appropriate, they will land
> in atrpms-testing.
Be aware of the new encoder firmware included with the package! When I
make a final release I'll ensure that it will be part of the firmware
tarball on ivtvdriver.org and that the older ivtv versions (0.4, 0.6,
0.7) can be used with that larger firmware.
> > My intention is to release a ivtv-0.18.0 for kernel 2.6.18, 0.19.0
> > for kernel 2.6.19 and a 0.20.0 for kernel 2.6.20. This keeps the
> > numbering nicely regular. There will probably also be a 0.21.0 for
> > kernel 2.6.21,
>
> If it wouldn't be a too big issue I would recommend using the same
> versioning throughout all supported kernels. I think it makes the
> users' handling easier, as well as for people reviewing the code,
> e.g. it is easier to review some conditionals based on kernel
> versions than to have several trees.
>
> It also makes packaging far more easier, as the userland portions
> remain in the same versioned subpackage, even if people have both
> 2.6.18 and 2.6.19 kernels and ivtv kernel subpackages installed.
True, but on the other hand it is much more like what it will be when
the driver enters the kernel: only limited fixes for older kernels. But
I'm not yet certain how to handle this.
Regards,
Hans
PS: the latest trunk contains patches to make it work with kernel
2.6.20, however I have major problems with the cx25840 module which
gives a kobject error and won't load its firmware. It's something in
the i2c setup somewhere that's causing it. For now I assume it is a
ivtv bug.
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
