From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Artem Bokhan <aptem@ngs.ru>
Cc: linux-media@vger.kernel.org
Subject: Re: problems with several saa7134 cards
Date: Tue, 14 Dec 2010 11:47:45 -0200 [thread overview]
Message-ID: <4D077581.9060008@redhat.com> (raw)
In-Reply-To: <4D062370.8070303@ngs.ru>
Em 13-12-2010 11:45, Artem Bokhan escreveu:
> 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.
> 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.
>
>
> The same problem with 2.6.36 kernel except "events" process have different name (can't remember exact name, sorry)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-12-14 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 13:45 problems with several saa7134 cards Artem Bokhan
2010-12-14 13:47 ` Mauro Carvalho Chehab [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D077581.9060008@redhat.com \
--to=mchehab@redhat.com \
--cc=aptem@ngs.ru \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.