problems with several saa7134 cards
I use several (from three to five) saa7134-based cards on single PC. Currently
I'm trying to migrate from 2.6.22 to 2.6.32 (ubuntu lts).
I've got problems which I did not have with 2.6.22 kernel:
1. Depending on configuration load average holds 1 or 2 when saa7134 module is loaded. The reason is kernel process "events/".
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 16 root 20 0 0 0 0 S 3 0.0 9:36.89 events/1 15 root 20 0 0 0 0 D 3 0.0 9:35.81 events/0
2. Sound and video are not synced when recording with mencoder.
The same problem with 2.6.36 kernel except "events" process have different name (can't remember exact name, sorry)
Em 13-12-2010 11:45, Artem Bokhan escreveu:
Quoted 9 lines
I use several (from three to five) saa7134-based cards on single PC. Currently I'm trying to migrate from 2.6.22 to 2.6.32 (ubuntu lts).
I've got problems which I did not have with 2.6.22 kernel:
1. Depending on configuration load average holds 1 or 2 when saa7134 module is loaded. The reason is kernel process "events/".
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 16 root 20 0 0 0 0 S 3 0.0 9:36.89 events/1 15 root 20 0 0 0 0 D 3 0.0 9:35.81 events/0
Probably, it is IR polling. You may disable IR via modprobe parameter:
$ modinfo saa7134|grep ir parm: disable_ir:disable infrared remote support (int)
Not sure if this parameter is on .32 kernel of if it were added on a newer one.
Quoted 1 line
2. Sound and video are not synced when recording with mencoder.
I think that there are some parameters at mencoder to adjust the sync between video and audio (-delay?). Basically, it needs to delay either audio or video, in order to sync. The delay time is empiric, as the audio API doesn't provide any way to pass audio timestamps, currently.
Quoted 7 lines
The same problem with 2.6.36 kernel except "events" process have different name (can't remember exact name, sorry)
Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html