On Tuesday 28 March 2006 21:54, Larry Symms wrote:
> Haven't heard from Hans about this in a while. One of two things
> occurred, he was sidetracked by more urgent issues, or the issue was
> corrected. I'm still on 0.3.6 drivers because I haven't taken the
> time to look into this as my problems are minor or rare. I'll be
> upgrading soon to newest 0.4 drivers so I'll report back with my
> results.
I've seen this happen with older firmwares, it's been awhile that I've
seen it with the latest firmware. It also sometimes happens after a lot
of rmmod ivtv/modprobe ivtv. Doing rmmod ivtv/modprobe ivtv another
time clears it up for me.
And indeed, I'm working hard to get some things in the kernel in time
for 2.6.17. Next week I'll have more time for some outstanding ivtv
issues.
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
