From: Marko Ristola <marko.ristola@kolumbus.fi>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: VDR User <user.vdr@gmail.com>,
linux-media@vger.kernel.org,
Manu Abraham <abraham.manu@gmail.com>,
Ozan ?a?layan <ozan@pardus.org.tr>,
Manu Abraham <manu@linuxtv.org>,
stable@kernel.org
Subject: Re: [PATCH] Mantis, hopper: use MODULE_DEVICE_TABLE use the macro to make modules auto-loadable
Date: Mon, 21 Jun 2010 22:01:57 +0300 [thread overview]
Message-ID: <4C1FB725.6070707@kolumbus.fi> (raw)
In-Reply-To: <87vd9c72id.fsf@nemi.mork.no>
21.06.2010 19:51, Bjørn Mork wrote:
> VDR User<user.vdr@gmail.com> writes:
>
>
>> Instead of copy&paste patches from Manu's tree, maybe it's better to
>> just wait for him to push all the changes into v4l.
>>
>
I'm Manu sorry about trying to put patches directly into v4-dvb, if
those should go onto your branch first.
So, what Manu do you think about my DMA patch or other patches I sent
into linux-media mailing list this weekend?
Is it okay to generate one interrupt once per 16k bytes,
or are the interrupts too rare?
At least VDR reads the DVB stream rarely, so I think
that it is enough if the DVB card has always something
to be delivered when VDR or MythTV asks more data,
so if the number of DMA transfer IRQs is twice than the
number of times VDR or MythTV asks more data per second,
then the context switches are in balance.
Understandable DMA RISC programming should be easier to maintain, and it
removes the initial garbage from the stream too.
How about the tasklet enable/disable patch I wrote?
What needs to be done for these patches to be accepted?
Best regards,
Marko
prev parent reply other threads:[~2010-06-21 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 8:52 [PATCH] Mantis, hopper: use MODULE_DEVICE_TABLE use the macro to make modules auto-loadable Bjørn Mork
2010-06-21 16:12 ` VDR User
2010-06-21 16:51 ` Bjørn Mork
2010-06-21 19:01 ` Marko Ristola [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=4C1FB725.6070707@kolumbus.fi \
--to=marko.ristola@kolumbus.fi \
--cc=abraham.manu@gmail.com \
--cc=bjorn@mork.no \
--cc=linux-media@vger.kernel.org \
--cc=manu@linuxtv.org \
--cc=ozan@pardus.org.tr \
--cc=stable@kernel.org \
--cc=user.vdr@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox