Skip to content
  1. Aug 25, 2009
  2. Aug 19, 2009
  3. Aug 18, 2009
  4. Aug 17, 2009
  5. Aug 16, 2009
  6. Aug 15, 2009
  7. Aug 14, 2009
    • Linus Torvalds's avatar
      Merge branch 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6 · 3011c7f0
      Linus Torvalds authored
      * 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6: (38 commits)
        V4L/DVB (12441): siano: read buffer overflow
        V4L/DVB (12440): Use kzalloc for frontend states to have struct dvb_frontend properly
        V4L/DVB (12438): Read buffer overflow
        V4L/DVB (12437): dvb: siano uses/depends on INPUT
        V4L/DVB (12436): stk-webcam: read buffer overflow
        V4L/DVB (12432): em28xx: fix regression in Empire DualTV digital tuning
        V4L/DVB (12429): v4l2-ioctl: fix G_STD and G_PARM default handlers
        V4L/DVB (12428): hdpvr: add missing initialization of current_norm
        V4L/DVB (12424): soc-camera: fix recursive locking in .buf_queue()
        V4L/DVB (12422): media/zr364xx: fix build errors
        V4L/DVB (12405): em28xx-cards: move register 0x13 setting to the proper place
        V4L/DVB (12411): em28xx: Fix artifacts with Silvercrest webcam
        V4L/DVB (12410): em28xx: Move the non-board dependent part to be outside em28xx_pre_card_setup()
        V4L/DVB (12407): em28xx: Adjust Silvercrest xtal frequency
        V4L/DVB (12406): em28xx: fix: don't do image interlacing on webcams
        V4L/DVB (12403): em28xx: properly reports some em2710 chips
        V4L/DVB (12402): em28xx: fix: some em2710 chips use a different vendor ID
        V4L/DVB (12401): m9v011: add vflip/hflip controls to control mirror/upside down
        V4L/DVB (12400): em28xx: Allow changing fps on webcams
        V4L/DVB (12399): mt9v011: Add support for controlling frame rates
        ...
      3011c7f0
    • Steven Whitehouse's avatar
      GFS2: Fix permissions on "recover" file · d7e623da
      Steven Whitehouse authored
      
      
      Although this file is only ever written and not read by
      userspace, it seems that the utils are opening this
      file O_RDWR, so we need to allow that.
      
      Also fixes the whitespace which seemed to be broken.
      
      Signed-off-by: default avatarSteven Whitehouse <swhiteho@redhat.com>
      Cc: David Teigland <teigland@redhat.com>
      d7e623da
    • Valentin Longchamp's avatar
      mx31moboard: invert sdhc ro signal sense · 563abb4b
      Valentin Longchamp authored
      
      
      Small confusion with our hardware engineer, the WP signal (RO) is
      active low on our boards, the signal has to inverted.
      
      This is a pretty straightforward patch, it could even go to -rc,
      but if not, then push it for 2.6.32.
      
      Signed-off-by: default avatarValentin Longchamp <valentin.longchamp@epfl.ch>
      Signed-off-by: default avatarSascha Hauer <s.hauer@pengutronix.de>
      563abb4b
    • Davide Rizzo's avatar
      ARM: S3C24XX: Fix clkout mpx error · 48ec45e7
      Davide Rizzo authored
      
      
      Bug correction: CLK Outputs cannot have XTAL as parent
      
      Signed-off-by: default avatarDavide Rizzo <elpa.rizzo@gmail.com>
      [ben-linux@fluff.org: updated patch subject]
      Signed-off-by: default avatarBen Dooks <ben-linux@fluff.org>
      48ec45e7
    • Ramax Lo's avatar
      ARM: S3C64XX: serial: Fix a typo in Kconfig · a219dc4d
      Ramax Lo authored
      
      
      The typo causes drivers/serial/s3c6400.c not being built for s3c6400 platform.
      
      Signed-off-by: default avatarRamax Lo <ramaxlo@gmail.com>
      Signed-off-by: default avatarBen Dooks <ben-linux@fluff.org>
      a219dc4d
    • Roel Kluin's avatar
      V4L/DVB (12441): siano: read buffer overflow · 08b39642
      Roel Kluin authored
      
      
      With mode DEVICE_MODE_RAW_TUNER a read occurs past the end of smscore_fw_lkup[].
      Subsequently an attempt is made to load the firmware from the resulting
      filename.
      
      Signed-off-by: default avatarRoel Kluin <roel.kluin@gmail.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarDouglas Schilling Landgraf <dougsland@redhat.com>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      08b39642
    • Matthias Schwarzott's avatar
      V4L/DVB (12440): Use kzalloc for frontend states to have struct dvb_frontend properly · 084e24ac
      Matthias Schwarzott authored
      
      
      This patch changes most frontend drivers to allocate their state structure via
      kzalloc and not kmalloc. This is done to properly initialize the
      embedded "struct dvb_frontend frontend" field, that they all have.
      
      The visible effect of this struct being uninitalized is, that the member "id"
      that is used to set the name of kernel thread is totally random.
      
      Some board drivers (for example cx88-dvb) set this "id" via
      videobuf_dvb_alloc_frontend but most do not.
      
      So I at least get random id values for saa7134, flexcop and ttpci based cards.
      It looks like this in dmesg:
      DVB: registering adapter 1 frontend -10551321 (ST STV0299 DVB-S)
      
      The related kernel thread then also gets a strange name
      like "kdvb-ad-1-fe--1".
      
      Cc: Michael Krufky <mkrufky@linuxtv.org>
      Cc: Steven Toth <stoth@linuxtv.org>
      Cc: Timothy Lee <timothy.lee@siriushk.com>
      Cc: Igor M. Liplianin <liplianin@me.by>
      Signed-off-by: default avatarMatthias Schwarzott <zzam@gentoo.org>
      Acked-by: default avatarAndreas Oberritter <obi@linuxtv.org>
      Signed-off-by: default avatarDouglas Schilling Landgraf <dougsland@redhat.com>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      084e24ac
    • Roel Kluin's avatar
      V4L/DVB (12438): Read buffer overflow · bb2b4542
      Roel Kluin authored
      
      
      parport[n] is checked before n < MAX_CAMS
      
      Signed-off-by: default avatarRoel Kluin <roel.kluin@gmail.com>
      Signed-off-by: default avatarDouglas Schilling Landgraf <dougsland@redhat.com>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      bb2b4542
    • Randy Dunlap's avatar
      V4L/DVB (12437): dvb: siano uses/depends on INPUT · 27059b35
      Randy Dunlap authored
      
      
      siano uses input_*() functions so it should depend on INPUT
      to prevent build errors:
      
      ERROR: "input_event" [drivers/media/dvb/siano/sms1xxx.ko] undefined!
      ERROR: "input_register_device" [drivers/media/dvb/siano/sms1xxx.ko] undefined!
      ERROR: "input_free_device" [drivers/media/dvb/siano/sms1xxx.ko] undefined!
      ERROR: "input_unregister_device" [drivers/media/dvb/siano/sms1xxx.ko] undefined!
      ERROR: "input_allocate_device" [drivers/media/dvb/siano/sms1xxx.ko] undefined!
      
      Cc: Michael Krufky <mkrufky@linuxtv.org>
      Cc: Uri Shkolnik <uris@siano-ms.com>
      Signed-off-by: default avatarRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: default avatarDouglas Schilling Landgraf <dougsland@redhat.com>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      27059b35
    • Roel Kluin's avatar
      V4L/DVB (12436): stk-webcam: read buffer overflow · 77f2c2db
      Roel Kluin authored
      
      
      It tested the value of stk_sizes[i].m before checking whether i was in range.
      
      Cc: Hans Verkuil <hverkuil@xs4all.nl>
      Cc: Trent Piepho <xyzzy@speakeasy.org>
      Signed-off-by: default avatarRoel Kluin <roel.kluin@gmail.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarDouglas Schilling Landgraf <dougsland@redhat.com>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      77f2c2db
    • Devin Heitmueller's avatar
      V4L/DVB (12432): em28xx: fix regression in Empire DualTV digital tuning · 01a5fd6f
      Devin Heitmueller authored
      
      
      Restore support for digital tuning caused by regression during introduction
      of disable_i2c_gate parameter to zl10353 driver.
      
      Thanks to user "Xwang" for reporting the problem and testing the fix
      
      Cc: Xwang <xwang1976@email.it>
      Signed-off-by: default avatarDevin Heitmueller <dheitmueller@kernellabs.com>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      01a5fd6f
    • Hans Verkuil's avatar
      V4L/DVB (12429): v4l2-ioctl: fix G_STD and G_PARM default handlers · 9bedc7f7
      Hans Verkuil authored
      
      
      The v4l core supplies default handlers for G_STD and G_PARM. However, both
      default handlers are buggy.
      
      This patch fixes the following:
      
      1) If no g_std is supplied and current_norm == 0, then this driver does not
         support TV video standards (e.g. a radio or webcam driver). Return
         -EINVAL. This ensures that there is no bogus VIDIOC_G_STD support for
         such drivers.
      
      2) The default VIDIOC_G_PARM handler used current_norm instead of first
         checking if the driver supported g_std and calling that to get the norm.
         It also didn't check if current_norm was 0, since in that case the driver
         does not support TV standards (or no standard was set at all) and the
         default handler should return -EINVAL.
      
      Note that I am very unhappy with these default handlers: I think they
      basically behave like some very strange and unexpected side-effect.
      
      Signed-off-by: default avatarHans Verkuil <hverkuil@xs4all.nl>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      9bedc7f7
    • Hans Verkuil's avatar
      V4L/DVB (12428): hdpvr: add missing initialization of current_norm · 99362e1e
      Hans Verkuil authored
      
      
      Drivers should either set current_norm or supply a g_std callback.
      
      The hdpvr driver does neither. Since it initializes to a 60 Hz format
      I've initialized the current_norm to NTSC | PAL_M | PAL_60 which is the
      60 Hz subset of tvnorms.
      
      Cc: Janne Grunau <j@jannau.net>
      Signed-off-by: default avatarHans Verkuil <hverkuil@xs4all.nl>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      99362e1e
    • Guennadi Liakhovetski's avatar
      V4L/DVB (12424): soc-camera: fix recursive locking in .buf_queue() · 2dd54a54
      Guennadi Liakhovetski authored
      
      
      The .buf_queue() V4L2 driver method is called under
      spinlock_irqsave(q->irqlock,...), don't take the lock again inside the
      function.
      
      Reported-by: default avatarAntonio Ospite <ospite@studenti.unina.it>
      Signed-off-by: default avatarGuennadi Liakhovetski <g.liakhovetski@gmx.de>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      2dd54a54
    • Randy Dunlap's avatar
      V4L/DVB (12422): media/zr364xx: fix build errors · 7d2e2e35
      Randy Dunlap authored
      
      
      Fix build errors in zr364xx by adding selects:
      
      zr364xx.c:(.text+0x195ed7): undefined reference to `videobuf_streamon'
      zr364xx.c:(.text+0x196030): undefined reference to `videobuf_dqbuf'
      zr364xx.c:(.text+0x1960c4): undefined reference to `videobuf_qbuf'
      zr364xx.c:(.text+0x196123): undefined reference to `videobuf_querybuf'
      zr364xx.c:(.text+0x196182): undefined reference to `videobuf_reqbufs'
      zr364xx.c:(.text+0x196224): undefined reference to `videobuf_queue_is_busy'
      zr364xx.c:(.text+0x196390): undefined reference to `videobuf_vmalloc_free'
      zr364xx.c:(.text+0x196571): undefined reference to `videobuf_iolock'
      zr364xx.c:(.text+0x196678): undefined reference to `videobuf_mmap_mapper'
      zr364xx.c:(.text+0x196760): undefined reference to `videobuf_poll_stream'
      zr364xx.c:(.text+0x19689a): undefined reference to `videobuf_read_one'
      zr364xx.c:(.text+0x1969ec): undefined reference to `videobuf_mmap_free'
      zr364xx.c:(.text+0x197862): undefined reference to `videobuf_queue_vmalloc_init'
      zr364xx.c:(.text+0x197a28): undefined reference to `videobuf_streamoff'
      zr364xx.c:(.text+0x198203): undefined reference to `videobuf_to_vmalloc'
      zr364xx.c:(.text+0x198603): undefined reference to `videobuf_streamoff'
      drivers/built-in.o: In function `free_buffer':
      zr364xx.c:(.text+0x19930c): undefined reference to `videobuf_vmalloc_free'
      drivers/built-in.o: In function `zr364xx_open':
      zr364xx.c:(.text+0x19a7de): undefined reference to `videobuf_queue_vmalloc_init'
      drivers/built-in.o: In function `read_pipe_completion':
      zr364xx.c:(.text+0x19b17f): undefined reference to `videobuf_to_vmalloc'
      
      Signed-off-by: default avatarRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: default avatarDouglas Schilling Landgraf <dougsland@redhat.com>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      7d2e2e35
    • Mauro Carvalho Chehab's avatar
      V4L/DVB (12405): em28xx-cards: move register 0x13 setting to the proper place · d7612c86
      Mauro Carvalho Chehab authored
      
      
      Register 0x13 seems to be a sort of image control, maybe gamma, white
      level or black level. Lower values produce better images, while higher
      values increases the contrast and shifts colors to green. 0xff produces
      a black image. This register is not Silvercrest-specific, so its code
      should be moved to a better place.
      
      If this register is left alone, a random value can be found at the
      register, producing weird results.
      
      While here, let's remove register 0x0d, as it had no noticed effect at
      the image.
      
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      d7612c86
    • Mauro Carvalho Chehab's avatar
      V4L/DVB (12411): em28xx: Fix artifacts with Silvercrest webcam · 3d3215c4
      Mauro Carvalho Chehab authored
      
      
      Silvercrest mt9v011 sensor produces a 640x480 image. However,
      previously, the code were getting only half of the lines and merging two
      consecutive frames to "produce" a 640x480 image.
      
      With the addition of progressive mode, now em28xx is working with a full
      image. However, when the number of lines is bigger than 240, the
      beginning of some odd lines are filled with blank.
      
      After lots of testing, and physically checking the device for a Xtal, it
      was noticed experimentally that mt9v011 is using em28xx XCLK as its
      clock. Due to that, changing XCLK value changes the maximum speed of the
      stream.
      
      At the tests, it were possible to produce up to 32 fps, using a 30 MHz
      XCLK. However, at that rate, the artifacts happen even at 320x240. Lower
      values of XCLK produces artifacts only at 640x480.
      
      At some values of xclk (for example XCLKK = 6 MHz, 640x480), it is
      possible to see an invalid sucession of artifacts with this pattern:
      
      .xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      ..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      ...xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      ....xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      .xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      ..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      ...xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      ....xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      
      (where the dots represent the blanked pixels)
      
      So, it seems that a waveform in the format of a ramp is interferring at
      the image.
      
      The cause of this interference is currently unknown. Some possibilities
      are:
      	- electrical interference (maybe this device is broken?);
      	- some issue at mt9v011 programming;
      	- some bug at em28xx chip.
      
      So, for now, let's be conservative and use a value of XCLK that we know
      for sure that it won't cause artifacts.
      
      As I'm waiting for more of such devices with different em28xx chipset
      revisions, I'll have the opportunity to double check the issue with
      other pieces of hardware.
      
      Later patches can vary XCLK depending on the vertical resolutions, if a
      proper fix is not discovered.
      
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      3d3215c4