On Tuesday 10 May 2005 10:50 am, Chris Kennedy wrote:
> Try this patch, I think it fixes that, let me know how it works...
>
> diff -ru ivtv-0.3.4j/ChangeLog ivtv-0.3.4k/ChangeLog
> --- ivtv-0.3.4j/ChangeLog       2005-05-10 01:10:50.000000000 -0500
> +++ ivtv-0.3.4k/ChangeLog       2005-05-10 12:48:17.000000000 -0500
> @@ -1,5 +1,7 @@
>  IVTV changes:
>
> +#0.3.4k - detect new pvr150 id.
> +
>  #0.3.4j - change way vbi decoding works for output through pvr350,
>            now lock and send vbi data on vsync interrupt.
>          - some debug messages removed.
> diff -ru ivtv-0.3.4j/driver/ivtv-cards.c ivtv-0.3.4k/driver/ivtv-cards.c
> --- ivtv-0.3.4j/driver/ivtv-cards.c     2005-05-08 09:37:39.000000000 -0500
> +++ ivtv-0.3.4k/driver/ivtv-cards.c     2005-05-10 12:49:12.000000000 -0500
> @@ -426,6 +426,7 @@
>         {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0xe807},
>         {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0xe817},
>         {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0xc801},
> +       {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0x0801},
>         {PCI_DEVICE_ID_IVTV16, IVTV_PCI_ID_HAUPPAUGE, 0x0009},
>         {0, 0, 0}
>  };
> diff -ru ivtv-0.3.4j/driver/ivtv-driver.h ivtv-0.3.4k/driver/ivtv-driver.h
> --- ivtv-0.3.4j/driver/ivtv-driver.h    2005-05-10 00:29:58.000000000 -0500
> +++ ivtv-0.3.4k/driver/ivtv-driver.h    2005-05-10 12:48:04.000000000 -0500
> @@ -130,7 +130,7 @@
>  #define IVTV_DRIVER_VERSION_MAJOR 0
>  #define IVTV_DRIVER_VERSION_MINOR 3
>  #define IVTV_DRIVER_VERSION_PATCHLEVEL 4
> -#define IVTV_DRIVER_VERSION_COMMENT "j"
> +#define IVTV_DRIVER_VERSION_COMMENT "k"
>  #define IVTV_VERSION __stringify(IVTV_DRIVER_VERSION_MAJOR) "."
> __stringify(IVTV_DRIVER_VERSION_MINOR) "."
> __stringify(IVTV_DRIVER_VERSION_PATCHLEVEL) "-" IVTV_DRIVER_VERSION_COMMENT
>
>  #define IVTV_DRIVER_VERSION
> KERNEL_VERSION(IVTV_DRIVER_VERSION_MAJOR,IVTV_DRIVER_VERSION_MINOR,IVTV_DRI
>VER_VERSION_PATCHLEVEL) diff -ru ivtv-0.3.4j/driver/ivtv-streams.c
> ivtv-0.3.4k/driver/ivtv-streams.c --- ivtv-0.3.4j/driver/ivtv-streams.c  
> 2005-05-09 11:25:39.000000000 -0500 +++ ivtv-0.3.4k/driver/ivtv-streams.c  
> 2005-05-10 11:06:08.000000000 -0500 @@ -470,7 +470,7 @@
>         ivtv_vapi(itv, IVTV_API_ASSIGN_BITRATES, 5,
> itv->codec.bitrate_mode, itv->codec.bitrate,   /* bps */
>
>
>
>
> Thanks,
> Chris


I think the end of the patch there is missing.  It failed, and it's pretty 
obvious that there are some lines missing in that last chunk, ivtv-streams.c

Also, just as a side note, I specified the card type and all works well again.  
If you can get a good patch out, I'll try it as soon as possible.

~Lou
>
> On Tue, May 10, 2005 at 10:43:38AM -0700, Louie Ilievski wrote:
> > On Monday 09 May 2005 11:22 pm, Chris Kennedy wrote:
> > > This syncs up and cleans up the pvr350 CC output, probably all VBI
> > > output, Hans is still working on what seems to be original CC packets
> > > missed and out of order for re-insertion, so this is just part of the
> > > fix.
> > >
> > > Also this fixes the OSD buffers for userspace pointers, which was
> > > broken from the dynamic stream stuff, but now uses the OSD stream
> > > instead of the decoder and so that's the default instead of the static
> > > ones now.
> > >
> > > #0.3.4j: http://www.ivtv.tv/releases/ivtv-0.3/
> > >
> > >
> > > Thanks,
> > > Chris
> >

Attachment: pgp4HAvxTPMkg.pgp
Description: PGP signature

Reply via email to