Re: [ivtv-devel] [PATCH] more cx25840 cleanup

2005-05-27 Thread Allan Stirling
Chris Kennedy wrote: Yeah, that is strange, I was wondering how it fixed it too, maybe the chip just saw the video re-init and does something about audio automatically? I'll know within a day or so if it really fixed it, I'll look at the audio re-init too, sounds interesting to do that too. Tha

Re: [ivtv-devel] [PATCH] more cx25840 cleanup

2005-05-27 Thread Chris Kennedy
Yeah, that is strange, I was wondering how it fixed it too, maybe the chip just saw the video re-init and does something about audio automatically? I'll know within a day or so if it really fixed it, I'll look at the audio re-init too, sounds interesting to do that too. Thanks, Chris On Fri, May 2

Re: [ivtv-devel] [PATCH] more cx25840 cleanup

2005-05-27 Thread Tyler Trafford
Oh, I forgot to mention that I made SET_NORM check to see if it was already set, and not do anything if it was... i can't see how that could break what you did, though. Your force of state->input should still make the input reinitialize correctly. You may want to reinit the audio_input too though

Re: [ivtv-devel] [PATCH] more cx25840 cleanup

2005-05-27 Thread Chris Kennedy
Actually one problem I see with this patch, and it's a recent change which I'm still trying to figure out the reasons for needing. There seems to be a problem running the pvr500/150 over extended periods of time for audio, will just stop working eventually, after a day or so. It seems that if you

[ivtv-devel] [PATCH] more cx25840 cleanup

2005-05-27 Thread Tyler Trafford
Straight forward patch, does the following: * During initialization, instead of iteratively copying the array values for cx25840_input_layout, just the set a pointer to the proper array. * In DECODER_SET_INPUT, assign state->input after performing operation successfully. Also tried to make debug