On Fri, Jan 07, 2005 at 10:58:21PM -0500, Michael T. Dean wrote: > On 01/07/2005 09:15 PM, Axel Thimm wrote: > > >while packaging ivtv 0.3.x I found two things: > > > >a) the required tuner.ko modle (for PVR 150/500) will conflict with > > v4l's tuner module. Just like for msp3400 I renamed it for the rpms > > to tuner-ivtv.ko. So you need alias tuner tuner-ivtv in your > > modprobe.conf file to get ivtv's tuner.
> As of right now, the indexes for both of the new tuners in tuner-ivtv > have already been used--i.e., in ivtv's tuner.h: > > #define TUNER_LG_PAL_TAPE_PVR150 51 > #define TUNER_PHILIPS_FM1216ME_PVR150 52 > > in the V4L tuner.h: > > #define TUNER_PHILIPS_FM1256_IH3 51 > #define TUNER_THOMSON_DTT7610 52 That's bad, we should ask Gerd for assigning two slots before grabbing them. :/ > Merging the msp3400 changes into the official msp3400 module was (the > beginning of--we're not yet done with that one) a step in the right > direction. Starting to distribute our own tuner module is a giant leap > in the wrong direction. (Apologies to Neil Armstrong.) The tuner module in ivtv is transitional. It should get shaped into something we can submit to Gerd, and kept during a transition phase (which, if support for 2.4 is dropped, will be small). -- Axel.Thimm at ATrpms.net
pgp4U22hlDfrM.pgp
Description: PGP signature
