On Friday 31 March 2006 23:55, Martin Dauskardt wrote:
> > From: Hans Verkuil <[EMAIL PROTECTED]>
> >
> > You can also try to go back to an older encoder firmware
> > (0x02040011 is also a good version). I've seen differences in
> > behavior based on fw version. Did you also change firmware versions
> > when you upgraded to 0.7? How old is your PVR-350?
>
> My PVR350 is about two years old and has a tuner which was supported
> even by 2.4 kernels. I used encoder firmware 0x02050032 with 0.4.4x
> and did not change it when I made the first test with 0.7.0
OK
>
> Both firmware work with 2.6.15/0.4.x
>
> Is there something I can debug to help?
>
> When I use 2.6.15 + ivtv 0.4.x the timeout appears from time to time,
> but not often. But when it appears, it is always when I zap through
> analog channels. Using the decoder fo watching TV from a DVB-T card
> has never resulted a firmware timeout.
>
> I would also like to test 0.6.1, but as I already posted, it is not
> possible to compile this on a 2.6.16 system with installed
> v4l-dvb-drivers
I hope to have more time after the weekend (although there seem to be a
lot of different issues at the moment, each pretty hard to reproduce).
One test you can do is to run ivtvctl -H (reload the fw) and see what
happens. Another is to see what has changed in the ivtv initialization
since the last version you used. As far as I am aware I didn't make any
changes that could cause this, but obviously something changed. If you
can pinpoint the change that introduced this, that would be a great
help.
If you can do tests and investigate (with pointers from me when needed)
I'd really appreciate it given the list of things I still have to look
into. It's probably faster than waiting for me to get around it would
be.
Regards,
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
