On Saturday 22 January 2005 17:43, Michael T. Dean wrote: > On 01/19/05 12:23, Charles Waddell wrote: > > here is the ivtv section of dmesg: > > Actually, just a partial... As explained in Jarod's guide, you should > get the ivtv initialization information with: > > tac /var/log/messages | > sed -n '/=\ \ END INIT IVTV\ \ =/,/= START INIT IVTV =/p; > /= START INIT IVTV =/q' | > tac > > The reason is because many of the most important messages do not contain > the string "ivtv", so "grep ivtv" doesn't work... well that should be easy enough to fix. why don't we change the drivers so that all the messages *do* start with ivtv. that way we will won't have this problem. it will also solve another problem (which has hit me in the past and i know others). that problem is loading the *wrong* version on msp3400.ko or tuner.ko, etc. if the ivtv versions output ivtv before every message then the difference should be obvious. -- simon
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
