I guess I missed the reports that the kernel msp3400 started working with the ivtv driver again. Sorry for the duplicate report earlier.


At any rate, it works for me with opmode=1. You do have to unmute the device using ivtvctrl before you do the initial capture or you will get no audio.


One issue with the msp3400 driver shipped with the kernel is that you can't get accruate readings of the settings using ivtvctrl (i.e. MUTE).




On Mon, 10 Jan 2005, Gerd Knorr wrote:

David George <[EMAIL PROTECTED]> writes:

FYI, There was a last minute commit to 2.6.10 to change the default
msp3400 mode because it was causing some problems with certain bttv
cards.  Basically with ivtv the default mode is simpler, in 2.6.10 the
default mode was changed back to the bttv default of simple.  So if
the 2.6.10 msp3400 doesn't work try options simpler=1 for the msp3400
module.

No, the insmod option is "opmode":

  0 == manual
  1 == simple
  2 == simpler (i.e. ivtv).

At the moment the driver picks either 0 or 1 depending on the hardware
capabilities unless you overwrite that with the opmode insmod option.
opmode=1 might work with ivtv as well, any reports on this are
welcome.  opmode=2 broke Hauppauge bttv cards for not-yet known
reasons.

 Gerd

--
#define printk(args...) fprintf(stderr, ## args)

//========================================================\\ || D. Hageman <[email protected]> || \\========================================================//


------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to