Re: v4l-dvb unsupported device: Conceptronic CTVDIGUSB2 1b80:d393 (Afatech) - possibly similar to CTVCTVDIGRCU v3.0?

2010-06-29 Thread Matteo Sisti Sette

On 06/29/2010 07:54 AM, Jan Hoogenraad wrote:

I see: apparently the versions earlier than V3.0 of CTVDIGRCU used
Realtek RTL2831U. I'll make a note of that on the wiki page.


Thank you; indeed I provided incomplete information (i forgot the v3.0 
part).


Is it possible to force the driver to treat my chipset as if it was an 
af9015 and try and see if it works?


thanks
m.


--
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 2/2] V4L/DVB: radio-si4713: Add regulator framework support

2010-06-29 Thread Jarkko Nikula
On Sun, 13 Jun 2010 21:09:28 +0300
Jarkko Nikula jhnik...@gmail.com wrote:

 Convert the driver to use regulator framework instead of set_power callback.
 This with gpio_reset platform data provide cleaner way to manage chip VIO,
 VDD and reset signal inside the driver.
 
 Signed-off-by: Jarkko Nikula jhnik...@gmail.com
 Cc: Eduardo Valentin eduardo.valen...@nokia.com
 ---
 I don't have specifications for this chip so I don't know how long the
 reset signal must be active after power-up. I used 50 us from Maemo
 kernel sources for Nokia N900 and I can successfully enable-disable
 transmitter on N900 with vdd power cycling.
 ---

Ping? Any comments to these two Si4713 patches?


-- 
Jarkko
--
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


Fwd: v4l-dvb unsupported device: Conceptronic CTVDIGUSB2 1b80:d393 (Afatech) - possibly similar to CTVCTVDIGRCU v3.0?

2010-06-29 Thread Pedro Côrte-Real
On Tue, Jun 29, 2010 at 6:54 AM, Jan Hoogenraad
jan-conceptro...@hoogenraad.net wrote:
 I see: apparently the versions earlier than V3.0 of CTVDIGRCU used Realtek
 RTL2831U. I'll make a note of that on the wiki page.

Is the CTVDIGRCU well supported by mainline? I think I can source
these locally.

Is the AF9015 driver stable? I've had very bad luck with 3 different
devices now.

Pedro
--
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


Question on uvcvideo driver's power management

2010-06-29 Thread Samuel Xu
Question on uvcvideo driver's power management:
Q1: We found some USB material mentioned : Relationship between ACPI
Dx states and USB PM states (active/suspended) is orthogonal.
Suspend/resume might not effect device Dx state(e.g. D0/D1/D3). Is it
a correct statement for general usb device and uvcvideo usb device?
Q2: How to tell USB uvcvideo device’s ACPI Dx state. It seems lsusb
can’t tell us those info. (lspci works for PCI device’s Dx state)
Q3: How to tell USB uvcvideo device’s suspension state? will any query
via urb will cause resume of uvcvideo device?
Q4: should USB uvcvideo device driver response to do some
device-specific power action (e.g. device register writing) to put a
specific USB camera into low power state when responding to suspend
action? (I didn't find such device-specific power code inside uvcvideo
src code)
Q5: If Q4 is Yes, should device vendor respond for those device-specific code?

Thanks!
--
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: [media-ctl] [omap3camera:devel] How to use the app?

2010-06-29 Thread Laurent Pinchart
Hi Sergio,

On Tuesday 29 June 2010 01:34:01 Aguirre, Sergio wrote:
 Hi Laurent/Sakari,
 
 I have been attempting to migrate my IMX046 sensor driver, that I had
 working on my Zoom3(OMAP3630 ES1.1) with older codebase, to work with the
 latest omap3camera tree, 'devel' branch:
 
 http://gitorious.org/omap3camera/mainline/commits/devel
 
 And for that, I'm trying to also understand how to use your test tool:
 media-ctl:
 
 http://git.ideasonboard.org/?p=media-ctl.git;a=summary
 
 Now, the thing is that, I don't see any guide to learn how to write the
 Proper format for some of the parameters, like to build links in
 interactive mode (-i), or to set formats (-f).
 
 Can you please detail about a typical usage for this tool? (example on how
 to build a link, set link format, etc.)

I've pushed a new patch to the media-ctl repository that makes the help 
message a bit more verbose when running media-ctl -h. It describes the links 
and formats as follows:

