Re: Doing a stable v4l-utils release

2010-04-30 Thread Hans Verkuil
On Wednesday 28 April 2010 08:22:03 Hans Verkuil wrote:
 On Tuesday 27 April 2010 10:08:06 Hans de Goede wrote:
  Hi,
  
  On 04/26/2010 09:55 AM, Hans Verkuil wrote:
   On Monday 26 April 2010 09:35:23 Hans de Goede wrote:
   Hi all,
  
   Currently v4l-utils is at version 0.7.91, which as the version
   suggests is meant as a beta release.
  
   As this release seems to be working well I would like to do
   a v4l-utils-0.8.0 release soon. This is a headsup, to give
   people a chance to notify me of any bugs they would like to
   see fixed first / any patches they would like to add first.
  
   This is a good opportunity to mention that I would like to run checkpatch
   over the libs and clean them up.
  
   I also know that there is a bug in the control handling code w.r.t.
   V4L2_CTRL_FLAG_NEXT_CTRL. I have a patch, but I'd like to do the clean up
   first.
  
   If no one else has major patch series that they need to apply, then I can
   start working on this. The clean up is just purely whitespace changes to
   improve readability, no functionality will be touched.
  
  
  I've no big changes planned on the short term, so from my pov go ahead.
 
 As you noticed I have cleaned up the includes, libv4l1 and libv4l2. 
 libv4lconvert
 is a lot more work, so I will do that bit by bit, hopefully this week.

I just finished doing the checkpatch conversions (phew!). This weekend I will
push the control bug fix and I also have a v4l2-ctl enhancement pending that
I will try to upstream today.

Regards,

Hans

-- 
Hans Verkuil - video4linux developer - sponsored by TANDBERG, part of Cisco
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: WARNINGS

2010-04-30 Thread Hans Verkuil
This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.

Results of the daily build of v4l-dvb:

date:Thu Apr 29 19:00:29 CEST 2010
path:http://www.linuxtv.org/hg/v4l-dvb
changeset:   14618:905d76b95175
git master:   f6760aa024199cfbce564311dc4bc4d47b6fb349
git media-master: d3be2fab3a10b6c798a5f9970146d166d3345c37
gcc version:  i686-linux-gcc (GCC) 4.4.3
host hardware:x86_64
host os:  2.6.32.5

linux-2.6.32.6-armv5: OK
linux-2.6.33-armv5: OK
linux-2.6.34-rc1-armv5: OK
linux-2.6.32.6-armv5-davinci: OK
linux-2.6.33-armv5-davinci: OK
linux-2.6.34-rc1-armv5-davinci: OK
linux-2.6.32.6-armv5-ixp: OK
linux-2.6.33-armv5-ixp: OK
linux-2.6.34-rc1-armv5-ixp: OK
linux-2.6.32.6-armv5-omap2: OK
linux-2.6.33-armv5-omap2: OK
linux-2.6.34-rc1-armv5-omap2: OK
linux-2.6.22.19-i686: WARNINGS
linux-2.6.23.17-i686: WARNINGS
linux-2.6.24.7-i686: OK
linux-2.6.25.20-i686: OK
linux-2.6.26.8-i686: OK
linux-2.6.27.44-i686: OK
linux-2.6.28.10-i686: OK
linux-2.6.29.1-i686: WARNINGS
linux-2.6.30.10-i686: OK
linux-2.6.31.12-i686: OK
linux-2.6.32.6-i686: OK
linux-2.6.33-i686: OK
linux-2.6.34-rc1-i686: WARNINGS
linux-2.6.32.6-m32r: OK
linux-2.6.33-m32r: OK
linux-2.6.34-rc1-m32r: OK
linux-2.6.32.6-mips: OK
linux-2.6.33-mips: OK
linux-2.6.34-rc1-mips: OK
linux-2.6.32.6-powerpc64: OK
linux-2.6.33-powerpc64: OK
linux-2.6.34-rc1-powerpc64: WARNINGS
linux-2.6.22.19-x86_64: WARNINGS
linux-2.6.23.17-x86_64: WARNINGS
linux-2.6.24.7-x86_64: OK
linux-2.6.25.20-x86_64: OK
linux-2.6.26.8-x86_64: OK
linux-2.6.27.44-x86_64: OK
linux-2.6.28.10-x86_64: OK
linux-2.6.29.1-x86_64: WARNINGS
linux-2.6.30.10-x86_64: OK
linux-2.6.31.12-x86_64: OK
linux-2.6.32.6-x86_64: OK
linux-2.6.33-x86_64: OK
linux-2.6.34-rc1-x86_64: WARNINGS
linux-git-armv5: WARNINGS
linux-git-armv5-davinci: WARNINGS
linux-git-armv5-ixp: WARNINGS
linux-git-armv5-omap2: WARNINGS
linux-git-i686: WARNINGS
linux-git-m32r: OK
linux-git-mips: OK
linux-git-powerpc64: OK
linux-git-x86_64: WARNINGS
spec: ERRORS
spec-git: OK
sparse: ERRORS
linux-2.6.16.62-i686: WARNINGS
linux-2.6.17.14-i686: WARNINGS
linux-2.6.18.8-i686: WARNINGS
linux-2.6.19.7-i686: WARNINGS
linux-2.6.20.21-i686: WARNINGS
linux-2.6.21.7-i686: WARNINGS
linux-2.6.16.62-x86_64: WARNINGS
linux-2.6.17.14-x86_64: WARNINGS
linux-2.6.18.8-x86_64: WARNINGS
linux-2.6.19.7-x86_64: WARNINGS
linux-2.6.20.21-x86_64: WARNINGS
linux-2.6.21.7-x86_64: WARNINGS

Detailed results are available here:

http://www.xs4all.nl/~hverkuil/logs/Thursday.log

Full logs are available here:

http://www.xs4all.nl/~hverkuil/logs/Thursday.tar.bz2

The V4L-DVB specification from this daily build is here:

http://www.xs4all.nl/~hverkuil/spec/media.html
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [GIT PATCHES FOR 2.6.35] - Adding OMAP2/3 V4l2 display driver

2010-04-30 Thread Karicheri, Muralidharan
Vaibhav,

Thanks for clarifying

Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
phone: 301-407-9583
email: m-kariche...@ti.com

-Original Message-
From: Hiremath, Vaibhav
Sent: Thursday, April 29, 2010 1:33 AM
To: Mauro Carvalho Chehab; Muralidharan Karicheri
Cc: linux-media@vger.kernel.org; Hans Verkuil; Karicheri, Muralidharan
Subject: RE: [GIT PATCHES FOR 2.6.35] - Adding OMAP2/3 V4l2 display driver


 -Original Message-
 From: Mauro Carvalho Chehab [mailto:mche...@infradead.org]
 Sent: Thursday, April 29, 2010 9:31 AM
 To: Muralidharan Karicheri
 Cc: linux-media@vger.kernel.org; Hiremath, Vaibhav; Hans Verkuil;
Karicheri,
 Muralidharan
 Subject: Re: [GIT PATCHES FOR 2.6.35] - Adding OMAP2/3 V4l2 display
driver

 Muralidharan Karicheri wrote:
  Hi Mauro,
 
  Please pull from:-
 
  The following changes since commit
 184b7c85f31583632ad00c062a295b622759eef3:
Mauro Carvalho Chehab (1):
  ir-core: Fix the delete logic
 
  are available in the git repository at:
 
git://linuxtv.org/mkaricheri/vpfe-vpbe-video.git for_upstream_04_11
 
  Vaibhav Hiremath (2):
V4L2: Add support for OMAP2/3 V4L2 display driver on top of DSS2
omap_vout:V4L2 Display: Changed enum return type to int
 
   drivers/media/video/Kconfig |2 +
   drivers/media/video/Makefile|2 +
   drivers/media/video/omap/Kconfig|   11 +
   drivers/media/video/omap/Makefile   |7 +
   drivers/media/video/omap/omap_vout.c| 2643
 +++
   drivers/media/video/omap/omap_voutdef.h |  147 ++
   drivers/media/video/omap/omap_voutlib.c |  293 
   drivers/media/video/omap/omap_voutlib.h |   34 +
   8 files changed, 3139 insertions(+), 0 deletions(-)
   create mode 100644 drivers/media/video/omap/Kconfig
   create mode 100644 drivers/media/video/omap/Makefile
   create mode 100644 drivers/media/video/omap/omap_vout.c
   create mode 100644 drivers/media/video/omap/omap_voutdef.h
   create mode 100644 drivers/media/video/omap/omap_voutlib.c
   create mode 100644 drivers/media/video/omap/omap_voutlib.h
 

 Applied.
[Hiremath, Vaibhav] Missed to say Thanks. Cleanup patches and enhancement
will follow now on top of this.

Thanks,
Vaibhav

 Yet, I didn't like to see all those memory allocations for userprt
 inside
 the driver. IMO, it would be better placed inside the videobuf code.

 --

 Cheers,
 Mauro
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[GIT PATCHES FOR 2.6.35] Updates for the uvcvideo driver

2010-04-30 Thread Laurent Pinchart
The following changes since commit b88a1e83c9bfa5afbe1dd7481ea15fbea5ad9e55:
  Hans Verkuil (1):
V4L/DVB: v4l spec: document new events

are available in the git repository at:

  git://linuxtv.org/pinchartl/uvcvideo.git uvcvideo

Laurent Pinchart (3):
  uvcvideo: Add support for V4L2_PIX_FMT_Y16
  uvcvideo: Flag relative controls as write-only
  uvcvideo: Prevent division by 0 when control step value is 0

 drivers/media/video/uvc/uvc_ctrl.c   |   30 ++
 drivers/media/video/uvc/uvc_driver.c |7 ++-
 drivers/media/video/uvc/uvcvideo.h   |4 +++-
 3 files changed, 27 insertions(+), 14 deletions(-)

-- 
Regards,

Laurent Pinchart
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Post DSO scan file for Aberdare

2010-04-30 Thread Christoph Pfister
2010/4/29 Mike m...@redtux.org.uk:
 On Thu, 2010-04-29 at 19:48 +0200, Christoph Pfister wrote:
 2010/3/9 Mike m...@redtux.org.uk:
  Please see attached scan file for uk-Aberdare if anyone finds it useful

 Hmm, I'm not sure whether you're the guy who also sent this
 (different) update:
 http://www.mail-archive.com/linux-media@vger.kernel.org/msg17569.html

 Can you enlighten me please?

 Thanks,

 Christoph

 Yep the first file was for DSO stage 1 , and the second was for full
 switchover.

 Here Switchover was
 Part 1 3/3/2010
 Part 2 31/3/2010

 Obviously now full switchover has taken place the first file is u/s as
 is is the old scan file

Ok.

Christoph
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[OT] preferred video apps?

2010-04-30 Thread Randy Dunlap
Hi,

Sorry for a non-kernel question, but I'd like to get some suggestions
on video recording and editing software, please.

If it matters, this is mostly for recording  editing sports events (matches).

Reply privately if you prefer ...

thanks,
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[PATCH 0/3] TI WL1273 FM Radio Driver v2.

2010-04-30 Thread Matti J. Aaltonen
Hello.

I've implemented most of the changes proposed on the previous review round. 
There are some things to be done in the RDS handling...

I've left the region handling as it was because neither of the chip's
regions cover the complete range. Japan is from 76 - 90MHz and
Europe/US is 87.5 to 108 MHz.

