1. 05 Jan, 2012 8 commits
  2. 04 Jan, 2012 15 commits
  3. 01 Jan, 2012 1 commit
  4. 31 Dec, 2011 16 commits
    • Mauro Carvalho Chehab's avatar
    • Mauro Carvalho Chehab's avatar
      [media] fs/compat_ioctl: it needs to see the DVBv3 compat stuff · e97a5d89
      Mauro Carvalho Chehab authored
      Only the ioctl core should see the DVBv3 compat stuff, as its
      contents are not available anymore to the drivers.
      
      As fs/compat_ioctl also handles DVBv3 ioctl's, it needs those
      definitions:
      
          fs/compat_ioctl.c:1345: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1345: error: array type has incomplete element type
          fs/compat_ioctl.c:1345: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1345: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1345: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1345: error: array type has incomplete element type
          fs/compat_ioctl.c:1345: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1345: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1345: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1345: error: array type has incomplete element type
          fs/compat_ioctl.c:1345: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1345: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1345: error: initializer element is not constant
          fs/compat_ioctl.c:1345: error: (near initialization for ‘ioctl_pointer[462]’)
          fs/compat_ioctl.c:1346: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1346: error: array type has incomplete element type
          fs/compat_ioctl.c:1346: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1346: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1346: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1346: error: array type has incomplete element type
          fs/compat_ioctl.c:1346: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1346: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1346: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1346: error: array type has incomplete element type
          fs/compat_ioctl.c:1346: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1346: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_parameters’
          fs/compat_ioctl.c:1346: error: initializer element is not constant
          fs/compat_ioctl.c:1346: error: (near initialization for ‘ioctl_pointer[463]’)
          fs/compat_ioctl.c:1347: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_event’
          fs/compat_ioctl.c:1347: error: array type has incomplete element type
          fs/compat_ioctl.c:1347: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_event’
          fs/compat_ioctl.c:1347: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_event’
          fs/compat_ioctl.c:1347: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_event’
          fs/compat_ioctl.c:1347: error: array type has incomplete element type
          fs/compat_ioctl.c:1347: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_event’
          fs/compat_ioctl.c:1347: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_event’
          fs/compat_ioctl.c:1347: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_event’
          fs/compat_ioctl.c:1347: error: array type has incomplete element type
          fs/compat_ioctl.c:1347: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_event’
          fs/compat_ioctl.c:1347: error: invalid application of ‘sizeof’ to incomplete type ‘struct dvb_frontend_event’
          fs/compat_ioctl.c:1347: error: initializer element is not constant
          fs/compat_ioctl.c:1347: error: (near initialization for ‘ioctl_pointer[464]’)
      Reported-by: default avatarMichael Krufky <mkrufky@linuxtv.org>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      e97a5d89
    • Mauro Carvalho Chehab's avatar
    • Mauro Carvalho Chehab's avatar
      a95c471e
    • Mauro Carvalho Chehab's avatar
      [media] dvb: Add ops.delsys to the remaining frontends · 533b673b
      Mauro Carvalho Chehab authored
      A few drivers don't have .delsys. Add it, in order to allow
      future patches for dvb_frontend.c to not use info.type.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      533b673b
    • Mauro Carvalho Chehab's avatar
      [media] dvb: don't require a parameter for get_frontend · 7c61d80a
      Mauro Carvalho Chehab authored
      Just like set_frontend, use the dvb cache properties for get_frontend.
      This is more consistent, as both functions are now symetric. Also,
      at the places get_frontend is called, it makes sense to update the
      cache.
      
      Most of this patch were generated by this small perl script:
      
      	while (<>) { $file .= $_; }
      	if ($file =~ m/\.get_frontend\s*=\s*([\d\w_]+)/) {
      		my $get = $1;
      		$file =~ s/($get)(\s*\([^\,\)]+)\,\s*struct\s+dtv_frontend_properties\s*\*\s*([_\d\w]+)\)\s*\{/\1\2)\n{\n\tstruct dtv_frontend_properties *\3 = &fe->dtv_property_cache;/g;
      	}
      	print $file;
      
      Of course, the changes at dvb_frontend.[ch] were made by hand,
      as well as the changes on a few other places, where get_frontend()
      is called internally inside the driver.
      
      On some places, get_frontend() were just a void function. Those
      occurrences were removed, as the DVB core handles such cases.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      7c61d80a
    • Mauro Carvalho Chehab's avatar
      [media] dvb_frontend: Fix inversion breakage due to DVBv5 conversion · ac3852c4
      Mauro Carvalho Chehab authored
      On several places inside dvb_frontend, only the DVBv3 parameters
      were updated. Change it to be sure that, on all places, the DVBv5
      parameters will be changed instead.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      ac3852c4
    • Mauro Carvalho Chehab's avatar
      [media] s921: Properly report the delivery system · 63aad05b
      Mauro Carvalho Chehab authored
      Before this patch, a query for the delivery systems were
      returned SYS_UNDEFINED.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      63aad05b
    • Mauro Carvalho Chehab's avatar
      [media] dvb-core: be sure that drivers won't use DVBv3 internally · 8de8594a
      Mauro Carvalho Chehab authored
      Now that all frontends are implementing DVBv5, don't export the
      DVBv3 specific stuff to the drivers. Only the core should be
      aware of that, as it will keep providing DVBv3 backward compatibility.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      8de8594a
    • Mauro Carvalho Chehab's avatar
      [media] cx23885-dvb: Remove a dirty hack that would require DVBv3 · a7d44baa
      Mauro Carvalho Chehab authored
      The cx23885-dvb driver has a dirty hack:
      	1) it hooks the DVBv3 legacy call to FE_SET_FRONTEND;
      	2) it uses internally the DVBv3 struct to decide some
      	   configs.
      
      Replace it by a change during the gate control. This will
      likely work, but requires testing. Anyway, the current way
      will break, as soon as we stop copying data for DVBv3 for
      pure DVBv5 calls.
      
      Compile-tested only.
      
      Cc: Michael Krufky <mkrufky@linuxtv.org>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      a7d44baa
    • Mauro Carvalho Chehab's avatar
      [media] dvb: don't use DVBv3 bandwidth macros · c6f56e7d
      Mauro Carvalho Chehab authored
      Every frontend now uses DVBv5 way. So, let's not use the DVBv3
      macros internally anymore.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      c6f56e7d
    • Mauro Carvalho Chehab's avatar
      [media] dvb-core: don't use fe_bandwidth_t on driver · 88ab898f
      Mauro Carvalho Chehab authored
      Now that everybody is talking DVBv5 API dialect, using this
      DVBv3 macro internally is not ok.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      88ab898f
    • Mauro Carvalho Chehab's avatar
      [media] dvb: remove the track() fops · 1b5d8716
      Mauro Carvalho Chehab authored
      This callback is not used anywhere. Maybe it were used in the
      past to optimize the custom algo, but, as it is not used anymore,
      let's just remove it.
      
      If later needed, some patch may re-add it with a proper
      implementation.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      1b5d8716
    • Mauro Carvalho Chehab's avatar
      [media] dvb: don't pass a DVBv3 parameter for search() fops · 41da5320
      Mauro Carvalho Chehab authored
      Just like the other DVB algorithms, drivers should use the DVBv5
      way to retrieve parameters: via the cache struct.
      
      Actually, several drivers were partially using the DVBv3 struct
      and partially using the DVBv5 way, with is confusing and may
      lead into troubles.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      41da5320
    • Mauro Carvalho Chehab's avatar
      [media] dvb-core: Don't pass DVBv3 parameters on tune() fops · 7e072221
      Mauro Carvalho Chehab authored
      As all parameters are passed via DVBv5 to the frontends, there's
      no need to pass them again via fops. Also, most drivers weren't using
      it anyway. So, instead, just pass a parameter to indicate if the
      hardware algorithm wants the driver to re-tune or not.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      7e072221
    • Mauro Carvalho Chehab's avatar
      [media] dvb: simplify get_tune_settings() struct · 5581e130
      Mauro Carvalho Chehab authored
      In the past, dvb_frontent_parameters were passed inside the
      struct where get_tuner_settings should store their result.
      
      This is not needed anymore, as all parameters needed are stored
      already at the fe property cache. So, use it, where needed.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      5581e130