On Wed, 26 Oct 2011 15:58:32 -0400
James bjloc...@lockie.ca wrote:
On 10/26/11 15:49, Devin Heitmueller wrote:
On Wed, Oct 26, 2011 at 3:45 PM, Jamesbjloc...@lockie.ca wrote:
How many different formats are there (do I have to go through the
archive)? Would it be feasable to change femon
Hi,
I believe that I have found a problem with dtv_property_cache updating
when handling the legacy API. This was introduced between 2.6.39 and
3.0.
dtv_property_cache_submit() in dvb_frontend.c tests the field
delivery_system and if it's a legacy type (including SYS_UNDEFINED) then
it calls
On 05.11.2011 16:19, Lawrence Rust wrote:
Hi,
I believe that I have found a problem with dtv_property_cache updating
when handling the legacy API. This was introduced between 2.6.39 and
3.0.
dtv_property_cache_submit() in dvb_frontend.c tests the field
delivery_system and if it's a
On Sat, 2011-11-05 at 17:39 +0100, Andreas Oberritter wrote:
[snip]
How does MythTV set the parameters (i.e. using which interface, calls)?
If using S2API, it should also set DTV_DELIVERY_SYSTEM.
The following kern.log excerpt shows MythTV setting up the card:
Nov 5 11:54:52 cyclops kernel: [
On 05.11.2011 18:20, Lawrence Rust wrote:
On Sat, 2011-11-05 at 17:39 +0100, Andreas Oberritter wrote:
[snip]
How does MythTV set the parameters (i.e. using which interface, calls)?
If using S2API, it should also set DTV_DELIVERY_SYSTEM.
The following kern.log excerpt shows MythTV setting
On Sat, 2011-11-05 at 18:38 +0100, Andreas Oberritter wrote:
[snip]
I don't get how this could be useful. MythTV knows what delivery system
it wants to use, so it should pass this information to the kernel.
Trying to set an invalid delivery system must fail.
Using SYS_UNDEFINED as a pre-set
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date:Sat Nov 5 19:00:17 CET 2011
git hash:31cea59efb3a4210c063f31c061ebcaff833f583
gcc version: i686-linux-gcc
When enumerating an entity, assign the entire entity specification
instead of only the first two words. (This requires giving the
specification union a name.)
So far, no driver actually uses more than two words, but this will
be needed for ALSA entities.
Signed-off-by: Clemens Ladisch