Some of the private IOCTL were not necessary because corresponding standardized
controls already exist. And for setting the audio mode to digital or analog
I created an ALSA control because that's an audio thing anyway. 

A couple of private IOCTLs are still there: 

1. WL1273_CID_FM_REGION for setting the region. This may not be a good
candidate for standardization as the region control shouldn't exist 
in the kernel in general...

2. WL1273_CID_FM_SEEK_SPACING: defines what resolution is used when scanning 
automatically for stations (50KHz, 100KHz or 200KHz). This could be
useful in genaral. Could this be a field in the v4l2_hw_freq_seek struct?

3. WL1273_CID_FM_RDS_CTRL for turning on and off the RDS reception / 
transmission. To me this seems like a useful standard control...

4. WL1273_CID_SEARCH_LVL for setting the threshold level when detecting radio
channels when doing automatic scan. This could be useful for fine tuning
because automatic  scanning seems to be kind of problematic... This could also
be a field in the v4l2_hw_freq_seek struct?

5. WL1273_CID_FM_RADIO_MODE: Now the radio has the following modes: off, 
suspend, rx and tx. It probably would be better to separate the powering 
state (off, on, suspend) from the FM radio state (rx, tx)... 

Could the VIDIOC_S_MODULATOR and VIDIOC_S_TUNER IOCTLs be used for setting the
TX/RX mode?

Now there already exits a class for fm transmitters: V4L2_CTRL_CLASS_FM_TX.
Should a corresponding class be created for FM tuners?

B.R.
Matti A.

Matti J. Aaltonen (3):
  MFD: WL1273 FM Radio: MFD driver for the FM radio.
  WL1273 FM Radio: Digital audio codec.
  V4L2: WL1273 FM Radio: Controls for the FM radio.

 drivers/media/radio/Kconfig|   15 +
 drivers/media/radio/Makefile   |1 +
 drivers/media/radio/radio-wl1273.c | 1849 
 drivers/mfd/Kconfig|6 +
 drivers/mfd/Makefile   |2 +
 drivers/mfd/wl1273-core.c  |  609 
 include/linux/mfd/wl1273-core.h|  323 +++
 sound/soc/codecs/Kconfig   |6 +
 sound/soc/codecs/Makefile  |2 +
 sound/soc/codecs/wl1273.c  |  587 
 sound/soc/codecs/wl1273.h  |   40 +
 11 files changed, 3440 insertions(+), 0 deletions(-)
 create mode 100644 drivers/media/radio/radio-wl1273.c
 create mode 100644 drivers/mfd/wl1273-core.c
 create mode 100644 include/linux/mfd/wl1273-core.h
 create mode 100644 sound/soc/codecs/wl1273.c
 create mode 100644 sound/soc/codecs/wl1273.h

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [GIT PATCHES FOR 2.6.35] - Adding OMAP2/3 V4l2 display driver

2010-04-30 Thread Hiremath, Vaibhav

 -Original Message-
 From: Mauro Carvalho Chehab [mailto:mche...@infradead.org]
 Sent: Thursday, April 29, 2010 9:31 AM
 To: Muralidharan Karicheri
 Cc: linux-media@vger.kernel.org; Hiremath, Vaibhav; Hans Verkuil; Karicheri,
 Muralidharan
 Subject: Re: [GIT PATCHES FOR 2.6.35] - Adding OMAP2/3 V4l2 display driver
 
 Muralidharan Karicheri wrote:
  Hi Mauro,
 
  Please pull from:-
 
  The following changes since commit
 184b7c85f31583632ad00c062a295b622759eef3:
Mauro Carvalho Chehab (1):
  ir-core: Fix the delete logic
 
  are available in the git repository at:
 
git://linuxtv.org/mkaricheri/vpfe-vpbe-video.git for_upstream_04_11
 
  Vaibhav Hiremath (2):
V4L2: Add support for OMAP2/3 V4L2 display driver on top of DSS2
omap_vout:V4L2 Display: Changed enum return type to int
 
   drivers/media/video/Kconfig |2 +
   drivers/media/video/Makefile|2 +
   drivers/media/video/omap/Kconfig|   11 +
   drivers/media/video/omap/Makefile   |7 +
   drivers/media/video/omap/omap_vout.c| 2643
 +++
   drivers/media/video/omap/omap_voutdef.h |  147 ++
   drivers/media/video/omap/omap_voutlib.c |  293 
   drivers/media/video/omap/omap_voutlib.h |   34 +
   8 files changed, 3139 insertions(+), 0 deletions(-)
   create mode 100644 drivers/media/video/omap/Kconfig
   create mode 100644 drivers/media/video/omap/Makefile
   create mode 100644 drivers/media/video/omap/omap_vout.c
   create mode 100644 drivers/media/video/omap/omap_voutdef.h
   create mode 100644 drivers/media/video/omap/omap_voutlib.c
   create mode 100644 drivers/media/video/omap/omap_voutlib.h
 
 
 Applied. Yet, I didn't like to see all those memory allocations for userprt
 inside
 the driver. IMO, it would be better placed inside the videobuf code.
 
[Hiremath, Vaibhav] Mauro,

The OMAP is a really different device in terms of how the features are 
supported; let's take an example of rotation here,


Rotation is supported by another separate hardware module called VRFB (Virtual 
rotation FB) and there are some constraints on how you can use it, for example, 
the line length (pitch) must be 2048. Also VRFB has 12 contexts only and shared 
all over system (V4L2 display and Fbdev driver) so we should be using it 
efficiently.

Now as an application user I wouldn't want to consider this constraint and 
allocate this much huge buffer although we are not using it. Also most of the 
cases buffers come from other modules like, codes, DSP side application.

So the approach we took here is, we are limiting user application to use 4 
buffers only in case of rotation enabled. And differentiating user and VRFB 
buffers, so that user doesn't have to care about all VRFB related constraints 
here. Internally system DMA copies user buffer to VRFB buffers.

That's where we required buffer allocation which can not be generic.

Thanks,
Vaibhav

 --
 
 Cheers,
 Mauro
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [RFC 0/2] UVC gadget driver

2010-04-30 Thread Laurent Pinchart
Hi Greg,

On Thursday 29 April 2010 09:32:10 Greg KH wrote:
 On Thu, Apr 29, 2010 at 09:14:03AM +0200, Laurent Pinchart wrote:
  On Thursday 29 April 2010 05:41:11 Greg KH wrote:
   On Thu, Apr 29, 2010 at 12:52:57AM +0200, Laurent Pinchart wrote:
Hi everybody,

Here's a new version of the UVC gadget driver I posted on the list
some time ago, rebased on 2.6.34-rc5.

The private events API has been replaced by the new V4L2 events API
that will be available in 2.6.34 (the code is already available in
the v4l-dvb tree on linuxtv.org, and should be pushed to
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-next.git
very soon).

Further testing of the changes related to the events API is required
(this is planned for the next few days). As it seems to be the UVC
gadget driver season (Robert Lukassen posted his own implementation -
having a different goal - two days ago)
   
   What are the different goals here?  Shouldn't there just be only one
   way to implement this, or am I missing something?
  
  Both drivers act as webcams. Robert's version exports the local frame
  buffer through USB, making the webcam capture what's displayed on the
  device. My version exposes a V4L2 interface to userspace, allowing an
  application on the device to send whatever it wants over USB (for
  instance frames captured from a sensor, making the device a real
  camera).
 
 Ah.  So your's has the advantage of being able to do what his does as
 well, right?

I think so (although I'm not sure if a userspace application can capture the 
content of the frame buffer on sync events).

, I thought I'd post the patch as an RFC. I'd like the UVC function
driver to make it to 2.6.35, comments are more than welcome.
   
   It needs to get into my tree _now_ if you are wanting it in .35
   Just fyi.
  
  Does now mean today, or before next week ?
 
 Before next week would be good, as soon as possible is best.

I'd like to test the events API changes some more. I'll have time to do this 
before next week.

-- 
Regards,

Laurent Pinchart
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [GIT PATCHES FOR 2.6.35] - Adding OMAP2/3 V4l2 display driver

2010-04-30 Thread Mauro Carvalho Chehab
Muralidharan Karicheri wrote:
 Hi Mauro,
 
 Please pull from:-
 
 The following changes since commit 184b7c85f31583632ad00c062a295b622759eef3:
   Mauro Carvalho Chehab (1):
 ir-core: Fix the delete logic
 
 are available in the git repository at:
 
   git://linuxtv.org/mkaricheri/vpfe-vpbe-video.git for_upstream_04_11
 
 Vaibhav Hiremath (2):
   V4L2: Add support for OMAP2/3 V4L2 display driver on top of DSS2
   omap_vout:V4L2 Display: Changed enum return type to int
 
  drivers/media/video/Kconfig |2 +
  drivers/media/video/Makefile|2 +
  drivers/media/video/omap/Kconfig|   11 +
  drivers/media/video/omap/Makefile   |7 +
  drivers/media/video/omap/omap_vout.c| 2643 
 +++
  drivers/media/video/omap/omap_voutdef.h |  147 ++
  drivers/media/video/omap/omap_voutlib.c |  293 
  drivers/media/video/omap/omap_voutlib.h |   34 +
  8 files changed, 3139 insertions(+), 0 deletions(-)
  create mode 100644 drivers/media/video/omap/Kconfig
  create mode 100644 drivers/media/video/omap/Makefile
  create mode 100644 drivers/media/video/omap/omap_vout.c
  create mode 100644 drivers/media/video/omap/omap_voutdef.h
  create mode 100644 drivers/media/video/omap/omap_voutlib.c
  create mode 100644 drivers/media/video/omap/omap_voutlib.h
 

Applied. Yet, I didn't like to see all those memory allocations for userprt 
inside
the driver. IMO, it would be better placed inside the videobuf code.

-- 

Cheers,
Mauro
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: ATMEL camera interface

2010-04-30 Thread Guennadi Liakhovetski
Hi Sedji

On Thu, 29 Apr 2010, Sedji Gaouaou wrote:

 Hi,
 
 I need to re-work my driver so I could commit it to the community.
 Is there a git tree that I can use?

Nice to hear that! As far as soc-camera is concerned, the present APIs are 
pretty stable. Just use the Linus' git tree, or, if you like, you can use 
the v4l-dvb git tree at git://linuxtv.org/v4l-dvb.git. In fact, you don't 
have to use the soc-camera API these days, you can just write a complete 
v4l2-device driver, using the v4l2-subdev API to interface to video 
clients (sensors, decoders, etc.) However, you can still write your driver 
as an soc-camera host driver, which would make your task a bit easier at 
the cost of some reduced flexibility, it's up to you to decide.

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [RFC 0/2] UVC gadget driver

2010-04-30 Thread Greg KH
On Thu, Apr 29, 2010 at 09:14:03AM +0200, Laurent Pinchart wrote:
 Hi Greg,
 
 On Thursday 29 April 2010 05:41:11 Greg KH wrote:
  On Thu, Apr 29, 2010 at 12:52:57AM +0200, Laurent Pinchart wrote:
   Hi everybody,
   
   Here's a new version of the UVC gadget driver I posted on the list some
   time ago, rebased on 2.6.34-rc5.
   
   The private events API has been replaced by the new V4L2 events API that
   will be available in 2.6.34 (the code is already available in the
   v4l-dvb tree on linuxtv.org, and should be pushed to
   git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-next.git very
   soon).
   
   Further testing of the changes related to the events API is required
   (this is planned for the next few days). As it seems to be the UVC
   gadget driver season (Robert Lukassen posted his own implementation -
   having a different goal - two days ago)
  
  What are the different goals here?  Shouldn't there just be only one way
  to implement this, or am I missing something?
 
 Both drivers act as webcams. Robert's version exports the local frame 
 buffer 
 through USB, making the webcam capture what's displayed on the device. My 
 version exposes a V4L2 interface to userspace, allowing an application on the 
 device to send whatever it wants over USB (for instance frames captured from 
 a 
 sensor, making the device a real camera).