Links and formats are defined as
link= pad, '-', pad, '[', flags, ']' ;
format  = pad, '[', fcc, ' ', size, [ ' ', crop ], ']' ;
pad = entity, ':', pad number ;
entity  = entity number | ( '\', entity name, '\' ) ;
size= width, 'x', height ;
crop= left, ',', top, '/', size ;
where the fields are
entity number   Entity numeric identifier
entity name Entify name (string)
pad number  Pad numeric identifier
flags   Link flags (0: inactive, 1: active)
fcc Format FourCC
width   Image width in pixels
height  Image height in pixels

For instance, to set the CCDC to preview link as active, the link specifier 
would be

'OMAP3 ISP CCDC:2 - OMAP3 ISP preview:0 [1]'

To set the format on the preview output pad to YUYV 1280x720, the format 
specifier would be

'OMAP3 ISP preview:2 [YUYV 1280x720]'

Spaces are optional.

 So far, my progress is pushed into this branch:
 
 http://dev.omapzoom.org/?p=saaguirre/linux-omap-camera.git;a=shortlog;h=ref
 s/heads/mc_migration_wip

Thanks for the link.

 And with that, after I boot, I get the following topology:

[snip]

You will find a set of patches that remove the legacy video nodes attached to 
this e-mail. They haven't been applied to the omap3camera tree yet, as we 
still haven't fixed all userspace components yet, but they should get there in 
a few weeks hopefully. You should probably apply them to your tree to make 
sure you don't start using the legacy video nodes by mistake. They also remove 
a lot of code, which is always good, and remove the hardcoded number of 
sensors.

-- 
Regards,

Laurent Pinchart


omap34xxcam-patches.tar.gz
Description: application/compressed-tar


Re: Problems with Pinnacle 310i (saa7134) and recent kernels

2010-06-29 Thread Avl Jawrowski
Well, thank you very much Hermann!
You're very helpul. The sure thing is that when I'll buy a new card I'll ask 
you 
for a hint.
Thank you again,
Avl

--
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


[media-ctl RFC][PATCH 0/5] Exported headers to userspace fixes

2010-06-29 Thread Sergio Aguirre
Hi Laurent,

While trying to generate kernel headers by doing 'make headers_install',
I noticed that the headers weren't actually copied into the filesystem.

So, here's some fixes I have come across. This is the baseline I use:

http://gitorious.org/omap3camera/mainline/commits/devel

Any feedback is greatly appreciated.

Regards,
Sergio

Sergio Aguirre (5):
  media: Add media.h to headers_install
  v4l: Add v4l2-subdev.h to headers_install
  v4l: Add v4l2-mediabus.h to headers_install
  media: Add missing linux/types.h include
  v4l: Add missing linux/types.h include

 include/linux/Kbuild  |3 +++
 include/linux/media.h |2 ++
 include/linux/v4l2-mediabus.h |1 +
 include/linux/v4l2-subdev.h   |1 +
 4 files changed, 7 insertions(+), 0 deletions(-)

--
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


[media-ctl RFC][PATCH 2/5] v4l: Add v4l2-subdev.h to headers_install

2010-06-29 Thread Sergio Aguirre
This complements commit ID:

  commit cf16808f35cf59524fde0b15e5974cba165988b1
  Author: Laurent Pinchart laurent.pinch...@ideasonboard.com
  Date:   Tue Mar 16 00:26:04 2010 +0100

  v4l: v4l2_subdev userspace format API

Signed-off-by: Sergio Aguirre saagui...@ti.com
---
 include/linux/Kbuild |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/include/linux/Kbuild b/include/linux/Kbuild
index efc9718..c5e8c6a 100644
--- a/include/linux/Kbuild
+++ b/include/linux/Kbuild
@@ -167,6 +167,7 @@ header-y += udf_fs_i.h
 header-y += ultrasound.h
 header-y += un.h
 header-y += utime.h
+header-y += v4l2-subdev.h
 header-y += veth.h
 header-y += videotext.h
 header-y += x25.h
-- 
1.6.3.3

--
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


[media-ctl RFC][PATCH 5/5] v4l: Add missing linux/types.h include

2010-06-29 Thread Sergio Aguirre
This fixes following headers_check warnings:

*/usr/include/linux/v4l2-mediabus.h:63: found __[us]{8,16,32,64} type without 
#include linux/types.h
*/usr/include/linux/v4l2-subdev.h:33: found __[us]{8,16,32,64} type without 
#include linux/types.h

Signed-off-by: Sergio Aguirre saagui...@ti.com
---
 include/linux/v4l2-mediabus.h |1 +
 include/linux/v4l2-subdev.h   |1 +
 2 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/include/linux/v4l2-mediabus.h b/include/linux/v4l2-mediabus.h
index 6832919..2a8e490 100644
--- a/include/linux/v4l2-mediabus.h
+++ b/include/linux/v4l2-mediabus.h
@@ -11,6 +11,7 @@
 #ifndef __LINUX_V4L2_MEDIABUS_H
 #define __LINUX_V4L2_MEDIABUS_H
 
+#include linux/types.h
 #include linux/videodev2.h
 
 /*
diff --git a/include/linux/v4l2-subdev.h b/include/linux/v4l2-subdev.h
index 5df95d4..e2e2c8d 100644
--- a/include/linux/v4l2-subdev.h
+++ b/include/linux/v4l2-subdev.h
@@ -19,6 +19,7 @@
 #define __LINUX_V4L2_SUBDEV_H
 
 #include linux/ioctl.h
+#include linux/types.h
 #include linux/v4l2-mediabus.h
 
 enum v4l2_subdev_format {
-- 
1.6.3.3

--
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


[media-ctl RFC][PATCH 4/5] media: Add missing linux/types.h include

2010-06-29 Thread Sergio Aguirre
This fixes headers_check warning:

*/usr/include/linux/media.h:25: found __[us]{8,16,32,64} type without #include 
linux/types.h

Signed-off-by: Sergio Aguirre saagui...@ti.com
---
 include/linux/media.h |2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/include/linux/media.h b/include/linux/media.h
index a44875d..4f39639 100644
--- a/include/linux/media.h
+++ b/include/linux/media.h
@@ -1,6 +1,8 @@
 #ifndef __LINUX_MEDIA_H
 #define __LINUX_MEDIA_H
 
+#include linux/types.h
+
 #define MEDIA_ENTITY_TYPE_NODE 1
 #define MEDIA_ENTITY_TYPE_SUBDEV   2
 
-- 
1.6.3.3

--
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


[media-ctl RFC][PATCH 3/5] v4l: Add v4l2-mediabus.h to headers_install

2010-06-29 Thread Sergio Aguirre
This complements commit ID:

  commit f1ee99adf3c73c6a2423c11813e17ca0227d98b7
  Author: Laurent Pinchart laurent.pinch...@ideasonboard.com
  Date:   Mon Mar 15 23:33:31 2010 +0100

  v4l: Move the media/v4l2-mediabus.h header to include/linux

Signed-off-by: Sergio Aguirre saagui...@ti.com
---
 include/linux/Kbuild |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/include/linux/Kbuild b/include/linux/Kbuild
index c5e8c6a..257812e 100644
--- a/include/linux/Kbuild
+++ b/include/linux/Kbuild
@@ -167,6 +167,7 @@ header-y += udf_fs_i.h
 header-y += ultrasound.h
 header-y += un.h
 header-y += utime.h
+header-y += v4l2-mediabus.h
 header-y += v4l2-subdev.h
 header-y += veth.h
 header-y += videotext.h
-- 
1.6.3.3

--
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


[media-ctl RFC][PATCH 1/5] media: Add media.h to headers_install

2010-06-29 Thread Sergio Aguirre
This makes the header available to the user-space apps when
doing headers_install.

Signed-off-by: Sergio Aguirre saagui...@ti.com
---
 include/linux/Kbuild |1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/include/linux/Kbuild b/include/linux/Kbuild
index 2fc8e14..efc9718 100644
--- a/include/linux/Kbuild
+++ b/include/linux/Kbuild
@@ -112,6 +112,7 @@ header-y += magic.h
 header-y += major.h
 header-y += map_to_7segment.h
 header-y += matroxfb.h
+header-y += media.h
 header-y += meye.h
 header-y += minix_fs.h
 header-y += mmtimer.h
-- 
1.6.3.3

--
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: [media-ctl RFC][PATCH 0/5] Exported headers to userspace fixes

2010-06-29 Thread Laurent Pinchart
Hi Sergio,

On Tuesday 29 June 2010 14:43:05 Sergio Aguirre wrote:
 Hi Laurent,
 
 While trying to generate kernel headers by doing 'make headers_install',
 I noticed that the headers weren't actually copied into the filesystem.
 
 So, here's some fixes I have come across. This is the baseline I use:
 
 http://gitorious.org/omap3camera/mainline/commits/devel
 
 Any feedback is greatly appreciated.

Thanks for the patches. They look good to me.

I'll squash the patches with the related patches when submitting the code 
upstream. In the meantime they will go to the omap3camera tree, but that will 
have to wait until Sakari comes back from holidays.

-- 
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: em28xx/xc3028 - kernel driver vs. Markus Rechberger's driver

2010-06-29 Thread Torsten Krah
Am Mittwoch, 23. Juni 2010, um 00:15:36 schrieb Mauro Carvalho Chehab:
 You probably damaged the contents of the device's eeprom. If you have the
 logs with the previous eeprom contents somewhere, it is possible to recover
 it. There's an util at v4l-utils that allows re-writing the information at
 the eeprom.

Hi,

can you tell me which util and how it can be done.
I am too affected and damaged the eeprom (don't know how) - but my usb id did 
change too from e1ba:2870 to eb1a:2871. 

Still need to find a old dmesg log for my stick but it should be this:

http://www.mail-archive.com/linux-media@vger.kernel.org/msg14758.html

Is this output enough to rewrite the correct eeprom date back to my borked 
stick or is something else needed?

thx

Torsten

-- 
Bitte senden Sie mir keine Word- oder PowerPoint-Anhänge.
Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html

Really, I'm not out to destroy Microsoft. That will just be a 
completely unintentional side effect.
-- Linus Torvalds


smime.p7s
Description: S/MIME cryptographic signature


[GIT PATCHES FOR 2.6.36] Updates for the uvcvideo driver

2010-06-29 Thread Laurent Pinchart
The following changes since commit 41c5f984b67b331064e69acc9fca5e99bf73d400:

  Merge tag 'v2.6.35-rc2' into HEAD (2010-06-09 00:05:54 -0300)

are available in the git repository at:

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

Hans de Goede (1):
  uvcvideo: Make button controls work properly

Laurent Pinchart (4):
  uvcvideo: Support menu controls in the control mapping API
  uvcvideo: Define control information bits using macros
  uvcvideo: Don't use stack-based buffers for USB transfers
  uvcvideo: Add support for Manta MM-353 Plako

Martin Rubli (1):
  uvcvideo: Add support for absolute pan/tilt controls

 drivers/media/video/uvc/uvc_ctrl.c   |  105 +++---
 drivers/media/video/uvc/uvc_driver.c |   10 +++
 drivers/media/video/uvc/uvc_v4l2.c   |   95 +++---
 drivers/media/video/uvc/uvcvideo.h   |   26 +++--
 include/linux/usb/video.h|7 ++
 5 files changed, 194 insertions(+), 49 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: em28xx/xc3028 - kernel driver vs. Markus Rechberger's driver

2010-06-29 Thread Douglas Schilling Landgraf
Hello Torsten,

On Tue, Jun 29, 2010 at 10:42 AM, Torsten Krah
tk...@fachschaft.imn.htwk-leipzig.de wrote:
 Am Mittwoch, 23. Juni 2010, um 00:15:36 schrieb Mauro Carvalho Chehab:
 You probably damaged the contents of the device's eeprom. If you have the
 logs with the previous eeprom contents somewhere, it is possible to recover
 it. There's an util at v4l-utils that allows re-writing the information at
 the eeprom.

 Hi,

 can you tell me which util and how it can be done.
 I am too affected and damaged the eeprom (don't know how) - but my usb id did
 change too from e1ba:2870 to eb1a:2871.

 Still need to find a old dmesg log for my stick but it should be this:

 http://www.mail-archive.com/linux-media@vger.kernel.org/msg14758.html

 Is this output enough to rewrite the correct eeprom date back to my borked
 stick or is something else needed?


Yes, I think it's enough, of course if it's not the right one, you
always can re-write until you
get the right eeprom. Good luck!

The rewrite_eeprom.pl is available under git.utils tree:
http://git.linuxtv.org/v4l-utils.git

All instructions are available into the source code. Let me know if
you have any problem with such tool.

BTW, maybe is a good idea to create at wikipage a page for EEPROMs.

Cheers
Douglas
--
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: ERRORS

2010-06-29 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:Tue Jun 29 19:00:25 CEST 2010
path:http://www.linuxtv.org/hg/v4l-dvb
changeset:   14993:9652f85e688a
git master:   f6760aa024199cfbce564311dc4bc4d47b6fb349
git media-master: 41c5f984b67b331064e69acc9fca5e99bf73d400
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-armv5: WARNINGS
linux-2.6.35-rc1-armv5: ERRORS
linux-2.6.32.6-armv5-davinci: OK
linux-2.6.33-armv5-davinci: OK
linux-2.6.34-armv5-davinci: WARNINGS
linux-2.6.35-rc1-armv5-davinci: ERRORS
linux-2.6.32.6-armv5-ixp: WARNINGS
linux-2.6.33-armv5-ixp: WARNINGS
linux-2.6.34-armv5-ixp: WARNINGS
linux-2.6.35-rc1-armv5-ixp: ERRORS
linux-2.6.32.6-armv5-omap2: OK
linux-2.6.33-armv5-omap2: OK
linux-2.6.34-armv5-omap2: WARNINGS
linux-2.6.35-rc1-armv5-omap2: ERRORS
linux-2.6.22.19-i686: ERRORS
linux-2.6.23.17-i686: ERRORS
linux-2.6.24.7-i686: WARNINGS
linux-2.6.25.20-i686: WARNINGS
linux-2.6.26.8-i686: WARNINGS
linux-2.6.27.44-i686: WARNINGS
linux-2.6.28.10-i686: WARNINGS
linux-2.6.29.1-i686: WARNINGS
linux-2.6.30.10-i686: WARNINGS
linux-2.6.31.12-i686: OK
linux-2.6.32.6-i686: OK
linux-2.6.33-i686: OK
linux-2.6.34-i686: WARNINGS
linux-2.6.35-rc1-i686: ERRORS
linux-2.6.32.6-m32r: OK
linux-2.6.33-m32r: OK
linux-2.6.34-m32r: WARNINGS
linux-2.6.35-rc1-m32r: ERRORS
linux-2.6.32.6-mips: OK
linux-2.6.33-mips: OK
linux-2.6.34-mips: WARNINGS
linux-2.6.35-rc1-mips: ERRORS
linux-2.6.32.6-powerpc64: OK
linux-2.6.33-powerpc64: OK
linux-2.6.34-powerpc64: WARNINGS
linux-2.6.35-rc1-powerpc64: ERRORS
linux-2.6.22.19-x86_64: ERRORS
linux-2.6.23.17-x86_64: ERRORS
linux-2.6.24.7-x86_64: WARNINGS
linux-2.6.25.20-x86_64: WARNINGS
linux-2.6.26.8-x86_64: WARNINGS
linux-2.6.27.44-x86_64: WARNINGS
linux-2.6.28.10-x86_64: WARNINGS
linux-2.6.29.1-x86_64: WARNINGS
linux-2.6.30.10-x86_64: WARNINGS
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-x86_64: WARNINGS
linux-2.6.35-rc1-x86_64: ERRORS
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: ERRORS
linux-2.6.17.14-i686: ERRORS
linux-2.6.18.8-i686: ERRORS
linux-2.6.19.7-i686: ERRORS
linux-2.6.20.21-i686: ERRORS
linux-2.6.21.7-i686: ERRORS
linux-2.6.16.62-x86_64: ERRORS
linux-2.6.17.14-x86_64: ERRORS
linux-2.6.18.8-x86_64: ERRORS
linux-2.6.19.7-x86_64: ERRORS
linux-2.6.20.21-x86_64: ERRORS
linux-2.6.21.7-x86_64: ERRORS

Detailed results are available here:

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

Full logs are available here:

http://www.xs4all.nl/~hverkuil/logs/Tuesday.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: em28xx/xc3028 - kernel driver vs. Markus Rechberger's driver

2010-06-29 Thread Torsten Krah
Am Dienstag, 29. Juni 2010 schrieb Douglas Schilling Landgraf:
 The rewrite_eeprom.pl is available under git.utils tree:
 http://git.linuxtv.org/v4l-utils.git
 
 All instructions are available into the source code. Let me know if
 you have any problem with such tool.

Hi, yes i have problems with the tool :-).

Connected my broken device:

lsusb:
Bus 001 Device 002: ID eb1a:2871 eMPIA Technology, Inc.

dmesg:
[  455.348172] usb 1-1: new high speed USB device using ehci_hcd and address 2
[  455.481791] usb 1-1: configuration #1 chosen from 1 choice
[  455.609668] usbcore: registered new interface driver snd-usb-audio


Running the script which does generate the recover script does work.
But running this one fails with:

Could not detect i2c bus from any device, run again ./rewrite_eeprom.pl. Did 
you forget to connect the device?
Modules supported: em28xx saa7134

Device is connected.

Anything what i can do?

thx

Torsten


smime.p7s
Description: S/MIME cryptographic signature


Re: [PATCHv4 1/3] mx2_camera: Add soc_camera support for i.MX25/i.MX27

2010-06-29 Thread Guennadi Liakhovetski
Hi Baruch

On Mon, 21 Jun 2010, Baruch Siach wrote:

 This is the soc_camera support developed by Sascha Hauer for the i.MX27.  Alan
 Carvalho de Assis modified the original driver to get it working on more 
 recent
 kernels. I modified it further to add support for i.MX25. This driver has been
 tested on i.MX25 and i.MX27 based platforms.

This looks good to me, thanks! Overflow on eMMA is, probably, still 
broken, but it will, most probably, remain so, until someone tests and 
fixes it. One question though: do you know whether this imx/mxc overhaul: 
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-June/thread.html#18844
 
affects your driver? I can ask Uwe, but maybe you have an idea or could 
test your patches with Uwe's git tree?

Thanks
Guennadi

 
 Signed-off-by: Baruch Siach bar...@tkos.co.il
 ---
  arch/arm/plat-mxc/include/mach/memory.h  |4 +-
  arch/arm/plat-mxc/include/mach/mx2_cam.h |   46 +
  drivers/media/video/Kconfig  |   13 +
  drivers/media/video/Makefile |1 +
  drivers/media/video/mx2_camera.c | 1493 
 ++
  5 files changed, 1555 insertions(+), 2 deletions(-)
  create mode 100644 arch/arm/plat-mxc/include/mach/mx2_cam.h
  create mode 100644 drivers/media/video/mx2_camera.c
 
 diff --git a/arch/arm/plat-mxc/include/mach/memory.h 
 b/arch/arm/plat-mxc/include/mach/memory.h
 index c4b40c3..5803836 100644
 --- a/arch/arm/plat-mxc/include/mach/memory.h
 +++ b/arch/arm/plat-mxc/include/mach/memory.h
 @@ -44,12 +44,12 @@
   */
  #define CONSISTENT_DMA_SIZE SZ_8M
  
 -#elif defined(CONFIG_MX1_VIDEO)
 +#elif defined(CONFIG_MX1_VIDEO) || defined(CONFIG_MX2_VIDEO)
  /*
   * Increase size of DMA-consistent memory region.
   * This is required for i.MX camera driver to capture at least four VGA 
 frames.
   */
  #define CONSISTENT_DMA_SIZE SZ_4M
 -#endif /* CONFIG_MX1_VIDEO */
 +#endif /* CONFIG_MX1_VIDEO || CONFIG_MX2_VIDEO */
  
  #endif /* __ASM_ARCH_MXC_MEMORY_H__ */
 diff --git a/arch/arm/plat-mxc/include/mach/mx2_cam.h 
 b/arch/arm/plat-mxc/include/mach/mx2_cam.h
 new file mode 100644
 index 000..3c080a3
 --- /dev/null
 +++ b/arch/arm/plat-mxc/include/mach/mx2_cam.h
 @@ -0,0 +1,46 @@
 +/*
 + * mx2-cam.h - i.MX27/i.MX25 camera driver header file
 + *
 + * Copyright (C) 2003, Intel Corporation
 + * Copyright (C) 2008, Sascha Hauer s.ha...@pengutronix.de
 + * Copyright (C) 2010, Baruch Siach bar...@tkos.co.il
 + *
 + * This program is free software; you can redistribute it and/or modify
 + * it under the terms of the GNU General Public License as published by
 + * the Free Software Foundation; either version 2 of the License, or
 + * (at your option) any later version.
 + *
 + * 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.
 + */
 +
 +#ifndef __MACH_MX2_CAM_H_
 +#define __MACH_MX2_CAM_H_
 +
 +#define MX2_CAMERA_SWAP16(1  0)
 +#define MX2_CAMERA_EXT_VSYNC (1  1)
 +#define MX2_CAMERA_CCIR  (1  2)
 +#define MX2_CAMERA_CCIR_INTERLACE(1  3)
 +#define MX2_CAMERA_HSYNC_HIGH(1  4)
 +#define MX2_CAMERA_GATED_CLOCK   (1  5)
 +#define MX2_CAMERA_INV_DATA  (1  6)
 +#define MX2_CAMERA_PCLK_SAMPLE_RISING(1  7)
 +#define MX2_CAMERA_PACK_DIR_MSB  (1  8)
 +
 +/**
 + * struct mx2_camera_platform_data - optional platform data for mx2_camera
 + * @flags: any combination of MX2_CAMERA_*
 + * @clk: clock rate of the csi block / 2
 + */
 +struct mx2_camera_platform_data {
 + unsigned long flags;
 + unsigned long clk;
 +};
 +
 +#endif /* __MACH_MX2_CAM_H_ */
 diff --git a/drivers/media/video/Kconfig b/drivers/media/video/Kconfig
 index bdbc9d3..47bf6e6 100644
 --- a/drivers/media/video/Kconfig
 +++ b/drivers/media/video/Kconfig
 @@ -969,6 +969,19 @@ config VIDEO_OMAP2
   ---help---
 This is a v4l2 driver for the TI OMAP2 camera capture interface
  
 +config MX2_VIDEO
 +bool
 +
 +config VIDEO_MX2
 + tristate i.MX27/i.MX25 Camera Sensor Interface driver
 + depends on VIDEO_DEV  SOC_CAMERA  (MACH_MX27 || ARCH_MX25)
 + select VIDEOBUF_DMA_CONTIG
 + select MX2_VIDEO
 + ---help---
 +   This is a v4l2 driver for the i.MX27 and the i.MX25 Camera Sensor
 +   Interface
 +
 +
  #
  # USB Multimedia device configuration
  #
 diff --git a/drivers/media/video/Makefile b/drivers/media/video/Makefile
 index cc93859..b08bd2b 100644
 --- a/drivers/media/video/Makefile
 +++ b/drivers/media/video/Makefile
 @@ -162,6 +162,7 @@ obj-$(CONFIG_SOC_CAMERA)  += soc_camera.o 
 

Re: em28xx/xc3028 - kernel driver vs. Markus Rechberger's driver

2010-06-29 Thread Douglas Schilling Landgraf
Hello,

On Tue, Jun 29, 2010 at 4:42 PM, Torsten Krah
tk...@fachschaft.imn.htwk-leipzig.de wrote:
 Am Dienstag, 29. Juni 2010 schrieb Douglas Schilling Landgraf:
 The rewrite_eeprom.pl is available under git.utils tree:
 http://git.linuxtv.org/v4l-utils.git

 All instructions are available into the source code. Let me know if
 you have any problem with such tool.

 Hi, yes i have problems with the tool :-).

 Connected my broken device:

 lsusb:
 Bus 001 Device 002: ID eb1a:2871 eMPIA Technology, Inc.

 dmesg:
 [  455.348172] usb 1-1: new high speed USB device using ehci_hcd and address 2
 [  455.481791] usb 1-1: configuration #1 chosen from 1 choice
 [  455.609668] usbcore: registered new interface driver snd-usb-audio


 Running the script which does generate the recover script does work.
 But running this one fails with:

 Could not detect i2c bus from any device, run again ./rewrite_eeprom.pl. Did
 you forget to connect the device?
 Modules supported: em28xx saa7134

 Device is connected.

 Anything what i can do?

Could you please verify if you have  the module i2c-dev loaded?

Example:

#lsmod | grep i2c_dev
i2c_dev 6976  0
i2c_core   21104  11
i2c_dev,lgdt330x,tuner_xc2028,tuner,tvp5150,saa7115,em28xx,v4l2_common,videodev,tveeprom,i2c_i801

If yes, please give us the output of:

#i2cdetect -l
i2c-0   smbus   SMBus I801 adapter at ece0  SMBus adapter
i2c-1   smbus   em28xx #0   SMBus adapter
   ^ here my device/driver

Basically, in your case the tool is not able to recognize your device
by i2cdetect.This may happen because i2c_dev module was not able to
load?
If the module is not loaded, please load it manually and give a new try.

I did right now a test with i2c-tools 3.0.0 and 3.0.2.
http://dl.lm-sensors.org/i2c-tools/releases/

Let us know the results.

Cheers
Douglas
--
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: em28xx/xc3028 - kernel driver vs. Markus Rechberger's driver

2010-06-29 Thread Thorsten Hirsch
Hi,

success! I could recover my eeprom with Mauro's rewrite_eeprom.pl.
@Torsten: I also had to modprobe i2c-dev manually. And I even
modprobed i2c-smbus.

Unfortunately the driver (kernel 2.6.34) still doesn't work. There's
no /dev/dvb (even after loading em28xx_dvb manually as it has not been
loaded automatically.

Please have another look at the attached dmesg output.

Thorsten


[ 3481.670969] usb 2-3: new high speed USB device using ehci_hcd and address 5
[ 3481.829797] em28xx: New device TerraTec Electronic GmbH Cinergy T
USB XS @ 480 Mbps (0ccd:0043, interface 0, class 0)
[ 3481.829956] em28xx #0: chip ID is em2870
[ 3481.983457] em28xx #0: i2c eeprom 00: 1a eb 67 95 cd 0c 43 00 c0 12
81 00 6a 24 8e 34
[ 3481.983483] em28xx #0: i2c eeprom 10: 00 00 06 57 02 0c 00 00 00 00
00 00 00 00 00 00
[ 3481.983504] em28xx #0: i2c eeprom 20: 44 00 00 00 f0 10 01 00 00 00
00 00 5b 00 00 00
[ 3481.983525] em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 01 01
00 00 26 3c e3 49
[ 3481.983547] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[ 3481.983568] em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[ 3481.983589] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00
24 03 43 00 69 00
[ 3481.983611] em28xx #0: i2c eeprom 70: 6e 00 65 00 72 00 67 00 79 00
20 00 54 00 20 00
[ 3481.983632] em28xx #0: i2c eeprom 80: 55 00 53 00 42 00 20 00 58 00
53 00 00 00 34 03
[ 3481.983653] em28xx #0: i2c eeprom 90: 54 00 65 00 72 00 72 00 61 00
54 00 65 00 63 00
[ 3481.983675] em28xx #0: i2c eeprom a0: 20 00 45 00 6c 00 65 00 63 00
74 00 72 00 6f 00
[ 3481.983696] em28xx #0: i2c eeprom b0: 6e 00 69 00 63 00 20 00 47 00
6d 00 62 00 48 00
[ 3481.983717] em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[ 3481.983738] em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[ 3481.983759] em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[ 3481.983781] em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[ 3481.983805] em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0x5a1fc1df
[ 3481.983810] em28xx #0: EEPROM info:
[ 3481.983814] em28xx #0:   No audio on board.
[ 3481.983817] em28xx #0:   500mA max power
[ 3481.983823] em28xx #0:   Table at 0x06, strings=0x246a, 0x348e, 0x
[ 3481.984942] em28xx #0: Identified as Terratec Cinergy T XS (card=43)
[ 3481.984947] em28xx #0:
[ 3481.984949]
[ 3481.984953] em28xx #0: The support for this board weren't valid yet.
[ 3481.984958] em28xx #0: Please send a report of having this working
[ 3481.984962] em28xx #0: not to V4L mailing list (and/or to other addresses)
[ 3481.984965]
[ 3481.990805] Chip ID is not zero. It is not a TEA5767
[ 3481.990980] tuner 5-0060: chip found @ 0xc0 (em28xx #0)
[ 3481.991163] xc2028 5-0060: creating new instance
[ 3481.991169] xc2028 5-0060: type set to XCeive xc2028/xc3028 tuner
[ 3481.991182] usb 2-3: firmware: requesting xc3028-v27.fw
[ 3481.998357] xc2028 5-0060: Loading 80 firmware images from
xc3028-v27.fw, type: xc2028 firmware, ver 2.7
[ 3482.052776] xc2028 5-0060: Loading firmware for type=BASE (1), id
.
[ 3483.003956] xc2028 5-0060: Loading firmware for type=(0), id
b700.
[ 3483.018947] SCODE (2000), id b700:
[ 3483.018961] xc2028 5-0060: Loading SCODE for type=MONO SCODE
HAS_IF_4320 (60008000), id 8000.
[ 3483.054451] xc2028 5-0060: Returned an incorrect version. However,
read is not reliable enough. Ignoring it.
[ 3483.220169] em28xx #0: v4l2 driver version 0.1.2
[ 3483.225202] em28xx #0: V4L2 video device registered as video1
[ 3508.137491] Em28xx: Initialized (Em28xx dvb Extension) extension
--
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: [media-ctl] [omap3camera:devel] How to use the app?

2010-06-29 Thread Aguirre, Sergio
Hi Laurent,

 -Original Message-
 From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
 Sent: Tuesday, June 29, 2010 5:23 AM
 To: Aguirre, Sergio
 Cc: Sakari Ailus; linux-media@vger.kernel.org
 Subject: Re: [media-ctl] [omap3camera:devel] How to use the app?
 
 Hi Sergio,
 
 On Tuesday 29 June 2010 01:34:01 Aguirre, Sergio wrote:
  Hi Laurent/Sakari,
 
  I have been attempting to migrate my IMX046 sensor driver, that I had
  working on my Zoom3(OMAP3630 ES1.1) with older codebase, to work with
 the
  latest omap3camera tree, 'devel' branch:
 
  http://gitorious.org/omap3camera/mainline/commits/devel
 
  And for that, I'm trying to also understand how to use your test tool:
  media-ctl:
 
  http://git.ideasonboard.org/?p=media-ctl.git;a=summary
 
  Now, the thing is that, I don't see any guide to learn how to write the
  Proper format for some of the parameters, like to build links in
  interactive mode (-i), or to set formats (-f).
 
  Can you please detail about a typical usage for this tool? (example on
 how
  to build a link, set link format, etc.)
 
 I've pushed a new patch to the media-ctl repository that makes the help
 message a bit more verbose when running media-ctl -h. It describes the
 links
 and formats as follows:
 
 Links and formats are defined as
   link= pad, '-', pad, '[', flags, ']' ;
   format  = pad, '[', fcc, ' ', size, [ ' ', crop ], ']' ;
   pad = entity, ':', pad number ;
   entity  = entity number | ( '\', entity name, '\' ) ;
   size= width, 'x', height ;
   crop= left, ',', top, '/', size ;
 where the fields are
   entity number   Entity numeric identifier
   entity name Entify name (string)
   pad number  Pad numeric identifier
   flags   Link flags (0: inactive, 1: active)
   fcc Format FourCC
   width   Image width in pixels
   height  Image height in pixels
 
 For instance, to set the CCDC to preview link as active, the link
 specifier
 would be
 
 'OMAP3 ISP CCDC:2 - OMAP3 ISP preview:0 [1]'
 
 To set the format on the preview output pad to YUYV 1280x720, the format
 specifier would be
 
 'OMAP3 ISP preview:2 [YUYV 1280x720]'
 
 Spaces are optional.

Thanks a lot for the explanation, and for the verbose help patch!
That's much better :)

 
  So far, my progress is pushed into this branch:
 
  http://dev.omapzoom.org/?p=saaguirre/linux-omap-
 camera.git;a=shortlog;h=ref
  s/heads/mc_migration_wip
 
 Thanks for the link.
 
  And with that, after I boot, I get the following topology:
 
 [snip]
 
 You will find a set of patches that remove the legacy video nodes attached
 to
 this e-mail. They haven't been applied to the omap3camera tree yet, as we
 still haven't fixed all userspace components yet, but they should get
 there in
 a few weeks hopefully. You should probably apply them to your tree to make
 sure you don't start using the legacy video nodes by mistake. They also
 remove
 a lot of code, which is always good, and remove the hardcoded number of
 sensors.

I had following compilation error:

drivers/media/video/isp/ispvideo.c: In function 'isp_video_streamon':
drivers/media/video/isp/ispvideo.c:780: error: 'const struct 
isp_video_operations' has no member named 'stream_off'
drivers/media/video/isp/ispvideo.c:781: error: 'const struct 
isp_video_operations' has no member named 'stream_off'
make[4]: *** [drivers/media/video/isp/ispvideo.o] Error 1
make[3]: *** [drivers/media/video/isp] Error 2
make[3]: *** Waiting for unfinished jobs
make[2]: *** [drivers/media/video] Error 2
make[1]: *** [drivers/media] Error 2
make: *** [drivers] Error 2

Which I solved with the attached patch. You might want to squash it with your 
patch omap3isp: video: Remove the init, cleanup and stream_off operations

I'll continue trying to bring up my sensor, and let you know if I have other 
query.

Thanks for your time!

Regards,
Sergio

 
 --
 Regards,
 
 Laurent Pinchart


0001-SQUASH-omap3isp-video-Remove-the-init-cleanup-and-st.patch
Description: 0001-SQUASH-omap3isp-video-Remove-the-init-cleanup-and-st.patch


laggy remote on x64

2010-06-29 Thread Timothy D. Lenz
I have 2 systems nearly identical except one runs 64bit and the other 
runs 32bit. I'm now trying to use the remote port on the nexus-s card. 
The 32 bit seems to be working ok, but the 64bit acts like it's bussy 
doing somthing else. It randomly won't respond to the remote. It doesn't 
buffer the keys or anything. Wait a moment and maybe it works fine for a 
few presses. When it doesn't respond is highly random. Kernel-2.6.34, 
debian squeeze updated a few days ago, v4l is hg from 06/25/2010

--
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: [PATCHv4 1/3] mx2_camera: Add soc_camera support for i.MX25/i.MX27

2010-06-29 Thread Baruch Siach
On Tue, Jun 29, 2010 at 09:47:42PM +0200, Guennadi Liakhovetski wrote:
 On Mon, 21 Jun 2010, Baruch Siach wrote:
 
  This is the soc_camera support developed by Sascha Hauer for the i.MX27.  
  Alan
  Carvalho de Assis modified the original driver to get it working on more 
  recent
  kernels. I modified it further to add support for i.MX25. This driver has 
  been
  tested on i.MX25 and i.MX27 based platforms.
 
 This looks good to me, thanks! Overflow on eMMA is, probably, still 
 broken, but it will, most probably, remain so, until someone tests and 
 fixes it. One question though: do you know whether this imx/mxc overhaul: 
 http://lists.infradead.org/pipermail/linux-arm-kernel/2010-June/thread.html#18844
  
 affects your driver?

I tested this yesterday, and, unfortunately, it does :(. See 
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-June/019111.html.  
However, this issue does not affect mx27 builds. So I think this should not 
stop the merge of this driver, for now. I hope Uwe and I will find an 
acceptable solution before the .36 merge window opens.

baruch

 I can ask Uwe, but maybe you have an idea or could test your patches with 
 Uwe's git tree?
 
 Thanks
 Guennadi
 
  
  Signed-off-by: Baruch Siach bar...@tkos.co.il
  ---

-- 
 ~. .~   Tk Open Systems
=}ooO--U--Ooo{=
   - bar...@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
--
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