Ah.  So your's has the advantage of being able to do what his does as
well, right?

   , I thought I'd post the patch as an RFC. I'd like the UVC function
   driver to make it to 2.6.35, comments are more than welcome.
  
  It needs to get into my tree _now_ if you are wanting it in .35
  Just fyi.
 
 Does now mean today, or before next week ?

Before next week would be good, as soon as possible is best.

thanks,

greg k-h
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH] TT S2-1600 allow more current for diseqc

2010-04-30 Thread André Weidemann

Hi Hermann,
On 30.04.2010 02:31, hermann pitton wrote:


Hi,

Am Mittwoch, den 28.04.2010, 17:13 +0400 schrieb Manu Abraham:

On Wed, Apr 28, 2010 at 12:33 PM, Guy Martingms...@tuxicoman.be  wrote:

On Wed, 28 Apr 2010 09:45:39 +0200
André Weidemannandre.weidem...@web.de  wrote:


I advise not to pull this change into the kernel sources.
The card has only been testet with the a maximum current of 515mA.
Anything above is outside the specification for this card.



I'm currently running two of these cards in the same box with this
patch.
Actually, later on I've even set curlim = SEC_CURRENT_LIM_OFF because
sometimes diseqc wasn't working fine and that seemed to solve the
problem.


I would advise to not do this: since disabling current limiting etc
will cause a large problem in the case of a short circuit thereby no
protection to the hardware. In such an event, it could probably damage
the tracks carrying power on the card as well as the tracks on the
motherboard, and in some cases the gold finches themselves and or the
PCI connector.

Generally, there are only a few devices capable of sourcing  0.5A, So
I wonder 

Regards,
Manu


for the few devices I do have, you seem to be for sure right.

All the Creatix stuff drawing up to 900mA on a potentially dual isl6405
has direct voltage from the PSU over an extra floppy connector.

Max. 500mA should be sufficient with a DiSEqC 1.2 compliant rotor.
Nothing else should come above that limit.

I wonder, if someone close in reading specs just now, can tell if 900mA
can be sufficient for two rotors ;)

Andre, BTW, assuming you still have a CTX944 (md8800 Quad), can you
measure if the 16be:0008 device really does switch between 13 and 18V.


You seem to mistake me for someone else. I do not have a CTX944 and 
never had.


Regards
 André
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


RE: [GIT PATCHES FOR 2.6.35] - Adding OMAP2/3 V4l2 display driver

2010-04-30 Thread Hiremath, Vaibhav

 -Original Message-
 From: Mauro Carvalho Chehab [mailto:mche...@infradead.org]
 Sent: Thursday, April 29, 2010 9:31 AM
 To: Muralidharan Karicheri
 Cc: linux-media@vger.kernel.org; Hiremath, Vaibhav; Hans Verkuil; Karicheri,
 Muralidharan
 Subject: Re: [GIT PATCHES FOR 2.6.35] - Adding OMAP2/3 V4l2 display driver
 
 Muralidharan Karicheri wrote:
  Hi Mauro,
 
  Please pull from:-
 
  The following changes since commit
 184b7c85f31583632ad00c062a295b622759eef3:
Mauro Carvalho Chehab (1):
  ir-core: Fix the delete logic
 
  are available in the git repository at:
 
git://linuxtv.org/mkaricheri/vpfe-vpbe-video.git for_upstream_04_11
 
  Vaibhav Hiremath (2):
V4L2: Add support for OMAP2/3 V4L2 display driver on top of DSS2
omap_vout:V4L2 Display: Changed enum return type to int
 
   drivers/media/video/Kconfig |2 +
   drivers/media/video/Makefile|2 +
   drivers/media/video/omap/Kconfig|   11 +
   drivers/media/video/omap/Makefile   |7 +
   drivers/media/video/omap/omap_vout.c| 2643
 +++
   drivers/media/video/omap/omap_voutdef.h |  147 ++
   drivers/media/video/omap/omap_voutlib.c |  293 
   drivers/media/video/omap/omap_voutlib.h |   34 +
   8 files changed, 3139 insertions(+), 0 deletions(-)
   create mode 100644 drivers/media/video/omap/Kconfig
   create mode 100644 drivers/media/video/omap/Makefile
   create mode 100644 drivers/media/video/omap/omap_vout.c
   create mode 100644 drivers/media/video/omap/omap_voutdef.h
   create mode 100644 drivers/media/video/omap/omap_voutlib.c
   create mode 100644 drivers/media/video/omap/omap_voutlib.h
 
 
 Applied. 
[Hiremath, Vaibhav] Missed to say Thanks. Cleanup patches and enhancement will 
follow now on top of this.

Thanks,
Vaibhav

 Yet, I didn't like to see all those memory allocations for userprt
 inside
 the driver. IMO, it would be better placed inside the videobuf code.
 
 --
 
 Cheers,
 Mauro
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [linux-dvb] Update for es-Alfabia scan file

2010-04-30 Thread Christoph Pfister
2010/3/5 Jesús Jiménez jesjime...@gmail.com:
 Hi everyone!

 I've update the es-Alfabia scan file that comes with my distro (Ubuntu
 Karmic) to reflect new channels that appeared recently.

 Hope it can be updated in future releases of dvb-apps.

Updated, thanks!

 Greetings and thanks for your great work!
 --
 Jesús Jiménez
 jesjime...@gmail.com

Christoph
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[ANNOUNCEMENT] Media controller tree updated

2010-04-30 Thread Laurent Pinchart
Hi everybody,

The next version of the media controller patches is available in git at

http://git.linuxtv.org/pinchartl/v4l-dvb-media.git

To avoid putting too much pressure on the linuxtv.org git server, please make 
sure you reference an existing mainline Linux git tree when cloning v4l-dvb-
media (see the --reference option to git-clone).

Beside the media controller core, the tree contains a uvcvideo driver ported 
to the media controller. If you want to test the media controller code with 
the OMAP3 ISP driver, you can check out the devel branch in the 
http://gitorious.org/omap3camera/mainline/ tree instead.

WARNING: Don't unplug the device or unload the driver while holding a 
/dev/media or /dev/subdev device open. This problem will be fixed in a future 
release.

-- 
Regards,

Laurent Pinchart
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [RFC 0/2] UVC gadget driver

2010-04-30 Thread Laurent Pinchart
Hi Greg,

On Thursday 29 April 2010 05:41:11 Greg KH wrote:
 On Thu, Apr 29, 2010 at 12:52:57AM +0200, Laurent Pinchart wrote:
  Hi everybody,
  
  Here's a new version of the UVC gadget driver I posted on the list some
  time ago, rebased on 2.6.34-rc5.
  
  The private events API has been replaced by the new V4L2 events API that
  will be available in 2.6.34 (the code is already available in the
  v4l-dvb tree on linuxtv.org, and should be pushed to
  git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-next.git very
  soon).
  
  Further testing of the changes related to the events API is required
  (this is planned for the next few days). As it seems to be the UVC
  gadget driver season (Robert Lukassen posted his own implementation -
  having a different goal - two days ago)
 
 What are the different goals here?  Shouldn't there just be only one way
 to implement this, or am I missing something?

Both drivers act as webcams. Robert's version exports the local frame buffer 
through USB, making the webcam capture what's displayed on the device. My 
version exposes a V4L2 interface to userspace, allowing an application on the 
device to send whatever it wants over USB (for instance frames captured from a 
sensor, making the device a real camera).

  , I thought I'd post the patch as an RFC. I'd like the UVC function
  driver to make it to 2.6.35, comments are more than welcome.
 
 It needs to get into my tree _now_ if you are wanting it in .35
 Just fyi.

Does now mean today, or before next week ?

-- 
Regards,

Laurent Pinchart
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH 0/5] Pushdown bkl from v4l ioctls

2010-04-30 Thread Laurent Pinchart
Hi Hans,

On Thursday 29 April 2010 08:44:29 Hans Verkuil wrote:
 On Thursday 29 April 2010 05:42:39 Frederic Weisbecker wrote:
  Hi,
  
  Linus suggested to rename struct v4l2_file_operations::ioctl
  into bkl_ioctl to eventually get something greppable and make
  its background explicit.
  
  While at it I thought it could be a good idea to just pushdown
  the bkl to every v4l drivers that have an .ioctl, so that we
  actually remove struct v4l2_file_operations::ioctl for good.
  
  It passed make allyesconfig on sparc.
  Please tell me what you think.
 
 I much prefer to keep the bkl inside the v4l2 core. One reason is that I
 think that we can replace the bkl in the core with a mutex. Still not
 ideal of course, so the next step will be to implement proper locking in
 each driver. For this some additional v4l infrastructure work needs to be
 done. I couldn't proceed with that until the v4l events API patches went
 in, and that happened yesterday.
 
 So from my point of view the timeline is this:
 
 1) I do the infrastructure work this weekend. This will make it much easier
 to convert drivers to do proper locking. And it will also simplify
 v4l2_priority handling, so I'm killing two birds with one stone :-)
 
 2) Wait until Arnd's patch gets merged that pushes the bkl down to
 v4l2-dev.c
 
 3) Investigate what needs to be done to replace the bkl with a v4l2-dev.c
 global mutex. Those drivers that call the bkl themselves should probably be
 converted to do proper locking, but there are only about 14 drivers that do
 this. The other 60 or so drivers should work fine if a v4l2-dev global lock
 is used. At this point the bkl is effectively removed from the v4l
 subsystem.
 
 4) Work on the remaining 60 drivers to do proper locking and get rid of the
 v4l2-dev global lock. This is probably less work than it sounds.
 
 Since your patch moves everything down to the driver level it will actually
 make this work harder rather than easier. And it touches almost all drivers
 as well.

Every driver will need to be carefully checked to make sure the BKL can be 
replaced by a v4l2-dev global mutex. Why would it be more difficult to do so 
if the BKL is pushed down to the drivers ?

-- 
Regards,

Laurent Pinchart
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Scan-file for uk-Aberdare

2010-04-30 Thread Christoph Pfister
2010/4/8 Mike Martin redt...@googlemail.com:
 Attached is a working scan file for uk-Aberdare post switchover

Updated, thanks!

Christoph
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [linux-dvb] Debian Bug#564204: dvb-apps: fr-Nantes should have an added offset of 167000 for each value

2010-04-30 Thread Christoph Pfister
2010/4/2 Jeremy Guitton debo...@gmail.com:
snip
 Like #478020 for fr-Paris, fr-Nantes should have an added offset of
 167000 for each value. The file should look like that to be able to use
 scan on it:

 # Nantes - France
 # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
 T 498167000 8MHz 2/3 NONE QAM64 8k 1/32 NONE
 T 506167000 8MHz 2/3 NONE QAM64 8k 1/32 NONE
 T 522167000 8MHz 2/3 NONE QAM64 8k 1/32 NONE
 T 530167000 8MHz 2/3 NONE QAM64 8k 1/32 NONE
 T 658167000 8MHz 2/3 NONE QAM64 8k 1/32 NONE
 T 802167000 8MHz 2/3 NONE QAM64 8k 1/32 NONE
snip

Updated, thanks!

Christoph
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH] TT S2-1600 allow more current for diseqc

2010-04-30 Thread hermann pitton
Hi,

Am Mittwoch, den 28.04.2010, 17:13 +0400 schrieb Manu Abraham:
 On Wed, Apr 28, 2010 at 12:33 PM, Guy Martin gms...@tuxicoman.be wrote:
  On Wed, 28 Apr 2010 09:45:39 +0200
  André Weidemann andre.weidem...@web.de wrote:
 
  I advise not to pull this change into the kernel sources.
  The card has only been testet with the a maximum current of 515mA.
  Anything above is outside the specification for this card.
 
 
  I'm currently running two of these cards in the same box with this
  patch.
  Actually, later on I've even set curlim = SEC_CURRENT_LIM_OFF because
  sometimes diseqc wasn't working fine and that seemed to solve the
  problem.
 
 I would advise to not do this: since disabling current limiting etc
 will cause a large problem in the case of a short circuit thereby no
 protection to the hardware. In such an event, it could probably damage
 the tracks carrying power on the card as well as the tracks on the
 motherboard, and in some cases the gold finches themselves and or the
 PCI connector.
 
 Generally, there are only a few devices capable of sourcing  0.5A, So
 I wonder 
 
 Regards,
 Manu

for the few devices I do have, you seem to be for sure right.

All the Creatix stuff drawing up to 900mA on a potentially dual isl6405
has direct voltage from the PSU over an extra floppy connector.

Max. 500mA should be sufficient with a DiSEqC 1.2 compliant rotor.
Nothing else should come above that limit.

I wonder, if someone close in reading specs just now, can tell if 900mA
can be sufficient for two rotors ;)

Andre, BTW, assuming you still have a CTX944 (md8800 Quad), can you
measure if the 16be:0008 device really does switch between 13 and 18V.

Mine does not, but is also not in the original PC and the 0007 and 0008
devices are swapped on the PCI bus compared to that one.

Seen from my limited skills, it should not make any difference. So I
don't know why some did report all is fine on 0008 and I can only say it
hangs on 18V after init from the i2c capable 0007 device and on exit it
powers down properly, that's all, but _never_ is on 13V.

Be aware, that RF loopthrough between the two DVB-S tuners is
enabled ...

Thanks,
Hermann







--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH] Updated scan file for dvb-c/fi-Turku (dvb-apps)

2010-04-30 Thread Christoph Pfister
2010/4/7 Miika Vesti mi...@vesti.fi:
 Hello.

 Here is an updated scan file for dvb-c/fi-Turku.

 Source information for scan file:
 http://www.turunkaapelitv.fi/p9-taajuudet.html [html]
 http://www.turunkaapelitv.fi/files/Kanavalista-(3).pdf [pdf]

 Both documents are in Finnish but it should be easy to pick the relevant
 information and compare those values to the patch below.

 Signed-off-by: Miika Vesti mi...@vesti.fi
snip

Thanks, updated (next time please attach patch instead of inlining it).

Christoph
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH] tm6000: bugfix analog init for tm6010

2010-04-30 Thread Stefan Ringel
Am 28.04.2010 22:57, schrieb Stefan Ringel:
   
I have superseded this patch.

Stefan Ringel

-- 
Stefan Ringel stefan.rin...@arcor.de

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[GIT PATCHES FOR 2.6.35] gspca for_2.6.35

2010-04-30 Thread Jean-Francois Moine
Hi Mauro,

The following changes since commit
d3be2fab3a10b6c798a5f9970146d166d3345c37:

  V4L/DVB: gspca - zc3xx: Fix the gamma calculation from the contrast
  (2010-04-29 02:44:55 -0300)

are available in the git repository at:
  git://linuxtv.org/jfrancois/gspca.git for_2.6.35

Jean-François Moine (1):
  gspca - main: Convert wMaxPacketSize from little endian 16 to cpu.

 drivers/media/video/gspca/gspca.c |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

Thanks.

-- 
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef |   http://moinejf.free.fr/
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[PATCH] tm6000: bugfix analog init for tm6010

2010-04-30 Thread stefan . ringel
From: Stefan Ringel stefan.rin...@arcor.de

- change values in function tm6000_set_fourcc_format
- disable digital source
- add vbi and audio init

Signed-off-by: Stefan Ringel stefan.rin...@arcor.de
---
 drivers/staging/tm6000/tm6000-core.c |   97 -
 1 files changed, 94 insertions(+), 3 deletions(-)

diff --git a/drivers/staging/tm6000/tm6000-core.c 
b/drivers/staging/tm6000/tm6000-core.c
index 0b4dc64..860553f 100644
--- a/drivers/staging/tm6000/tm6000-core.c
+++ b/drivers/staging/tm6000/tm6000-core.c
@@ -157,9 +157,9 @@ void tm6000_set_fourcc_format(struct tm6000_core *dev)
 {
if (dev-dev_type == TM6010) {
if (dev-fourcc == V4L2_PIX_FMT_UYVY)
-   tm6000_set_reg(dev, TM6010_REQ07_RC1_TRESHOLD, 0xfc);
+   tm6000_set_reg(dev, TM6010_REQ07_RC1_TRESHOLD, 0xd0);
else
-   tm6000_set_reg(dev, TM6010_REQ07_RC1_TRESHOLD, 0xfd);
+   tm6000_set_reg(dev, TM6010_REQ07_RC1_TRESHOLD, 0x90);
} else {
if (dev-fourcc == V4L2_PIX_FMT_UYVY)
tm6000_set_reg(dev, TM6010_REQ07_RC1_TRESHOLD, 0xd0);
@@ -177,7 +177,98 @@ int tm6000_init_analog_mode (struct tm6000_core *dev)
val = tm6000_get_reg(dev, TM6010_REQ07_RCC_ACTIVE_VIDEO_IF, 0);
val |= 0x60;
tm6000_set_reg(dev, TM6010_REQ07_RCC_ACTIVE_VIDEO_IF, val);
-   tm6000_set_reg(dev, TM6010_REQ07_RFE_POWER_DOWN, 0xcf);
+   val = tm6000_get_reg(dev,
+   TM6010_REQ07_RC0_ACTIVE_VIDEO_SOURCE, 0);
+   val = ~0x40;
+   tm6000_set_reg(dev, TM6010_REQ07_RC0_ACTIVE_VIDEO_SOURCE, val);
+
+   /* Init teletext */
+   tm6000_set_reg(dev, TM6010_REQ07_R3F_RESET, 0x01);
+   tm6000_set_reg(dev, TM6010_REQ07_R41_TELETEXT_VBI_CODE1, 0x27);
+   tm6000_set_reg(dev, TM6010_REQ07_R42_VBI_DATA_HIGH_LEVEL, 0x55);
+   tm6000_set_reg(dev, TM6010_REQ07_R43_VBI_DATA_TYPE_LINE7, 0x66);
+   tm6000_set_reg(dev, TM6010_REQ07_R44_VBI_DATA_TYPE_LINE8, 0x66);
+   tm6000_set_reg(dev, TM6010_REQ07_R45_VBI_DATA_TYPE_LINE9, 0x66);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R46_VBI_DATA_TYPE_LINE10, 0x66);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R47_VBI_DATA_TYPE_LINE11, 0x66);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R48_VBI_DATA_TYPE_LINE12, 0x66);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R49_VBI_DATA_TYPE_LINE13, 0x66);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R4A_VBI_DATA_TYPE_LINE14, 0x66);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R4B_VBI_DATA_TYPE_LINE15, 0x66);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R4C_VBI_DATA_TYPE_LINE16, 0x66);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R4D_VBI_DATA_TYPE_LINE17, 0x66);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R4E_VBI_DATA_TYPE_LINE18, 0x66);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R4F_VBI_DATA_TYPE_LINE19, 0x66);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R50_VBI_DATA_TYPE_LINE20, 0x66);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R51_VBI_DATA_TYPE_LINE21, 0x66);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R52_VBI_DATA_TYPE_LINE22, 0x66);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R53_VBI_DATA_TYPE_LINE23, 0x00);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R54_VBI_DATA_TYPE_RLINES, 0x00);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R55_VBI_LOOP_FILTER_GAIN, 0x01);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R56_VBI_LOOP_FILTER_I_GAIN, 0x00);
+   tm6000_set_reg(dev,
+   TM6010_REQ07_R57_VBI_LOOP_FILTER_P_GAIN, 0x02);
+   tm6000_set_reg(dev, TM6010_REQ07_R58_VBI_CAPTION_DTO1, 0x35);
+   tm6000_set_reg(dev, TM6010_REQ07_R59_VBI_CAPTION_DTO0, 0xa0);
+   tm6000_set_reg(dev, TM6010_REQ07_R5A_VBI_TELETEXT_DTO1, 0x11);
+   tm6000_set_reg(dev, TM6010_REQ07_R5B_VBI_TELETEXT_DTO0, 0x4c);
+   tm6000_set_reg(dev, TM6010_REQ07_R40_TELETEXT_VBI_CODE0, 0x01);
+   tm6000_set_reg(dev, TM6010_REQ07_R3F_RESET, 0x00);
+
+
+   /* Init audio */
+   tm6000_set_reg(dev, TM6010_REQ08_R01_A_INIT, 0x00);
+   tm6000_set_reg(dev, TM6010_REQ08_R02_A_FIX_GAIN_CTRL, 0x04);
+   tm6000_set_reg(dev, TM6010_REQ08_R03_A_AUTO_GAIN_CTRL, 0x00);
+   tm6000_set_reg(dev, TM6010_REQ08_R04_A_SIF_AMP_CTRL, 0xa0);
+   tm6000_set_reg(dev, 

Re: [Bug #15589] 2.6.34-rc1: Badness at fs/proc/generic.c:316

2010-04-30 Thread Stefan Lippers-Hollmann
Hi

On Friday 30 April 2010, Rafael J. Wysocki wrote:
 This message has been generated automatically as a part of a summary report
 of recent regressions.
 
 The following bug entry is on the current list of known regressions
 from 2.6.33.  Please verify if it still should be listed and let the tracking 
 team
 know (either way).
 
 
 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15589
 Subject   : 2.6.34-rc1: Badness at fs/proc/generic.c:316
 Submitter : Christian Kujau li...@nerdbynature.de
 Date  : 2010-03-13 23:53 (38 days old)
 Message-ID: alpine.deb.2.01.1003131544340.5...@bogon.housecafe.de
 References: http://marc.info/?l=linux-kernelm=126852442903680w=2

This also continues to be a problem with b2c2-flexcop and 2.6.34-rc5-git10:

[   10.119807] b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip 
loaded successfully
[   10.129183] flexcop-pci: will use the HW PID filter.
[   10.129187] flexcop-pci: card revision 2
[   10.129195] b2c2_flexcop_pci :06:01.0: PCI INT A - GSI 19 (level, low) 
- IRQ 19
[   10.129239] [ cut here ]
[   10.129244] WARNING: at 
/tmp/buildd/linux-sidux-2.6-2.6.34~rc5/debian/build/source_amd64_none/fs/proc/generic.c:317
 __xlate_proc_name+0xb5/0xd0()
[   10.129246] Hardware name: EP45-DS3
[   10.129247] name 'Technisat/B2C2 FlexCop II/IIb/III Digital TV PCI Driver'
[   10.129248] Modules linked in: b2c2_flexcop_pci(+) ath9k_common b2c2_flexcop 
v4l1_compat snd_timer radeon(+) dvb_core ar9170usb(+) ath9k_hw snd_seq_device 
ir_common tveeprom ttm v4l2_compat_ioctl32 snd drm_kms_helper ir_core ath 
mac80211 soundcore videobuf_dma_sg cx24123 drm i2c_i801 i2c_algo_bit 
snd_page_alloc videobuf_core cx24113 s5h1420 cfg80211 rfkill evdev i2c_core 
tpm_tis btcx_risc tpm led_class pcspkr tpm_bios rtc_cmos button rtc_core 
intel_agp rtc_lib processor ext4 mbcache jbd2 crc16 dm_mod sg sr_mod cdrom 
sd_mod usbhid hid uhci_hcd firewire_ohci firewire_core ahci r8169 ehci_hcd mii 
libata crc_itu_t scsi_mod thermal usbcore nls_base [last unloaded: 
scsi_wait_scan]
[   10.129279] Pid: 1124, comm: modprobe Not tainted 2.6.34-rc5-sidux-amd64 #1
[   10.129281] Call Trace:
[   10.129285]  [8104ba83] ? warn_slowpath_common+0x73/0xb0
[   10.129287]  [8104bb20] ? warn_slowpath_fmt+0x40/0x50
[   10.129290]  [8114f545] ? __xlate_proc_name+0xb5/0xd0
[   10.129292]  [8114fb2e] ? __proc_create+0x7e/0x150
[   10.129294]  [811504e7] ? proc_mkdir_mode+0x27/0x60
[   10.129297]  [8109fb55] ? register_handler_proc+0x115/0x130
[   10.129300]  [8109d4c1] ? __setup_irq+0x1d1/0x330
[   10.129303]  [a011b160] ? flexcop_pci_isr+0x0/0x190 
[b2c2_flexcop_pci]
[   10.129305]  [8109d735] ? request_threaded_irq+0x115/0x1b0
[   10.129308]  [a011b495] ? flexcop_pci_probe+0x1a5/0x330 
[b2c2_flexcop_pci]
[   10.129312]  [811ceef2] ? local_pci_probe+0x12/0x20
[   10.129314]  [811d02ca] ? pci_device_probe+0x10a/0x130
[   10.129317]  [8125cdda] ? driver_sysfs_add+0x5a/0x80
[   10.129320]  [8125cf03] ? driver_probe_device+0x93/0x190
[   10.129322]  [8125d093] ? __driver_attach+0x93/0xa0
[   10.129324]  [8125d000] ? __driver_attach+0x0/0xa0
[   10.129326]  [8125c638] ? bus_for_each_dev+0x58/0x80
[   10.129328]  [8125be70] ? bus_add_driver+0xb0/0x250
[   10.129330]  [8125d38a] ? driver_register+0x6a/0x130
[   10.129332]  [811d056c] ? __pci_register_driver+0x4c/0xc0
[   10.129335]  [a012e000] ? flexcop_pci_module_init+0x0/0x20 
[b2c2_flexcop_pci]
[   10.129338]  [81002044] ? do_one_initcall+0x34/0x1a0
[   10.129341]  [8107d15f] ? sys_init_module+0xdf/0x260
[   10.129344]  [81009f42] ? system_call_fastpath+0x16/0x1b
[   10.129345] ---[ end trace 370a62256537c67a ]---
[   10.134144] DVB: registering new adapter (FlexCop Digital TV device)
[   10.135610] b2c2-flexcop: MAC address = 00:d0:d7:0c:83:d6

Regards
Stefan Lippers-Hollmann
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: ir-Tehran initial scan file (DVB-T)

2010-04-30 Thread Christoph Pfister
2010/4/13 kamiar kanani kamiar.kan...@gmail.com:
 Hi

 Herewith attached is the initial scan file of Tehran @ Iran

Added, thanks!

 --
 Kamiar Kanani

Christoph
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[GIT PATCHES FOR 2.6.35] Updates for the uvcvideo driver

2010-04-30 Thread Laurent Pinchart
The following changes since commit b88a1e83c9bfa5afbe1dd7481ea15fbea5ad9e55:
  Hans Verkuil (1):
V4L/DVB: v4l spec: document new events

are available in the git repository at:

  git://linuxtv.org/pinchartl/uvcvideo.git uvcvideo

Laurent Pinchart (3):
  uvcvideo: Add support for V4L2_PIX_FMT_Y16
  uvcvideo: Flag relative controls as write-only
  uvcvideo: Prevent division by 0 when control step value is 0

 drivers/media/video/uvc/uvc_ctrl.c   |   30 ++
 drivers/media/video/uvc/uvc_driver.c |7 ++-
 drivers/media/video/uvc/uvcvideo.h   |4 +++-
 3 files changed, 27 insertions(+), 14 deletions(-)

-- 
Regards,

Laurent Pinchart
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[PATCH 2/3] WL1273 FM Radio: Digital audio codec.

2010-04-30 Thread Matti J. Aaltonen
The codec handles digital audio input to and output from the
WL1273 FM radio.

Signed-off-by: Matti J. Aaltonen matti.j.aalto...@nokia.com
---
 sound/soc/codecs/Kconfig  |6 +
 sound/soc/codecs/Makefile |2 +
 sound/soc/codecs/wl1273.c |  587 +
 sound/soc/codecs/wl1273.h |   40 +++
 4 files changed, 635 insertions(+), 0 deletions(-)
 create mode 100644 sound/soc/codecs/wl1273.c
 create mode 100644 sound/soc/codecs/wl1273.h

diff --git a/sound/soc/codecs/Kconfig b/sound/soc/codecs/Kconfig
index 52b005f..c4769f2 100644
--- a/sound/soc/codecs/Kconfig
+++ b/sound/soc/codecs/Kconfig
@@ -35,6 +35,7 @@ config SND_SOC_ALL_CODECS
select SND_SOC_TWL4030 if TWL4030_CORE
select SND_SOC_UDA134X
select SND_SOC_UDA1380 if I2C
+   select SND_SOC_WL1273 if I2C
select SND_SOC_WM8350 if MFD_WM8350
select SND_SOC_WM8400 if MFD_WM8400
select SND_SOC_WM8510 if SND_SOC_I2C_AND_SPI
@@ -161,6 +162,11 @@ config SND_SOC_UDA134X
 config SND_SOC_UDA1380
 tristate
 
+config SND_SOC_WL1273
+   tristate
+   select WL1273_CORE
+   default n
+
 config SND_SOC_WM8350
tristate
 
diff --git a/sound/soc/codecs/Makefile b/sound/soc/codecs/Makefile
index dbaecb1..2a7c564 100644
--- a/sound/soc/codecs/Makefile
+++ b/sound/soc/codecs/Makefile
@@ -22,6 +22,7 @@ snd-soc-tlv320dac33-objs := tlv320dac33.o
 snd-soc-twl4030-objs := twl4030.o
 snd-soc-uda134x-objs := uda134x.o
 snd-soc-uda1380-objs := uda1380.o
+snd-soc-wl1273-objs := wl1273.o
 snd-soc-wm8350-objs := wm8350.o
 snd-soc-wm8400-objs := wm8400.o
 snd-soc-wm8510-objs := wm8510.o
@@ -78,6 +79,7 @@ obj-$(CONFIG_SND_SOC_TLV320DAC33) += snd-soc-tlv320dac33.o
 obj-$(CONFIG_SND_SOC_TWL4030)  += snd-soc-twl4030.o
 obj-$(CONFIG_SND_SOC_UDA134X)  += snd-soc-uda134x.o
 obj-$(CONFIG_SND_SOC_UDA1380)  += snd-soc-uda1380.o
+obj-$(CONFIG_SND_SOC_WL1273)   += snd-soc-wl1273.o
 obj-$(CONFIG_SND_SOC_WM8350)   += snd-soc-wm8350.o
 obj-$(CONFIG_SND_SOC_WM8400)   += snd-soc-wm8400.o
 obj-$(CONFIG_SND_SOC_WM8510)   += snd-soc-wm8510.o
diff --git a/sound/soc/codecs/wl1273.c b/sound/soc/codecs/wl1273.c
new file mode 100644
index 000..ea2d382
--- /dev/null
+++ b/sound/soc/codecs/wl1273.c
@@ -0,0 +1,587 @@
+/*
+ * ALSA SoC WL1273 codec driver
+ *
+ * Author:  Matti Aaltonen, matti.j.aalto...@nokia.com
+ *
+ * Copyright:   (C) 2010 Nokia Corporation
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License
+ * version 2 as published by the Free Software Foundation.
+ *
+ * This program is distributed in the hope that it will be useful, but
+ * WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+ * General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
+ * 02110-1301 USA
+ *
+ */
+
+#undef DEBUG
+
+#include linux/mfd/wl1273-core.h
+#include linux/module.h
+#include sound/pcm.h
+#include sound/pcm_params.h
+#include sound/soc.h
+#include sound/soc-dapm.h
+#include sound/initval.h
+
+#include wl1273.h
+
+static int snd_wl1273_fm_set_i2s_mode(struct wl1273_core *core,
+ int rate, int width)
+{
+   struct device *dev = core-i2c_dev-dev;
+   int r = 0;
+   u16 mode;
+
+   dev_dbg(dev, rate: %d\n, rate);
+   dev_dbg(dev, width: %d\n, width);
+
+   mutex_lock(core-lock);
+
+   mode = core-i2s_mode  ~WL1273_IS2_WIDTH  ~WL1273_IS2_RATE;
+
+   switch (rate) {
+   case 48000:
+   mode |= WL1273_IS2_RATE_48K;
+   break;
+   case 44100:
+   mode |= WL1273_IS2_RATE_44_1K;
+   break;
+   case 32000:
+   mode |= WL1273_IS2_RATE_32K;
+   break;
+   case 22050:
+   mode |= WL1273_IS2_RATE_22_05K;
+   break;
+   case 16000:
+   mode |= WL1273_IS2_RATE_16K;
+   break;
+   case 12000:
+   mode |= WL1273_IS2_RATE_12K;
+   break;
+   case 11025:
+   mode |= WL1273_IS2_RATE_11_025;
+   break;
+   case 8000:
+   mode |= WL1273_IS2_RATE_8K;
+   break;
+   default:
+   dev_err(dev, Sampling rate: %d not supported\n, rate);
+   r = -EINVAL;
+   goto out;
+   }
+
+   switch (width) {
+   case 16:
+   mode |= WL1273_IS2_WIDTH_32;
+   break;
+   case 20:
+   mode |= WL1273_IS2_WIDTH_40;
+   break;
+   case 24:
+   mode |= WL1273_IS2_WIDTH_48;
+   break;
+   case 25:
+   mode |= WL1273_IS2_WIDTH_50;
+   break;
+   case 30:
+  

Re: Post DSO scan file for Aberdare

2010-04-30 Thread Mike
On Thu, 2010-04-29 at 19:48 +0200, Christoph Pfister wrote:
 2010/3/9 Mike m...@redtux.org.uk:
  Please see attached scan file for uk-Aberdare if anyone finds it useful
 
 Hmm, I'm not sure whether you're the guy who also sent this
 (different) update:
 http://www.mail-archive.com/linux-media@vger.kernel.org/msg17569.html
 
 Can you enlighten me please?
 
 Thanks,
 
 Christoph

Yep the first file was for DSO stage 1 , and the second was for full
switchover.

Here Switchover was 
Part 1 3/3/2010
Part 2 31/3/2010

Obviously now full switchover has taken place the first file is u/s as
is is the old scan file

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[PATCH 1/3] MFD: WL1273 FM Radio: MFD driver for the FM radio.

2010-04-30 Thread Matti J. Aaltonen
This is a parent driver for two child drivers: the V4L2 driver and
the ALSA codec driver. The MFD part provides the I2C communication
to the device and a couple of functions that are called from both
children.

Signed-off-by: Matti J. Aaltonen matti.j.aalto...@nokia.com
---
 drivers/mfd/Kconfig |6 +
 drivers/mfd/Makefile|2 +
 drivers/mfd/wl1273-core.c   |  609 +++
 include/linux/mfd/wl1273-core.h |  323 +
 4 files changed, 940 insertions(+), 0 deletions(-)
 create mode 100644 drivers/mfd/wl1273-core.c
 create mode 100644 include/linux/mfd/wl1273-core.h

diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
index 413576a..c16d500 100644
--- a/drivers/mfd/Kconfig
+++ b/drivers/mfd/Kconfig
@@ -135,6 +135,12 @@ config TWL4030_CODEC
select MFD_CORE
default n
 
+config WL1273_CORE
+   tristate
+   depends on I2C
+   select MFD_CORE
+   default n
+
 config MFD_TMIO
bool
default n
diff --git a/drivers/mfd/Makefile b/drivers/mfd/Makefile
index 78295d6..46e611d 100644
--- a/drivers/mfd/Makefile
+++ b/drivers/mfd/Makefile
@@ -30,6 +30,8 @@ obj-$(CONFIG_TWL4030_CORE)+= twl-core.o twl4030-irq.o 
twl6030-irq.o
 obj-$(CONFIG_TWL4030_POWER)+= twl4030-power.o
 obj-$(CONFIG_TWL4030_CODEC)+= twl4030-codec.o
 
+obj-$(CONFIG_WL1273_CORE)  += wl1273-core.o
+
 obj-$(CONFIG_MFD_MC13783)  += mc13783-core.o
 
 obj-$(CONFIG_MFD_CORE) += mfd-core.o
diff --git a/drivers/mfd/wl1273-core.c b/drivers/mfd/wl1273-core.c
new file mode 100644
index 000..efe8039
--- /dev/null
+++ b/drivers/mfd/wl1273-core.c
@@ -0,0 +1,609 @@
+/*
+ * MFD driver for wl1273 FM radio and audio codec submodules.
+ *
+ * Author: Matti Aaltonen matti.j.aalto...@nokia.com
+ *
+ * Copyright:   (C) 2010 Nokia Corporation
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ *
+ * This program is distributed in the hope that it will be useful, but
+ * WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+ * General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
+ * 02110-1301 USA
+ *
+ */
+
+#undef DEBUG
+
+#include asm/unaligned.h
+#include linux/completion.h
+#include linux/delay.h
+#include linux/i2c.h
+#include linux/interrupt.h
+#include linux/module.h
+#include linux/types.h
+#include linux/kernel.h
+#include linux/fs.h
+#include linux/platform_device.h
+#include linux/mfd/core.h
+#include linux/mfd/wl1273-core.h
+#include media/v4l2-common.h
+
+#define DRIVER_DESC WL1273 FM Radio Core
+
+#define WL1273_IRQ_MASK (WL1273_FR_EVENT   |   \
+ WL1273_POW_ENB_EVENT)
+
+static const struct region_info regions[] = {
+   /* Japan */
+   {
+   .bottom_frequency   = 76000,
+   .top_frequency  = 9,
+   .region = 0,
+   },
+   /* USA  Europe */
+   {
+   .bottom_frequency   = 87500,
+   .top_frequency  = 108000,
+   .region = 1,
+   },
+};
+
+/*
+ * static unsigned char radio_region - Region
+ *
+ * The regions are 0=Japan, 1=USA-Europe. USA-Europe is the default.
+ */
+static unsigned char radio_region = 1;
+module_param(radio_region, byte, 0);
+MODULE_PARM_DESC(radio_region, Region: 0=Japan, 1=USA-Europe*);
+
+/*
+ * static unsigned int rds_buf - the number of RDS buffer blocks used.
+ *
+ * The default number is 100.
+ */
+static unsigned int rds_buf = 100;
+module_param(rds_buf, uint, 0);
+MODULE_PARM_DESC(rds_buf, RDS buffer entries: *100*);
+
+int wl1273_fm_read_reg(struct wl1273_core *core, u8 reg, u16 *value)
+{
+   struct i2c_client *client = core-i2c_dev;
+   u8 b[2];
+   int r;
+
+   r = i2c_smbus_read_i2c_block_data(client, reg, 2, b);
+   if (r != 2) {
+   dev_err(client-dev, %s: Read: %d fails.\n, __func__, reg);
+   return -EREMOTEIO;
+   }
+
+   *value = (u16)b[0]  8 | b[1];
+
+   return 0;
+}
+EXPORT_SYMBOL(wl1273_fm_read_reg);
+
+int wl1273_fm_write_cmd(struct wl1273_core *core, u8 cmd, u16 param)
+{
+   struct i2c_client *client = core-i2c_dev;
+   u8 buf[] = { (param  8)  0xff, param  0xff };
+   int r;
+
+   r = i2c_smbus_write_i2c_block_data(client, cmd, 2, buf);
+   if (r) {
+   dev_err(client-dev, %s: Cmd: %d fails.\n, __func__, cmd);
+   return r;
+   }
+
+   return 0;
+}
+EXPORT_SYMBOL(wl1273_fm_write_cmd);
+
+int wl1273_fm_write_data(struct wl1273_core *core, u8 *data, u16 

Re: [PATCH] DVB-T initial scan file for Israel (dvb-utils)

2010-04-30 Thread Christoph Pfister
2010/4/10 Shaul Kremer shau...@gmail.com:
snip
 Sounds good. Here:

 # HG changeset patch
 # User Shaul Kremer shau...@gmail.com
 # Date 1270911802 -10800
 # Node ID 9c2dabea9d1b63a75593b920d41159e7ba607747
 # Parent  7de0663facd92bbb9049aeeda3dcba9601228f30
 Added DVB-T initial tuning tables for Israel.

 diff -r 7de0663facd9 -r 9c2dabea9d1b util/scan/dvb-t/il-All
 --- /dev/null   Thu Jan 01 00:00:00 1970 +
 +++ b/util/scan/dvb-t/il-All    Sat Apr 10 18:03:22 2010 +0300
 @@ -0,0 +1,5 @@
 +# Israel, Israel Broadcasting Authority's transmitters
 +# Generated from list in http://www.iba.org.il/reception/
 +# T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
 +T 51400 8MHz 2/3 NONE QAM16 8k 1/4 NONE
 +T 53800 8MHz 2/3 NONE QAM16 8k 1/4 NONE

Applied, thanks (for the next time: please attach patch instead of inlining it).

Christoph
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[PATCH v2] IR/imon: add proper auto-repeat support

2010-04-30 Thread Jarod Wilson
Simplified from version 1, in that hacks heisted from ati_remote2.c
aren't actually necessary, the real fix for too many repeats was
from setting too long a timer release value (200ms) on repeats in
mce mode -- this patch drops the release timeout to 33ms, matching
the input subsystem default input_dev-rep[REP_PERIOD].

Signed-off-by: Jarod Wilson ja...@redhat.com
---
 drivers/media/IR/imon.c |   11 ++-
 1 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/drivers/media/IR/imon.c b/drivers/media/IR/imon.c
index b65c31a..09d4e44 100644
--- a/drivers/media/IR/imon.c
+++ b/drivers/media/IR/imon.c
@@ -146,7 +146,6 @@ struct imon_context {
 };
 
 #define TOUCH_TIMEOUT  (HZ/30)
-#define MCE_TIMEOUT_MS 200
 
 /* vfd character device file operations */
 static const struct file_operations vfd_fops = {
@@ -1394,6 +1393,8 @@ static int imon_parse_press_type(struct imon_context 
*ictx,
 unsigned char *buf, u8 ktype)
 {
int press_type = 0;
+   int rep_delay = ictx-idev-rep[REP_DELAY];
+   int rep_period = ictx-idev-rep[REP_PERIOD];
 
/* key release of 0x02XX key */
if (ictx-kc == KEY_RESERVED  buf[0] == 0x02  buf[3] == 0x00)
@@ -1418,12 +1419,12 @@ static int imon_parse_press_type(struct imon_context 
*ictx,
ictx-mce_toggle_bit = buf[2];
press_type = 1;
mod_timer(ictx-itimer,
- jiffies + msecs_to_jiffies(MCE_TIMEOUT_MS));
+ jiffies + msecs_to_jiffies(rep_delay));
/* repeat */
} else {
press_type = 2;
mod_timer(ictx-itimer,
- jiffies + msecs_to_jiffies(MCE_TIMEOUT_MS));
+ jiffies + msecs_to_jiffies(rep_period));
}
 
/* incoherent or irrelevant data */
@@ -1541,7 +1542,7 @@ static void imon_incoming_packet(struct imon_context 
*ictx,
do_gettimeofday(t);
msec = tv2int(t, prev_time);
prev_time = t;
-   if (msec  200)
+   if (msec  idev-rep[REP_DELAY])
return;
}
 
@@ -1686,7 +1687,7 @@ static struct input_dev *imon_init_idev(struct 
imon_context *ictx)
strlcat(ictx-phys_idev, /input0, sizeof(ictx-phys_idev));
idev-phys = ictx-phys_idev;
 
-   idev-evbit[0] = BIT_MASK(EV_KEY) | BIT_MASK(EV_REL);
+   idev-evbit[0] = BIT_MASK(EV_KEY) | BIT_MASK(EV_REP) | BIT_MASK(EV_REL);
 
idev-keybit[BIT_WORD(BTN_MOUSE)] =
BIT_MASK(BTN_LEFT) | BIT_MASK(BTN_RIGHT);

-- 
Jarod Wilson
ja...@redhat.com

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [linux-dvb] Correct error is channels.conf es-Sevilla

2010-04-30 Thread Christoph Pfister
2010/3/4 x2 x...@ya.com:
 Excuse send an error channels.conf 8K defective well capitalized and added 
 two mux that will soon be operational.

 Error:
 http://www.linuxtv.org/pipermail/linux-dvb/2010-February/032593.html

 # DVB-T Sevilla (Spain) by x2 15-Ago-2006  modificado 4 Marzo 2010
 # T freq bw fec_hi fec_lo mod transm-mode guard-interval hierarchy
 T 66600 8MHz 2/3 NONE QAM64 8k 1/4 NONE                  # C45
 T 73800 8MHz 2/3 NONE QAM64 8k 1/4 NONE                  # C54
 T 75400 8MHz 2/3 NONE QAM64 8k 1/4 NONE                  # C56
 T 76200 8MHz 2/3 NONE QAM64 8k 1/4 NONE                  # C57
 T 79400 8MHz 2/3 NONE QAM64 8k 1/4 NONE                  # C61
 T 83400 8MHz 2/3 NONE QAM64 8k 1/4 NONE                  # C66
 T 84200 8MHz 2/3 NONE QAM64 8k 1/4 NONE                  # C67
 T 85000 8MHz 2/3 NONE QAM64 8k 1/4 NONE                  # C68
 T 85800 8MHz 2/3 NONE QAM64 8k 1/4 NONE                  # C69

Updated, thanks!

 I am sending this to the wrong list please tell me where to send to be 
 updated.

 A greeting.

 --
 x2 x...@ya.com

Christoph
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[PATCH 3/3] V4L2: WL1273 FM Radio: Controls for the FM radio.

2010-04-30 Thread Matti J. Aaltonen
This file implements V4L2 controls for using the Texas Instruments
WL1273 FM Radio.

Signed-off-by: Matti J. Aaltonen matti.j.aalto...@nokia.com
---
 drivers/media/radio/Kconfig|   15 +
 drivers/media/radio/Makefile   |1 +
 drivers/media/radio/radio-wl1273.c | 1849 
 3 files changed, 1865 insertions(+), 0 deletions(-)
 create mode 100644 drivers/media/radio/radio-wl1273.c

diff --git a/drivers/media/radio/Kconfig b/drivers/media/radio/Kconfig
index 83567b8..209fd37 100644
--- a/drivers/media/radio/Kconfig
+++ b/drivers/media/radio/Kconfig
@@ -452,4 +452,19 @@ config RADIO_TIMBERDALE
  found behind the Timberdale FPGA on the Russellville board.
  Enabling this driver will automatically select the DSP and tuner.
 
+config RADIO_WL1273
+   tristate Texas Instruments WL1273 I2C FM Radio
+depends on I2C  VIDEO_V4L2  SND
+   select FW_LOADER
+   ---help---
+ Choose Y here if you have this FM radio chip.
+
+ In order to control your radio card, you will need to use programs
+ that are compatible with the Video For Linux 2 API.  Information on
+ this API and pointers to v4l2 programs may be found at
+ file:Documentation/video4linux/API.html.
+
+ To compile this driver as a module, choose M here: the
+ module will be called radio-wl1273.
+
 endif # RADIO_ADAPTERS
diff --git a/drivers/media/radio/Makefile b/drivers/media/radio/Makefile
index f615583..d297074 100644
--- a/drivers/media/radio/Makefile
+++ b/drivers/media/radio/Makefile
@@ -26,5 +26,6 @@ obj-$(CONFIG_RADIO_TEA5764) += radio-tea5764.o
 obj-$(CONFIG_RADIO_SAA7706H) += saa7706h.o
 obj-$(CONFIG_RADIO_TEF6862) += tef6862.o
 obj-$(CONFIG_RADIO_TIMBERDALE) += radio-timb.o
+obj-$(CONFIG_RADIO_WL1273) += radio-wl1273.o
 
 EXTRA_CFLAGS += -Isound
diff --git a/drivers/media/radio/radio-wl1273.c 
b/drivers/media/radio/radio-wl1273.c
new file mode 100644
index 000..17b72df
--- /dev/null
+++ b/drivers/media/radio/radio-wl1273.c
@@ -0,0 +1,1849 @@
+/*
+ * Driver for the Texas Instruments WL1273 FM radio.
+ *
+ * Copyright (C) Nokia Corporation
+ * Author: Matti J. Aaltonen matti.j.aalto...@nokia.com
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License
+ * version 2 as published by the Free Software Foundation.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ */
+
+#undef DEBUG
+
+#include asm/unaligned.h
+#include linux/delay.h
+#include linux/firmware.h
+#include linux/mfd/wl1273-core.h
+#include linux/platform_device.h
+#include media/v4l2-common.h
+#include media/v4l2-device.h
+#include media/v4l2-ioctl.h
+
+#define DRIVER_DESC Wl1273 FM Radio - V4L2
+
+#define WL1273_POWER_SET_OFF   0
+#define WL1273_POWER_SET_FM(1  0)
+#define WL1273_POWER_SET_RDS   (1  1)
+#define WL1273_POWER_SET_RETENTION (1  4)
+
+#define WL1273_PUPD_SET_OFF0x00
+#define WL1273_PUPD_SET_ON 0x01
+#define WL1273_PUPD_SET_RETENTION  0x10
+
+#define WL1273_FREQ_MULT   (1 / 625)
+#define WL1273_INV_FREQ_MULT   (625 / 1)
+/*
+ * static unsigned char radio_region - Region
+ *
+ * The regions are 0=Japan, 1=USA-Europe. USA-Europe is the default.
+ */
+static unsigned char radio_region = 1;
+module_param(radio_region, byte, 0);
+MODULE_PARM_DESC(radio_region, Region: 0=Japan, 1=USA-Europe*);
+
+/*
+ * static int radio_nr - The number of the radio device
+ *
+ * The default is 0.
+ */
+static int radio_nr = -1;
+module_param(radio_nr, int, 0);
+MODULE_PARM_DESC(radio_nr, Radio Nr);
+
+struct wl1273_device {
+   struct v4l2_device v4l2dev;
+   struct video_device videodev;
+   struct device *dev;
+   struct wl1273_core *core;
+   bool rds_on;
+};
+
+static int wl1273_fm_set_tx_freq(struct wl1273_core *core, unsigned int freq)
+{
+   int r = 0;
+
+   if (freq  core-regions[core-region].bottom_frequency) {
+   dev_err(core-i2c_dev-dev,
+   Frequency out of range: %d  %d\n,
+   freq, core-regions[core-region].bottom_frequency);
+   return -EDOM;
+   }
+
+   if (freq  core-regions[core-region].top_frequency) {
+   dev_err(core-i2c_dev-dev,
+   Frequency out of range: %d  %d\n,
+   freq, core-regions[core-region].top_frequency);
+   return -EDOM;
+   }
+
+   /*
+*  The driver works better with this 

Re: Post DSO scan file for Aberdare

2010-04-30 Thread Christoph Pfister
2010/3/9 Mike m...@redtux.org.uk:
 Please see attached scan file for uk-Aberdare if anyone finds it useful

Hmm, I'm not sure whether you're the guy who also sent this
(different) update:
http://www.mail-archive.com/linux-media@vger.kernel.org/msg17569.html

Can you enlighten me please?

Thanks,

Christoph
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: debugging my Tevii S660 usb 2.0 dvb-s2 device

2010-04-30 Thread william

Hi all and Igor,

i only showed information with the drivers from tevii but then i looked 
again at the source from the hg v4l repo and there was support for my s660.

So sorry i asked questions about the drivers from tevii itself.

But now the following:

[   45.654362] dvb-usb: found a 'TeVii S660 USB' in cold state, will try 
to load a firmware

[   45.654379] usb 1-3: firmware: requesting dvb-usb-s630.fw
[   45.717438] dvb-usb: downloading firmware from file 'dvb-usb-s630.fw'
[   45.717450] dw2102: start downloading DW210X firmware
[   45.824245] usb 1-3: USB disconnect, address 3
[   45.930055] dvb-usb: found a 'TeVii S660 USB' in warm state.
[   45.930167] dvb-usb: will pass the complete MPEG2 transport stream to 
the software demuxer.

[   45.930233] DVB: registering new adapter (TeVii S660 USB)
[   56.182533] dvb-usb: MAC address: 00:00:00:00:00:00
[   56.262532] mt312: R(126): 00
[   56.262543] Only Zarlink VP310/MT312/ZL10313 are supported chips.
[   56.607024] ds3000_attach
[   56.642535] ds3000_readreg: read reg 0x00, value 0x00
[   56.642542] Invalid probe, probably not a DS3000
[   56.642816] dvb-usb: no frontend was attached by 'TeVii S660 USB'
[   56.643037] input: IR-receiver inside an USB DVB receiver as 
/devices/pci:00/:00:1d.7/usb1/1-3/input/input5

[   56.643189] dvb-usb: schedule remote query interval to 150 msecs.
[   56.643203] dvb-usb: TeVii S660 USB successfully initialized and 
connected.

[   56.643290] usbcore: registered new interface driver dw2102
[   56.773230] dvb-usb: TeVii S660 USB successfully deinitialized and 
disconnected.
[   57.050043] usb 1-3: new high speed USB device using ehci_hcd and 
address 5


in my previous post i got a message that an mt312 chip was found and now 
it does not find anything.

so now i don't have a dvb device at all.

the firmware is from the drivers from tevii. I tried and the s630 
firmware and later the s660 firmware renamed to s630 but none worked.


After installing the driver/changing the firmware, I shutdown the 
computer removed the power from the tevii device and then replugged and 
started my computer again.


Igor or someone else do you have an idea what is happening?

With kind regards

William van de Velde


--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: updated frequency list for Denmark (DVB-T)

2010-04-30 Thread Christoph Pfister
2010/3/8 René Kjellerup rk.katana.st...@gmail.com:
 this is all the used frequencies of the Main MUX 1  2 transponders

Updated, thanks!

 René
 --
 -- as life grows older, I gain experience.

Christoph
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


UVC Webcam

2010-04-30 Thread Gijo Prems
Hello,

I have some queries related to linux uvc client driver(uvcvideo) and
general uvc webcam functionality.

1. There is a wDelay (during probe-commit) parameter which camera
exposes to the host signifying the delay (Latency) inside the camera.
Does the UVC driver on Linux Host expose this parameter to the
application if they require it?
And what would be the use case of this parameter?

2. How the audio and video sync (lipsync) would happen on host side?

3. How buffers are allocated on the host side?
Which parameter from camera needs to be set to signify the correct
buffer allocation?

4. Are there any parameters in USB audio class which allocate the
buffers and handles the latency at host?

It would be great if someone could put some thoughts on these.

-Gijo
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[cron job] v4l-dvb daily build 2.6.22 and up: ERRORS, 2.6.16-2.6.21: WARNINGS

2010-04-30 Thread Hans Verkuil
This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.

Results of the daily build of v4l-dvb:

date:Fri Apr 30 19:00:22 CEST 2010
path:http://www.linuxtv.org/hg/v4l-dvb
changeset:   14619:ee9826bc7106
git master:   f6760aa024199cfbce564311dc4bc4d47b6fb349
git media-master: d3be2fab3a10b6c798a5f9970146d166d3345c37
gcc version:  i686-linux-gcc (GCC) 4.4.3
host hardware:x86_64
host os:  2.6.32.5

linux-2.6.32.6-armv5: OK
linux-2.6.33-armv5: OK
linux-2.6.34-rc1-armv5: OK
linux-2.6.32.6-armv5-davinci: OK
linux-2.6.33-armv5-davinci: OK
linux-2.6.34-rc1-armv5-davinci: OK
linux-2.6.32.6-armv5-ixp: OK
linux-2.6.33-armv5-ixp: OK
linux-2.6.34-rc1-armv5-ixp: OK
linux-2.6.32.6-armv5-omap2: OK
linux-2.6.33-armv5-omap2: OK
linux-2.6.34-rc1-armv5-omap2: OK
linux-2.6.22.19-i686: WARNINGS
linux-2.6.23.17-i686: WARNINGS
linux-2.6.24.7-i686: OK
linux-2.6.25.20-i686: OK
linux-2.6.26.8-i686: OK
linux-2.6.27.44-i686: OK
linux-2.6.28.10-i686: OK
linux-2.6.29.1-i686: WARNINGS
linux-2.6.30.10-i686: OK
linux-2.6.31.12-i686: OK
linux-2.6.32.6-i686: OK
linux-2.6.33-i686: OK
linux-2.6.34-rc1-i686: WARNINGS
linux-2.6.32.6-m32r: OK
linux-2.6.33-m32r: OK
linux-2.6.34-rc1-m32r: OK
linux-2.6.32.6-mips: OK
linux-2.6.33-mips: OK
linux-2.6.34-rc1-mips: OK
linux-2.6.32.6-powerpc64: OK
linux-2.6.33-powerpc64: OK
linux-2.6.34-rc1-powerpc64: WARNINGS
linux-2.6.22.19-x86_64: WARNINGS
linux-2.6.23.17-x86_64: WARNINGS
linux-2.6.24.7-x86_64: OK
linux-2.6.25.20-x86_64: OK
linux-2.6.26.8-x86_64: OK
linux-2.6.27.44-x86_64: OK
linux-2.6.28.10-x86_64: OK
linux-2.6.29.1-x86_64: WARNINGS
linux-2.6.30.10-x86_64: OK
linux-2.6.31.12-x86_64: OK
linux-2.6.32.6-x86_64: OK
linux-2.6.33-x86_64: OK
linux-2.6.34-rc1-x86_64: WARNINGS
linux-git-armv5: WARNINGS
linux-git-armv5-davinci: WARNINGS
linux-git-armv5-ixp: WARNINGS
linux-git-armv5-omap2: WARNINGS
linux-git-i686: WARNINGS
linux-git-m32r: OK
linux-git-mips: OK
linux-git-powerpc64: OK
linux-git-x86_64: WARNINGS
spec: ERRORS
spec-git: OK
sparse: ERRORS
linux-2.6.16.62-i686: WARNINGS
linux-2.6.17.14-i686: WARNINGS
linux-2.6.18.8-i686: WARNINGS
linux-2.6.19.7-i686: WARNINGS
linux-2.6.20.21-i686: WARNINGS
linux-2.6.21.7-i686: WARNINGS
linux-2.6.16.62-x86_64: WARNINGS
linux-2.6.17.14-x86_64: WARNINGS
linux-2.6.18.8-x86_64: WARNINGS
linux-2.6.19.7-x86_64: WARNINGS
linux-2.6.20.21-x86_64: WARNINGS
linux-2.6.21.7-x86_64: WARNINGS

Detailed results are available here:

http://www.xs4all.nl/~hverkuil/logs/Friday.log

Full logs are available here:

http://www.xs4all.nl/~hverkuil/logs/Friday.tar.bz2

The V4L-DVB specification from this daily build is here:

http://www.xs4all.nl/~hverkuil/spec/media.html
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH 0/5] Pushdown bkl from v4l ioctls

2010-04-30 Thread Arnd Bergmann
On Thursday 29 April 2010 09:10:42 Laurent Pinchart wrote:
 On Thursday 29 April 2010 08:44:29 Hans Verkuil wrote:
 
  3) Investigate what needs to be done to replace the bkl with a v4l2-dev.c
  global mutex. Those drivers that call the bkl themselves should probably be
  converted to do proper locking, but there are only about 14 drivers that do
  this. The other 60 or so drivers should work fine if a v4l2-dev global lock
  is used. At this point the bkl is effectively removed from the v4l
  subsystem.
  
  4) Work on the remaining 60 drivers to do proper locking and get rid of the
  v4l2-dev global lock. This is probably less work than it sounds.
  
  Since your patch moves everything down to the driver level it will actually
  make this work harder rather than easier. And it touches almost all drivers
  as well.
 
 Every driver will need to be carefully checked to make sure the BKL can be 
 replaced by a v4l2-dev global mutex. Why would it be more difficult to do so 
 if the BKL is pushed down to the drivers ?

Note that you can completely skip the step of a v4l2-dev global mutex with
Frederic's patch. This is the only use of the BKL in the common v4l2
code as far as I can tell, so instead of introducing yet another global
lock, you can go straight to stage 4 and look at each driver separately,
possibly introducing a per driver lock.

Arnd
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH] TT S2-1600 allow more current for diseqc

2010-04-30 Thread hermann pitton
Hi André,

Am Freitag, den 30.04.2010, 07:44 +0200 schrieb André Weidemann:
 Hi Hermann,
[snip]
 
  Andre, BTW, assuming you still have a CTX944 (md8800 Quad), can you
  measure if the 16be:0008 device really does switch between 13 and 18V.
 
 You seem to mistake me for someone else. I do not have a CTX944 and 
 never had.
 
 Regards
   André

yes, sorry, over the years with tda10086 questions and those about BBC
HD reception I confused Weidemann with Weymann (Helmut), who had such a
device in 2005.

Cheers,
Hermann


--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [OT] preferred video apps?

2010-04-30 Thread Mauro Carvalho Chehab
Randy Dunlap wrote:
 Hi,
 
 Sorry for a non-kernel question, but I'd like to get some suggestions
 on video recording and editing software, please.
 
 If it matters, this is mostly for recording  editing sports events (matches).
 
 Reply privately if you prefer ...

Please, _do_not_ reply privately ;) 

We should build a relation of the userspace applications we need to care when 
testing for regressions, so, this is not OT. It would be nice to hear what are
the preferred open source applications.

From my side, those are the applications I use:
analog: xawtv 3, xawtv 4, tvtime, mencoder, ffmpeg

Only mencoder and ffmpeg can record - but xawtv (and xdtv) call them.

On digital side, I use kaffeine, gnutv and vlc. Kaffeine and gnutv can record. 
Not sure about vlc.

mplayer is capable of working with both analog and digital (and, by consequence,
mencoder).

Although I don't use, mythtv and vdr are also very popular applications. AFAIK,
both have record support.

-- 

Cheers,
Mauro
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH 0/5] Pushdown bkl from v4l ioctls

2010-04-30 Thread Hans Verkuil
On Thursday 29 April 2010 05:42:39 Frederic Weisbecker wrote:
 Hi,
 
 Linus suggested to rename struct v4l2_file_operations::ioctl
 into bkl_ioctl to eventually get something greppable and make
 its background explicit.
 
 While at it I thought it could be a good idea to just pushdown
 the bkl to every v4l drivers that have an .ioctl, so that we
 actually remove struct v4l2_file_operations::ioctl for good.
 
 It passed make allyesconfig on sparc.
 Please tell me what you think.

I much prefer to keep the bkl inside the v4l2 core. One reason is that I
think that we can replace the bkl in the core with a mutex. Still not
ideal of course, so the next step will be to implement proper locking in
each driver. For this some additional v4l infrastructure work needs to be
done. I couldn't proceed with that until the v4l events API patches went in,
and that happened yesterday.

So from my point of view the timeline is this:

1) I do the infrastructure work this weekend. This will make it much easier to
convert drivers to do proper locking. And it will also simplify v4l2_priority
handling, so I'm killing two birds with one stone :-)

2) Wait until Arnd's patch gets merged that pushes the bkl down to v4l2-dev.c

3) Investigate what needs to be done to replace the bkl with a v4l2-dev.c
global mutex. Those drivers that call the bkl themselves should probably be
converted to do proper locking, but there are only about 14 drivers that do
this. The other 60 or so drivers should work fine if a v4l2-dev global lock
is used. At this point the bkl is effectively removed from the v4l subsystem.

4) Work on the remaining 60 drivers to do proper locking and get rid of the
v4l2-dev global lock. This is probably less work than it sounds.

Since your patch moves everything down to the driver level it will actually
make this work harder rather than easier. And it touches almost all drivers
as well.

Regards,

Hans

 
 Thanks.
 
 Frederic Weisbecker (5):
   v4l: Pushdown bkl into video_ioctl2
   v4l: Use video_ioctl2_unlocked from drivers that don't want the bkl
   v4l: Change users of video_ioctl2 to use unlocked_ioctl
   v4l: Pushdown bkl to drivers that implement their own ioctl
   v4l: Remove struct v4l2_file_operations::ioctl
 
  drivers/media/common/saa7146_fops.c  |2 +-
  drivers/media/radio/dsbr100.c|2 +-
  drivers/media/radio/radio-aimslab.c  |2 +-
  drivers/media/radio/radio-aztech.c   |2 +-
  drivers/media/radio/radio-cadet.c|2 +-
  drivers/media/radio/radio-gemtek-pci.c   |2 +-
  drivers/media/radio/radio-gemtek.c   |2 +-
  drivers/media/radio/radio-maestro.c  |2 +-
  drivers/media/radio/radio-maxiradio.c|2 +-
  drivers/media/radio/radio-miropcm20.c|2 +-
  drivers/media/radio/radio-mr800.c|2 +-
  drivers/media/radio/radio-rtrack2.c  |2 +-
  drivers/media/radio/radio-sf16fmi.c  |2 +-
  drivers/media/radio/radio-sf16fmr2.c |2 +-
  drivers/media/radio/radio-si4713.c   |2 +-
  drivers/media/radio/radio-tea5764.c  |2 +-
  drivers/media/radio/radio-terratec.c |2 +-
  drivers/media/radio/radio-timb.c |2 +-
  drivers/media/radio/radio-trust.c|2 +-
  drivers/media/radio/radio-typhoon.c  |2 +-
  drivers/media/radio/radio-zoltrix.c  |2 +-
  drivers/media/radio/si470x/radio-si470x-common.c |2 +-
  drivers/media/video/arv.c|2 +-
  drivers/media/video/au0828/au0828-video.c|   14 
  drivers/media/video/bt8xx/bttv-driver.c  |   26 +++---
  drivers/media/video/bw-qcam.c|   11 +-
  drivers/media/video/c-qcam.c |   11 +-
  drivers/media/video/cafe_ccic.c  |   14 
  drivers/media/video/cpia.c   |   11 +-
  drivers/media/video/cpia2/cpia2_v4l.c|   11 +-
  drivers/media/video/cx18/cx18-streams.c  |   12 +++---
  drivers/media/video/cx231xx/cx231xx-video.c  |4 +-
  drivers/media/video/cx23885/cx23885-417.c|2 +-
  drivers/media/video/cx23885/cx23885-video.c  |4 +-
  drivers/media/video/cx88/cx88-blackbird.c|2 +-
  drivers/media/video/cx88/cx88-video.c|4 +-
  drivers/media/video/davinci/vpfe_capture.c   |2 +-
  drivers/media/video/davinci/vpif_capture.c   |2 +-
  drivers/media/video/davinci/vpif_display.c   |2 +-
  drivers/media/video/em28xx/em28xx-video.c|4 +-
  drivers/media/video/et61x251/et61x251_core.c |   27 +++
  drivers/media/video/gspca/gspca.c|2 +-
  drivers/media/video/hdpvr/hdpvr-video.c  |2 +-
  drivers/media/video/meye.c   

Re: [ANNOUNCEMENT] Media controller tree updated

2010-04-30 Thread Mauro Carvalho Chehab
Hi Laurent,

Laurent Pinchart wrote:
 Hi everybody,
 
 The next version of the media controller patches is available in git at
 
 http://git.linuxtv.org/pinchartl/v4l-dvb-media.git
 
 To avoid putting too much pressure on the linuxtv.org git server, please make 
 sure you reference an existing mainline Linux git tree when cloning v4l-dvb-
 media (see the --reference option to git-clone).

I've made a small script that added the proper instructions to the existing
clones of the kernel tree. Please check if it is ok. 

The script is not automatic. When I have some time, I'll integrate it with some 
tool to run it automatically after a new tree is added there, but, for now, I 
need to run it after I notice that somebody created a new tree. The script has 
a basic test to discover that the tree is based on Kernel tree: it checks if a 
v2.6.32 tag exist at the new tree (ok, I confess: I was very lazy when I 
wrote 
the script... it works with the current trees, but we need a more reliable way, 
if we want to run automatically).


Cheers,
Mauro
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html