[PATCH] cx23885: Add support for LEADTEK WinFast PxTV1200.
I tested only tv and composite. Video works fine but no audio.
Signed-off-by: Kusanagi Kouichi
---
Documentation/video4linux/CARDLIST.cx23885 |1 +
drivers/media/video/cx23885/cx23885-cards.c | 32 +++
drivers/media/video/cx23885/cx23885-video.c | 13 +++
drivers/media/video/cx23885/cx23885.h |1 +
4 files changed, 47 insertions(+), 0 deletions(-)
diff --git a/Documentation/video4linux/CARDLIST.cx23885
b/Documentation/video4linux/CARDLIST.cx23885
index 7539e8f..16ca030 100644
--- a/Documentation/video4linux/CARDLIST.cx23885
+++ b/Documentation/video4linux/CARDLIST.cx23885
@@ -26,3 +26,4 @@
25 -> Compro VideoMate E800 [1858:e800]
26 -> Hauppauge WinTV-HVR1290 [0070:8551]
27 -> Mygica X8558 PRO DMB-TH [14f1:8578]
+ 28 -> LEADTEK WinFast PxTV1200[107d:6f22]
diff --git a/drivers/media/video/cx23885/cx23885-cards.c
b/drivers/media/video/cx23885/cx23885-cards.c
index 1ec4816..d639186 100644
--- a/drivers/media/video/cx23885/cx23885-cards.c
+++ b/drivers/media/video/cx23885/cx23885-cards.c
@@ -274,6 +274,31 @@ struct cx23885_board cx23885_boards[] = {
.portb = CX23885_MPEG_DVB,
.portc = CX23885_MPEG_DVB,
},
+ [CX23885_BOARD_LEADTEK_WINFAST_PXTV1200] = {
+ .name = "LEADTEK WinFast PxTV1200",
+ .porta = CX23885_ANALOG_VIDEO,
+ .tuner_type = TUNER_XC2028,
+ .tuner_addr = 0x61,
+ .input = {{
+ .type = CX23885_VMUX_TELEVISION,
+ .vmux = CX25840_VIN2_CH1 |
+ CX25840_VIN5_CH2 |
+ CX25840_NONE0_CH3,
+ }, {
+ .type = CX23885_VMUX_COMPOSITE1,
+ .vmux = CX25840_COMPOSITE1,
+ }, {
+ .type = CX23885_VMUX_SVIDEO,
+ .vmux = CX25840_SVIDEO_LUMA3 |
+ CX25840_SVIDEO_CHROMA4,
+ }, {
+ .type = CX23885_VMUX_COMPONENT,
+ .vmux = CX25840_VIN7_CH1 |
+ CX25840_VIN6_CH2 |
+ CX25840_VIN8_CH3 |
+ CX25840_COMPONENT_ON,
+ } },
+ },
};
const unsigned int cx23885_bcount = ARRAY_SIZE(cx23885_boards);
@@ -417,6 +442,10 @@ struct cx23885_subid cx23885_subids[] = {
.subvendor = 0x14f1,
.subdevice = 0x8578,
.card = CX23885_BOARD_MYGICA_X8558PRO,
+ }, {
+ .subvendor = 0x107d,
+ .subdevice = 0x6f22,
+ .card = CX23885_BOARD_LEADTEK_WINFAST_PXTV1200,
},
};
const unsigned int cx23885_idcount = ARRAY_SIZE(cx23885_subids);
@@ -617,6 +646,7 @@ int cx23885_tuner_callback(void *priv, int component, int
command, int arg)
case CX23885_BOARD_LEADTEK_WINFAST_PXDVR3200_H:
case CX23885_BOARD_COMPRO_VIDEOMATE_E650F:
case CX23885_BOARD_COMPRO_VIDEOMATE_E800:
+ case CX23885_BOARD_LEADTEK_WINFAST_PXTV1200:
/* Tuner Reset Command */
bitmask = 0x04;
break;
@@ -769,6 +799,7 @@ void cx23885_gpio_setup(struct cx23885_dev *dev)
case CX23885_BOARD_LEADTEK_WINFAST_PXDVR3200_H:
case CX23885_BOARD_COMPRO_VIDEOMATE_E650F:
case CX23885_BOARD_COMPRO_VIDEOMATE_E800:
+ case CX23885_BOARD_LEADTEK_WINFAST_PXTV1200:
/* GPIO-2 xc3028 tuner reset */
/* The following GPIO's are on the internal AVCore (cx25840) */
@@ -1076,6 +1107,7 @@ void cx23885_card_setup(struct cx23885_dev *dev)
case CX23885_BOARD_MYGICA_X8506:
case CX23885_BOARD_MAGICPRO_PROHDTVE2:
case CX23885_BOARD_HAUPPAUGE_HVR1290:
+ case CX23885_BOARD_LEADTEK_WINFAST_PXTV1200:
dev->sd_cx25840 = v4l2_i2c_new_subdev(&dev->v4l2_dev,
&dev->i2c_bus[2].i2c_adap,
"cx25840", "cx25840", 0x88 >> 1, NULL);
diff --git a/drivers/media/video/cx23885/cx23885-video.c
b/drivers/media/video/cx23885/cx23885-video.c
index 8934d61..2d3ac8b 100644
--- a/drivers/media/video/cx23885/cx23885-video.c
+++ b/drivers/media/video/cx23885/cx23885-video.c
@@ -36,6 +36,7 @@
#include
#include
#include "cx23885-ioctl.h"
+#include "tuner-xc2028.h"
MODULE_DESCRIPTION("v4l2 driver module for cx23885 based TV cards");
MODULE_AUTHOR("Steven Toth ");
@@ -1505,6 +1506,18 @@ int cx23885_video_register(struct cx23885_dev *dev)
tun_setup.tuner_callback = cx23885_tuner_callback;
v4l2_subdev_call(sd, tuner, s_type_addr, &tun_setup);
+
+ if (dev->board
[PATCH] cx25840: Fix composite detection.
If CX25840_VIN1_CH1 and the like is used, input is not detected as composite. Their value is 0x80XX and CX25840_COMPONENT_ON is 0x8200. So 739 else if ((vid_input & CX25840_COMPONENT_ON) == 0) this condition never be true. Signed-off-by: Kusanagi Kouichi --- drivers/media/video/cx25840/cx25840-core.c |6 ++ 1 files changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/media/video/cx25840/cx25840-core.c b/drivers/media/video/cx25840/cx25840-core.c index 385ecd5..764c811 100644 --- a/drivers/media/video/cx25840/cx25840-core.c +++ b/drivers/media/video/cx25840/cx25840-core.c @@ -734,10 +734,8 @@ static int set_input(struct i2c_client *client, enum cx25840_video_input vid_inp v4l_dbg(1, cx25840_debug, client, "vid_input 0x%x\n", vid_input); reg = vid_input & 0xff; - if ((vid_input & CX25840_SVIDEO_ON) == CX25840_SVIDEO_ON) - is_composite = 0; - else if ((vid_input & CX25840_COMPONENT_ON) == 0) - is_composite = 1; + is_composite = !is_component && + ((vid_input & CX25840_SVIDEO_ON) != CX25840_SVIDEO_ON); v4l_dbg(1, cx25840_debug, client, "mux cfg 0x%x comp=%d\n", reg, is_composite); -- 1.6.6 -- 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: About MPEG decoder interface
Hi, On Fri, Jan 22, 2010 at 6:42 AM, Michael Qiu wrote: > Hi all, > > How can I export my MPEG decoder control interface to user space? > Or in other words, which device file(/dev/xxx) should a proper > driver for mpeg decoder provide? The AV7110 based and the STi7109 based PCI and PCIe devices use /dev/dvb/adapterX/videoY and /dev/dvb/adapterX/osdY and /dev/dvb/adapterX/audioY You can find the relevant headers in include/dvb/video.h, audio.h and osd.h > And, in linux dvb documents, all the frontend interface looks like > /dev/dvb/adapter/xxx, it looks just for PCI based tv card. > If it's not a TV card, but a frontend for a embedded system without > PCI, which interface should I use? The decoder interface is different from the frontend interface. Regards, Manu -- 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: About MPEG decoder interface
On Fri, 2010-01-22 at 10:42 +0800, Michael Qiu wrote: > Hi all, > > How can I export my MPEG decoder control interface to user space? > Or in other words, which device file(/dev/xxx) should a proper > driver for mpeg decoder provide? The MPEG decoder on a PVR-350 PCI card provides a /dev/video interface (normally /dev/video16). The interface specification to userspace is the V4L2 API: http://www.linuxtv.org/downloads/video4linux/API/V4L2_API/spec-single/v4l2.html > And, in linux dvb documents, all the frontend interface looks like > /dev/dvb/adapter/xxx, it looks just for PCI based tv card. > If it's not a TV card, but a frontend for a embedded system without > PCI, which interface should I use? The V4L2 specification should be OK for basic functionality. Hans might be able to talk about more advanced interfaces that are in work for embedded platforms, if the V4L2 API is not good enough for you as is. Regards, Andy > Best regards > Michael Qiu -- 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
About MPEG decoder interface
Hi all, How can I export my MPEG decoder control interface to user space? Or in other words, which device file(/dev/xxx) should a proper driver for mpeg decoder provide? And, in linux dvb documents, all the frontend interface looks like /dev/dvb/adapter/xxx, it looks just for PCI based tv card. If it's not a TV card, but a frontend for a embedded system without PCI, which interface should I use? Best regards Michael Qiu -- 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] [RFC] support for fly dvb duo on medion laptop
Hi. Am Montag, den 18.01.2010, 07:17 +0100 schrieb tomloh...@gmail.com: > Hi list, > > this patch add support for lifeview fly dvb duo (hybrid card) on medion > laptop > > what works : dvb and analogic tv > not tested : svideo, composite, radio (i am not the owner of this card) > > this card uses gpio 22 for the mode switch between analogic and dvb > > gpio settings should change when svideo , composite an radio will be > tested > > > Cheers, > Thomas > > Signed-off-by : Thomas Genty Thomas, if at all, the special on that card should be, and why it did take so long, that this so called "Duo" has only a single hybrid tuner against all other "DUOs" previously with dual tuners IMHO. For what, within the current functions now, you need .i2c_gate = 0x4b ? Please provide output with i2c_debug=1, already previously asked for, to get a better idea about this hardware. 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: [ANNOUNCE] git tree repositories & libv4l
Hans Verkuil wrote: > On Thursday 21 January 2010 03:46:05 Brandon Philips wrote: >> On 00:07 Thu 21 Jan 2010, Mauro Carvalho Chehab wrote: >>> Brandon Philips wrote: >> So here is how I see v4l-utils.git being laid out based on what others >> have said: >> >> libv4l1/ >> libv4l2/ >> libv4lconvert/ >> test/ >> v4l2-dbg/ >> contrib/ >> qv4l2-qt3/ >> qv4l2-qt4/ >> cx25821/ >> etc... everything else > > Hmm. I think I would prefer to have a structure like this: > > lib/ > libv4l1/ > libv4l2/ > libv4lconvert/ I don't have a strong opinion if we should have a /lib dir here or not. > utils/ > v4l2-dbg > v4l2-ctl > cx18-ctl > ivtv-ctl keytable v4l2-sysfs-path parsers/ parse_em28xx.pl parse-sniffusb2.pl > test/ > everything else I like the idea of putting everything else under contrib/ > And everything in lib and utils can be packaged by distros, while contrib > is not packaged. With respect to the parsers (parse_em28xx.pl and parse-sniffusb2.pl), in practice, they seemed more important than the v4l2-dbg, as they help to check what GPIO's are needed to support the USB devices (and it is impractical to send us a non-parsed log, due to its very long size). So, IMO, this should be installed on distros. > What would also be nice is if this project http://v4l-test.sourceforge.net/ > could eventually be merged in v4l2-apps. Agreed. 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
[cron job] v4l-dvb daily build 2.6.22 and up: WARNINGS, 2.6.16-2.6.21: WARNINGS
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 Jan 21 19:00:03 CET 2010 path:http://www.linuxtv.org/hg/v4l-dvb changeset: 14014:e4429a1b736c gcc version: gcc (GCC) 4.3.1 hardware:x86_64 host os: 2.6.26 linux-2.6.30-armv5: OK linux-2.6.31-armv5: OK linux-2.6.32-armv5: OK linux-2.6.33-rc2-armv5: OK linux-2.6.32-armv5-davinci: WARNINGS linux-2.6.33-rc2-armv5-davinci: WARNINGS linux-2.6.30-armv5-ixp: WARNINGS linux-2.6.31-armv5-ixp: WARNINGS linux-2.6.32-armv5-ixp: WARNINGS linux-2.6.33-rc2-armv5-ixp: WARNINGS linux-2.6.30-armv5-omap2: WARNINGS linux-2.6.31-armv5-omap2: WARNINGS linux-2.6.32-armv5-omap2: WARNINGS linux-2.6.33-rc2-armv5-omap2: WARNINGS linux-2.6.22.19-i686: WARNINGS linux-2.6.23.12-i686: WARNINGS linux-2.6.24.7-i686: WARNINGS linux-2.6.25.11-i686: WARNINGS linux-2.6.26-i686: WARNINGS linux-2.6.27-i686: WARNINGS linux-2.6.28-i686: WARNINGS linux-2.6.29.1-i686: WARNINGS linux-2.6.30-i686: WARNINGS linux-2.6.31-i686: WARNINGS linux-2.6.32-i686: WARNINGS linux-2.6.33-rc2-i686: WARNINGS linux-2.6.30-m32r: OK linux-2.6.31-m32r: OK linux-2.6.32-m32r: OK linux-2.6.33-rc2-m32r: OK linux-2.6.30-mips: WARNINGS linux-2.6.31-mips: WARNINGS linux-2.6.32-mips: WARNINGS linux-2.6.33-rc2-mips: WARNINGS linux-2.6.30-powerpc64: WARNINGS linux-2.6.31-powerpc64: WARNINGS linux-2.6.32-powerpc64: WARNINGS linux-2.6.33-rc2-powerpc64: WARNINGS linux-2.6.22.19-x86_64: WARNINGS linux-2.6.23.12-x86_64: WARNINGS linux-2.6.24.7-x86_64: WARNINGS linux-2.6.25.11-x86_64: WARNINGS linux-2.6.26-x86_64: WARNINGS linux-2.6.27-x86_64: WARNINGS linux-2.6.28-x86_64: WARNINGS linux-2.6.29.1-x86_64: WARNINGS linux-2.6.30-x86_64: WARNINGS linux-2.6.31-x86_64: WARNINGS linux-2.6.32-x86_64: WARNINGS linux-2.6.33-rc2-x86_64: WARNINGS spec: OK sparse (linux-2.6.32): ERRORS sparse (linux-2.6.33-rc2): ERRORS linux-2.6.16.61-i686: OK linux-2.6.17.14-i686: OK linux-2.6.18.8-i686: OK linux-2.6.19.5-i686: OK linux-2.6.20.21-i686: WARNINGS linux-2.6.21.7-i686: WARNINGS linux-2.6.16.61-x86_64: OK linux-2.6.17.14-x86_64: OK linux-2.6.18.8-x86_64: OK linux-2.6.19.5-x86_64: OK 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: [ANNOUNCE] git tree repositories & libv4l
Hans Verkuil wrote: > On Thursday 21 January 2010 03:07:32 Mauro Carvalho Chehab wrote: >> Brandon Philips wrote: I've different experience in the projects with git I've used, as long as there are some governance rules (like never ever push -f, always do a rebase fix your stuff and then push, and if something else got in in the window in between rebase again, etc.). >>> If the group of people with commit access is small (3-4) it generally >>> works well. >> Yes. The more people touching at the same tree, the more troubles may happen. >> >> I don't object to allow a limited group of people accessing it, although >> I suspect that, if we open to more than one, we will have more than 4 people >> interested on it. > > In practice the only people who regularly touch v4l2-apps are Hans de Goede > (libv4l), you and myself (v4l2-ctl, v4l2-dbg, qv4l2). I can't remember anyone > else contributing regularly to v4l2-apps. It seems that you forgot me ;) After running the import proccess and have the contributions isolated, it would be easy to double check if nobody else is missed. 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: SSH key parser
Hi Andy, On Thu, Jan 21, 2010 at 6:21 AM, Andy Walls wrote: > On Wed, 2010-01-20 at 16:24 +0400, Manu Abraham wrote: >> Hi all, >> >> I have been working with some T&M applications. Does anybody know of a >> good SSH key parser that I need to use, for remote authentication in >> such applications. Or does SSH sound like using a hammer against a fly >> in such a circumstance ? > > Well, computer and communications security is more than just a good key > parser. It also involves protocols, procedures, audits, proper clocks, > etc. But I digress > > > I don't know what you mean by T&M, but maybe you might find dropbear SSH > useful: I meant Test & Measurement for some debugging applications, which eventually would be Open Source and public. I was looking on the security/authentication aspects of a remote applications and hence SSH. Maybe it might be too big a hammer, but well, without trying, i guess who knows ... > http://matt.ucc.asn.au/dropbear/dropbear.html > > I make no claims as to the secuirty "goodness" of Dropbear SSH; I only > know that it exists. > > Be aware that getting enough entropy in the entropy pool to generate > good host keys on an embedded platform with no mouse or keyboard can be > a problem. But you only have to do that once really, if you never > rotate keys. > > And watch out for those Australian drop-bears, I hear they are deadly. > > Regards, > Andy Thanks. I appreciate your feedback very much. I will try it out soon. Thanks, Manu -- 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: Remote for Terratec Cinergy C PCI HD (DVB-C)
Hi, I got it finally running! I just took the last s2-liplianin source and it was detected automatically: I: Bus=0001 Vendor= Product= Version=0001 N: Name="Mantis VP-2040 IR Receiver" P: Phys=pci-:01:06.0/ir0 S: Sysfs=/devices/virtual/input/input5 U: Uniq= H: Handlers=kbd event5 B: EV=13 B: KEY=108fc330 2842041 0 200018000 21804801 9e96c0 ffc Strange, that it didn't work with v4l-dvb sources. Thank you very much. I really appreciate your work! Regards Hans-Peter Hans-Peter Wolf schrieb: Hi, I installed the mantis driver from the v4l-dvb mercurial repository and got my tv-card Terratec Cinergy C PCI HD running successfully. However, I cannot find any information if the included remote, which also directly connected to the PCI card, is also working. The dmesg output gives me these lines at the startup (not comparable to the lines listed on linuxtv.org): [7.402278] Mantis :01:06.0: PCI INT A -> Link[LNKA] -> GSI 16 (level, low) -> IRQ 16 [7.403356] DVB: registering new adapter (Mantis DVB adapter) [8.322027] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)... (I also had to add the module 'mantis' to /etc/modules to run it automatically at startup. Is this normal?) I also tried cat /proc/bus/input/devices but couldn't find a plausible device (output attached below). Can anyone tell me how to find out if the device is properly installed? Or better: How to install the remote device? Is there any special module required? Thank you very much in advance! Hans-Peter cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: EV=3 B: KEY=10 0 I: Bus=0017 Vendor=0001 Product=0001 Version=0100 N: Name="Macintosh mouse button emulation" P: Phys= S: Sysfs=/devices/virtual/input/input2 U: Uniq= H: Handlers=mouse0 event2 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=/video/input0 S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:12/device:13/input/input3 U: Uniq= H: Handlers=kbd event3 B: EV=3 B: KEY=3f000b 0 0 0 I: Bus=0003 Vendor=046d Product=c01f Version=0110 N: Name="Logitech USB-PS/2 Optical Mouse" P: Phys=usb-:00:02.0-6/input0 S: Sysfs=/devices/pci:00/:00:02.0/usb3/3-6/3-6:1.0/input/input4 U: Uniq= H: Handlers=mouse1 event4 B: EV=17 B: KEY=f 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0003 Vendor=046a Product=0011 Version=0110 N: Name="HID 046a:0011" P: Phys=usb-:00:04.0-6/input0 S: Sysfs=/devices/pci:00/:00:04.0/usb4/4-6/4-6:1.0/input/input5 U: Uniq= H: Handlers=kbd event5 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=7 I: Bus=0001 Vendor=10ec Product=0888 Version=0001 N: Name="HDA Digital PCBeep" P: Phys=card0/codec#0/beep0 S: Sysfs=/devices/pci:00/:00:07.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: EV=40001 B: SND=6 -- 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
updated dvb-t/uk-StocklandHill scan file
I have an updated scan file for uk-StocklandHill for the new settings after the digital switch over. # UK, Stockland Hill # http://www.ukfree.tv/txdetail.php?a=ST222014 T 514167000 8MHz 2/3 1/2 QAM64 8k 1/32 NONE # PSB1 T 490167000 8MHz 2/3 1/2 QAM64 8k 1/32 NONE # PSB2 #T 538167000 8MHz 2/3 1/2 QAM64 8k 1/32 NONE # PSB3 (DVB-T2) T 505833000 8MHz 2/3 1/2 QAM64 8k 1/32 NONE # COM4 T 481833000 8MHz 2/3 1/2 QAM64 8k 1/32 NONE # COM5 T 529833000 8MHz 2/3 1/2 QAM64 8k 1/32 NONE # COM6 I've commented out the line for PSB3, since it's not actually activated yet and when it is, it'll be carrying a DVB-T2 signal. So even once it's up and running, there's nothing out there that supports it as far as I'm aware. There are a couple other transmitters in the south-west that have switched over as well so I'll bug some people on the Devon/Cornwall LUG mailing list to see if I can gather up the rest of them. -- 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: Drivers for Eyetv hybrid
On 21/01/2010 12:07, Markus Rechberger wrote: On Thu, Jan 21, 2010 at 10:55 AM, Morten Friesgaard wrote: To bad. I bought this tuner because of the cross platform compability :-/ Well, it looks awfully alot like the TerraTec H5, would there be a driver this one? http://www.terratec.net/en/products/TerraTec_H5_83188.html just fyi. this Terratec device is not supported. We've been working on a device with equivalent features (DVB-T/C/AnalogTV/VBI/Composite/S-Video/FM-Radio/RDS/Remote Control) http://support.sundtek.com/index.php/topic,4.0.html We are also integrating additional flexible USB CI support for it. Best Regards, Markus Rechberger you just don't give up - do you? -- 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: Conexant Systems, Inc. Hauppauge Inc. HDPVR-1250 model 1196 (rev 04) [How to make it work?]
On Thu, Jan 21, 2010 at 6:02 AM, Philip Downer wrote: > Ukko Happonen wrote: >> >> How do I make the TV tuner work? >> >> lspci -d 14f1:8880 -v says >> Kernel driver in use: cx23885 >> Kernel modules: cx23885 >> > > Looks to me like it's already working. > > Do you have a /dev/dvb/adapter0 dir with anything in it? if so see > http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device Hey Phil, I worked to him a bit on IRC yesterday. The only reason that the cx23885 was loaded was because he forced a modprobe with a card number (with an arbitrary card, btw). This looks like an Avermedia OEM version of the HVR-1200, but I would not be able to say for certain without taking a good look at the card. In order to get this working, a developer would probably have to work through the driver to build a card profile. Cheers, Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.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] Dump Complete DVB Stream, How to Dump Complete DVB Stream
Le jeudi 21 janvier 2010 12:57:00, dvbfreaky 007 a écrit : > Hi , > Can any one suggest me on linux, How to capture/dump/Save complete DVB > Stream( Not elementary Streams). > > To capture elementary stream, I know these > 1. dvbstream -f xx -o pid > /home/user/111/ts -o 8192 > 2. Through VLC also can able to store ( But i am not succeeding all times) > 3. Dumpstream option in mplayer > > > > Is there any application to stream out (via RTP) complete DVB TS throughout > LAN?? > Note: Not elementary Stream Out ( VLC does only Elementary Stream Out) > Can Any one help in this regard? > > please throw your pointers. > > Thanks in Advance, > Santhosh Kumar B > -- Christophe Thommeret -- 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] Dump Complete DVB Stream, How to Dump Complete DVB Stream
Dump pid 8192 to dump the raw ts. Soyeb email: so...@btinternet.com www: http://soyeb.homeip.net From: dvbfreaky 007 To: linux-...@linuxtv.org Sent: Thursday, 21 January, 2010 11:57:00 Subject: [linux-dvb] Dump Complete DVB Stream, How to Dump Complete DVB Stream Hi , Can any one suggest me on linux, How to capture/dump/Save complete DVB Stream( Not elementary Streams). To capture elementary stream, I know these 1. dvbstream -f xx -o pid > /home/user/111/ts 2. Through VLC also can able to store ( But i am not succeeding all times) 3. Dumpstream option in mplayer Is there any application to stream out (via RTP) complete DVB TS throughout LAN?? Note: Not elementary Stream Out ( VLC does only Elementary Stream Out) Can Any one help in this regard? please throw your pointers. Thanks in Advance, Santhosh Kumar B -- 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: TT-Budget/S-1500 PCI crashes with current hg (v4l-dvb-cdcf089168df)
On 01/21/10 15:58, Samuel Rakitnican wrote:
Hi,
for the kernel crash, there was a breakage introduced recently so all
devices with an IR cause a kernel oops without the following patch:
http://patchwork.kernel.org/patch/70126/
Regards
On Thu, 21 Jan 2010 08:47:16 +0100, wrote:
Hi,
My Technotrend S-1500 crashes everytime i load the drivers. This is on
2.6.30.10 kernel with a 2 day old tip from mercurial repo on linuxtv.
Reverting back to an older build seems to succeed but i have other
tuning problems. Looks like a prob in the infrared driver
registration. Is there any way to disable the IR totally as this is a
backend server in a mythtv config. Here's the panic/crash:
I did google before i posted and the patch aforementioned *is* in the
current mercurial source (v4l-dvb-cdcf089168df):
home:/usr/src/mythtv/v4l-dvb-cdcf089168df$ sed -n 121,132p
linux/drivers/media/IR/ir-sysfs.c
/*
* Static device attribute struct with the sysfs attributes for IR's
*/
static DEVICE_ATTR(current_protocol, S_IRUGO | S_IWUSR,
show_protocol, store_protocol);
static struct attribute *ir_dev_attrs[] = {
&dev_attr_current_protocol.attr,
NULL,
};
home:/usr/src/mythtv/v4l-dvb-cdcf089168df$
Any other ideas ?
D
--
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] Dump Complete DVB Stream, How to Dump Complete DVB Stream
dvbfreaky 007 wrote: > Hi , > Can any one suggest me on linux, How to capture/dump/Save complete DVB > Stream( Not elementary Streams). > > To capture elementary stream, I know these > 1. dvbstream -f xx -o pid > /home/user/111/ts > 2. Through VLC also can able to store ( But i am not succeeding all times) > 3. Dumpstream option in mplayer > > > > Is there any application to stream out (via RTP) complete DVB TS > throughout LAN?? > Note: Not elementary Stream Out ( VLC does only Elementary Stream Out) > Can Any one help in this regard? > Hello, MuMuDVB can do it (you have to choose pid 8192) Dvblast can do it dvbstream can do it with pi 8192 (but without RTP) Best regards -- Brice -- 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: Drivers for Eyetv hybrid
On Thu, Jan 21, 2010 at 10:55 AM, Morten Friesgaard wrote: > To bad. I bought this tuner because of the cross platform compability :-/ > > Well, it looks awfully alot like the TerraTec H5, would there be a > driver this one? > http://www.terratec.net/en/products/TerraTec_H5_83188.html > just fyi. this Terratec device is not supported. We've been working on a device with equivalent features (DVB-T/C/AnalogTV/VBI/Composite/S-Video/FM-Radio/RDS/Remote Control) http://support.sundtek.com/index.php/topic,4.0.html We are also integrating additional flexible USB CI support for it. Best Regards, Markus Rechberger -- 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: TT-Budget/S-1500 PCI crashes with current hg (v4l-dvb-cdcf089168df)
Hi, for the kernel crash, there was a breakage introduced recently so all devices with an IR cause a kernel oops without the following patch: http://patchwork.kernel.org/patch/70126/ Regards On Thu, 21 Jan 2010 08:47:16 +0100, wrote: Hi, My Technotrend S-1500 crashes everytime i load the drivers. This is on 2.6.30.10 kernel with a 2 day old tip from mercurial repo on linuxtv. Reverting back to an older build seems to succeed but i have other tuning problems. Looks like a prob in the infrared driver registration. Is there any way to disable the IR totally as this is a backend server in a mythtv config. Here's the panic/crash: Thanks D Jan 21 10:33:54 home kernel: saa7146: unregister extension 'budget_ci dvb'. Jan 21 10:33:54 home kernel: budget_ci dvb :01:06.0: PCI INT A disabled Jan 21 10:33:54 home kernel: saa7146: register extension 'budget_ci dvb'. Jan 21 10:33:54 home kernel: budget_ci dvb :01:06.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11 Jan 21 10:33:54 home kernel: IRQ 11/: IRQF_DISABLED is not guaranteed on shared IRQs Jan 21 10:33:54 home kernel: saa7146: found saa7146 @ mem fb6b6c00 (revision 1, irq 11) (0x13c2,0x1017). Jan 21 10:33:54 home kernel: saa7146 (0): dma buffer size 192512 Jan 21 10:33:54 home kernel: DVB: registering new adapter (TT-Budget/S-1500 PCI) Jan 21 10:33:54 home kernel: adapter has MAC addr = 00:d0:5c:07:98:02 Jan 21 10:33:54 home kernel: input: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci:00/:00:04.0/:01:06.0/ input/input6 Jan 21 10:33:54 home kernel: [ cut here ] Jan 21 10:33:54 home kernel: WARNING: at fs/sysfs/dir.c:487 sysfs_add_one+0x92/0xb0() Jan 21 10:33:54 home kernel: Hardware name: System Product Name Jan 21 10:33:54 home kernel: sysfs: cannot create duplicate filename '/devices/virtual/irrcv/irrcv1' Jan 21 10:33:54 home kernel: Modules linked in: budget_ci(+) budget_core saa7146 mac80211 cfg80211 btusb bluetooth tun snd_ pcm_oss snd_mixer_oss usb_storage uhci_hcd it87 hwmon_vid i2c_dev cx22702 isl6421 cx24116 cx88_dvb cx88_vp3054_i2c wm8775 v ideobuf_dvb lnbp21 stv0299 tuner_simple tuner_types snd_hda_codec_analog tda9887 tda8290 tuner usblp cx8800 cx8802 cx88_als a dvb_core cx88xx v4l2_common ir_common i2c_algo_bit snd_hda_intel ttpci_eeprom nvidia(P) videodev v4l1_compat tveeprom snd_hda_codec i2c_nforce2 ohci_hcd ehci_hcd floppy ir_core videobuf_dma_sg btcx_risc videobuf_core forcedeth i2c_core snd_pcm snd_timer snd snd_page_alloc [last unloaded: saa7146] Jan 21 10:33:54 home kernel: Pid: 1350, comm: modprobe Tainted: P 2.6.30.10 #12 Jan 21 10:33:54 home kernel: Call Trace: Jan 21 10:33:54 home kernel: [] ? sysfs_add_one+0x92/0xb0 Jan 21 10:33:54 home kernel: [] ? sysfs_add_one+0x92/0xb0 Jan 21 10:33:54 home kernel: [] ? warn_slowpath_common+0x6f/0xd0 Jan 21 10:33:54 home kernel: [] ? sysfs_add_one+0x92/0xb0 Jan 21 10:33:54 home kernel: [] ? warn_slowpath_fmt+0x2b/0x30 Jan 21 10:33:54 home kernel: [] ? sysfs_add_one+0x92/0xb0 Jan 21 10:33:54 home kernel: [] ? create_dir+0x48/0x90 Jan 21 10:33:54 home kernel: [] ? sysfs_create_dir+0x29/0x50 Jan 21 10:33:54 home kernel: [] ? kobject_add_internal+0xc2/0x1b0 Jan 21 10:33:54 home kernel: [] ? kobject_add+0x2d/0x60 Jan 21 10:33:54 home kernel: [] ? device_add+0xd7/0x550 Jan 21 10:33:54 home kernel: [] ? kvasprintf+0x45/0x60 Jan 21 10:33:54 home kernel: [] ? kobject_init+0x2a/0xa0 Jan 21 10:33:54 home kernel: [] ? device_create_vargs+0xa9/0xc0 Jan 21 10:33:54 home kernel: [] ? device_create+0x2b/0x30 Jan 21 10:33:54 home kernel: [] ? ir_register_class+0x66/0xd0 [ir_core] Jan 21 10:33:54 home kernel: [] ? ir_input_register+0x1b5/0x290 [ir_core] Jan 21 10:33:54 home kernel: [] ? budget_ci_attach+0x1b2/0xce0 [budget_ci] Jan 21 10:33:54 home kernel: [] ? saa7146_init_one+0x807/0x8d0 [saa7146] Jan 21 10:33:54 home kernel: [] ? iput+0x1d/0x50 Jan 21 10:33:54 home kernel: [] ? sysfs_addrm_finish+0x3a/0x1f0 Jan 21 10:33:54 home kernel: [] ? dma_generic_alloc_coherent+0x0/0x110 Jan 21 10:33:54 home kernel: [] ? dma_generic_alloc_coherent+0x0/0x110 Jan 21 10:33:54 home kernel: [] ? sysfs_do_create_link+0x92/0x110 Jan 21 10:33:54 home kernel: [] ? local_pci_probe+0xb/0x10 Jan 21 10:33:54 home kernel: [] ? pci_device_probe+0x61/0x80 Jan 21 10:33:54 home kernel: [] ? driver_probe_device+0x75/0x180 Jan 21 10:33:54 home kernel: [] ? pci_match_device+0x16/0xb0 Jan 21 10:33:54 home kernel: [] ? __driver_attach+0x79/0x80 Jan 21 10:33:54 home kernel: [] ? pci_device_remove+0x0/0x40 Jan 21 10:33:54 home kernel: [] ? bus_for_each_dev+0x49/0x70 Jan 21 10:33:54 home kernel: [] ? pci_device_remove+0x0/0x40 Jan 21 10:33:54 home kernel: [] ? driver_attach+0x16/0x20 Jan 21 10:33:54 home kernel: [] ? __driver_attach+0x0/0x80 Jan 21 10:33:54 home kernel: [] ? bus_add_driver+0xaf/0x220 Jan 21 10:33:54 home kernel: [] ? pci_device_remove+0x0/0x40 Jan 21 10:33:54 home kernel: [] ? driver_register+
Re: Conexant Systems, Inc. Hauppauge Inc. HDPVR-1250 model 1196 (rev 04) [How to make it work?]
Ukko Happonen wrote: How do I make the TV tuner work? lspci -d 14f1:8880 -v says Kernel driver in use: cx23885 Kernel modules: cx23885 Looks to me like it's already working. Do you have a /dev/dvb/adapter0 dir with anything in it? if so see http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device Phil -- 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: bt878 card: no sound and only xvideo support in 2.6.31 bttv 0.9.18
On Thu, Jan 21, 2010 at 09:05:06AM +0100, LiM wrote: > Hello, > > i have the same problem as > http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/11441 > also with Hercules Smart TV Stereo .. > works OK audio+video on ..2.6.29-gentoo-r5 + bttv 0.9.17 > but NO AUDIO on linux-2.6.31-gentoo-r6 + bttv 0.9.18 > > cat /etc/modprobe.d/bttv.conf > options tvaudio tda9874a=1 tda9874a_STD=0 > options bttv radio=0 card=100 tuner=29 gbuffers=14 i2c_udelay=128 pll=1 > autoload=1 > > 2.6.29-gentoo-r5 + bttv 0.9.17 > bttv: driver version 0.9.17 loaded > bttv: using 14 buffers with 2080k (520 pages) each for capture > bttv: Bt8xx card found (0). > bttv :04:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > bttv0: Bt878 (rev 17) at :04:01.0, irq: 16, latency: 64, mmio: > 0xf8ffe000 > bttv0: using: Hercules Smart TV Stereo [card=100,insmod option] > IRQ 16/bttv0: IRQF_DISABLED is not guaranteed on shared IRQs > bttv0: gpio: en=, out= in=00ff [init] > tvaudio' 6-0058: found tda9874a. > tvaudio' 6-0058: tda9874h/a found @ 0xb0 (bt878 #0 [sw]) > tvaudio' 6-004b: pic16c54 (PV951) found @ 0x96 (bt878 #0 [sw]) > bttv0: tuner type=29 > bttv0: i2c: checking for TDA9875 @ 0xb0... found > bttv0: i2c: checking for TDA7432 @ 0x8a... not found > All bytes are equal. It is not a TEA5767 > tuner' 6-0060: chip found @ 0xc0 (bt878 #0 [sw]) > tuner-simple 6-0060: creating new instance > tuner-simple 6-0060: type set to 29 (LG PAL_BG (TPI8PSB11D)) > bttv0: registered device video1 > bttv0: registered device vbi0 > bttv0: PLL: 28636363 => 35468950 .. ok > > linux-2.6.31-gentoo-r6 + bttv 0.9.18 > bttv: driver version 0.9.18 loaded > bttv: using 14 buffers with 2080k (520 pages) each for capture > bttv: Bt8xx card found (0). > bttv0: Bt878 (rev 17) at :04:01.0, irq: 16, latency: 64, mmio: > 0xf8ffe000 > bttv0: using: Hercules Smart TV Stereo [card=100,insmod option] > IRQ 16/bttv0: IRQF_DISABLED is not guaranteed on shared IRQs > bttv0: gpio: en=, out= in=00ff [init] > bttv0: tuner type=29 > tvaudio 0-0058: found tda9874a. > tvaudio 0-0058: tda9874h/a found @ 0xb0 (bt878 #0 [sw]) > All bytes are equal. It is not a TEA5767 > tuner 0-0060: chip found @ 0xc0 (bt878 #0 [sw]) > tuner-simple 0-0060: creating new instance > tuner-simple 0-0060: type set to 29 (LG PAL_BG (TPI8PSB11D)) > bttv0: registered device video0 > bttv0: registered device vbi0 > bttv0: PLL: 28636363 => 35468950 . > bttv0: PLL: 28636363 => 35468950 . > bttv0: PLL: 28636363 => 35468950 . ok > > > I think problem is in new bttv driver, in modules is new options > audiodev and tvaudio is loading with bttv? and this line: > "tvaudio' 6-004b: pic16c54 (PV951) found @ 0x96 (bt878 #0 [sw])" > is only with older bttv. > > modinfo -k 2.6.31-gentoo-r6 bttv > ---cut-- > parm: autoload:obsolete option, please do not use anymore (int) > parm: audiodev:specify audio device: > -1 = no audio > 0 = autodetect (default) > 1 = msp3400 > 2 = tda7432 > 3 = tvaudio (array of int) > ---cut-- > > How can i load module with new bttv to get sound working? > > rdgs > > Michal Vesely > > -- > 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 For my Hercules Smart TV card sound also disappeared after 2.6.29 with the message:"bttv0: audio absent, no audio device found!" I have bisected the problem to commit 859f0277a6c3ba59b0a5a1eb183f8f6ce661a95d: "bttv: convert to v4l2_subdev since i2c autoprobing will disappear" If I revert this everything works again -- 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: Drivers for Eyetv hybrid
To bad. I bought this tuner because of the cross platform compability :-/ Well, it looks awfully alot like the TerraTec H5, would there be a driver this one? http://www.terratec.net/en/products/TerraTec_H5_83188.html How hard is it to create a driver myself? I'm an engineer, have some knowlege with building the linux kernel, patching firmware etc. /Morten On Wed, Jan 20, 2010 at 7:00 PM, Devin Heitmueller wrote: > On Wed, Jan 20, 2010 at 12:26 PM, Morten Friesgaard > wrote: >> Hello. >> I installed mythbuntu 9.10 this week on some old hardware, I had a >> Hauppauge 500MCE PVR in and made it work fairly easy. I'm used to >> gentoo >> >> However, I want to record HD signal, so I plugged in a Eyetv hybrid >> and followed this guide >> http://ubuntuforums.org/showthread.php?t=1015387 >> >> I extracted the driver, put it in into /lib/firmware, modprobed >> em28xx, rebooted. When I plug in the device, it is not recognised. I >> tried both usb ports. The ID is "0fd9:0018", which is somewhat >> different from similar hardware e.g. Hauppauge wintv-hvr-950 (ID >> 2040:6513 http://www.linuxtv.org/wiki/index.ph..._WinTV-HVR-950 ) > > It's a totally different hardware design, nothing like the older > version of the EyeTV Hybrid (which was just a clone of the HVR-950). > > It is unsupported currently (and nobody is working on it to my knowledge). > > Devin > > -- > Devin J. Heitmueller - Kernel Labs > http://www.kernellabs.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
bt878 card: no sound and only xvideo support in 2.6.31 bttv 0.9.18
Hello, i have the same problem as http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/11441 also with Hercules Smart TV Stereo .. works OK audio+video on ..2.6.29-gentoo-r5 + bttv 0.9.17 but NO AUDIO on linux-2.6.31-gentoo-r6 + bttv 0.9.18 cat /etc/modprobe.d/bttv.conf options tvaudio tda9874a=1 tda9874a_STD=0 options bttv radio=0 card=100 tuner=29 gbuffers=14 i2c_udelay=128 pll=1 autoload=1 2.6.29-gentoo-r5 + bttv 0.9.17 bttv: driver version 0.9.17 loaded bttv: using 14 buffers with 2080k (520 pages) each for capture bttv: Bt8xx card found (0). bttv :04:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 bttv0: Bt878 (rev 17) at :04:01.0, irq: 16, latency: 64, mmio: 0xf8ffe000 bttv0: using: Hercules Smart TV Stereo [card=100,insmod option] IRQ 16/bttv0: IRQF_DISABLED is not guaranteed on shared IRQs bttv0: gpio: en=, out= in=00ff [init] tvaudio' 6-0058: found tda9874a. tvaudio' 6-0058: tda9874h/a found @ 0xb0 (bt878 #0 [sw]) tvaudio' 6-004b: pic16c54 (PV951) found @ 0x96 (bt878 #0 [sw]) bttv0: tuner type=29 bttv0: i2c: checking for TDA9875 @ 0xb0... found bttv0: i2c: checking for TDA7432 @ 0x8a... not found All bytes are equal. It is not a TEA5767 tuner' 6-0060: chip found @ 0xc0 (bt878 #0 [sw]) tuner-simple 6-0060: creating new instance tuner-simple 6-0060: type set to 29 (LG PAL_BG (TPI8PSB11D)) bttv0: registered device video1 bttv0: registered device vbi0 bttv0: PLL: 28636363 => 35468950 .. ok linux-2.6.31-gentoo-r6 + bttv 0.9.18 bttv: driver version 0.9.18 loaded bttv: using 14 buffers with 2080k (520 pages) each for capture bttv: Bt8xx card found (0). bttv0: Bt878 (rev 17) at :04:01.0, irq: 16, latency: 64, mmio: 0xf8ffe000 bttv0: using: Hercules Smart TV Stereo [card=100,insmod option] IRQ 16/bttv0: IRQF_DISABLED is not guaranteed on shared IRQs bttv0: gpio: en=, out= in=00ff [init] bttv0: tuner type=29 tvaudio 0-0058: found tda9874a. tvaudio 0-0058: tda9874h/a found @ 0xb0 (bt878 #0 [sw]) All bytes are equal. It is not a TEA5767 tuner 0-0060: chip found @ 0xc0 (bt878 #0 [sw]) tuner-simple 0-0060: creating new instance tuner-simple 0-0060: type set to 29 (LG PAL_BG (TPI8PSB11D)) bttv0: registered device video0 bttv0: registered device vbi0 bttv0: PLL: 28636363 => 35468950 . bttv0: PLL: 28636363 => 35468950 . bttv0: PLL: 28636363 => 35468950 . ok I think problem is in new bttv driver, in modules is new options audiodev and tvaudio is loading with bttv? and this line: "tvaudio' 6-004b: pic16c54 (PV951) found @ 0x96 (bt878 #0 [sw])" is only with older bttv. modinfo -k 2.6.31-gentoo-r6 bttv ---cut-- parm: autoload:obsolete option, please do not use anymore (int) parm: audiodev:specify audio device: -1 = no audio 0 = autodetect (default) 1 = msp3400 2 = tda7432 3 = tvaudio (array of int) ---cut-- How can i load module with new bttv to get sound working? rdgs Michal Vesely -- 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] MT9T031: write xskip and yskip at each set_params call
Guennadi Liakhovetski wrote:
On Wed, 20 Jan 2010, Valentin Longchamp wrote:
This prevents the registers to be different to the computed values
the second time you open the same camera with the sames parameters.
The images were different between the first device open and the
second one with the same parameters.
But why they were different? Weren't xskip and yskip preserved from the
previous S_CROP / S_FMT configuration? If so, then, I am afraid, this is
the behaviour, mandated by the API, and as such shall not be changed. Or
have I misunderstood you?
Here are more details about what I debugged:
First more details about what I do with the camera: I open the device,
issue the S_CROP / S_FMT calls and read images, the behaviour is fine,
then close the device.
Then if I reopen the device, reissue the S_CROP / S_FMT calls with the
same params, but the images is not the sames because of different xskip
and yskip. From what I have debugged in the driver at the second S_CROP
/S_FMT, xskip and yskip are computed by mt9t031_skip (and have the same
value that the one stored in the mt9t031 struct) and thus with the
current code are not rewritten.
However, if I read the register values containing bin and skip values on
the camera chip they have been reset (does a open/close do some reset to
the cam ?) and thus different than the ones that should be written.
I hope this clarifies the problem that I am experiencing. I don't think
that the API wants you to get two different images when you open the
device and issue the same parameters twice.
Best Regards
Val
Thanks
Guennadi
Signed-off-by: Valentin Longchamp
---
drivers/media/video/mt9t031.c | 17 -
1 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/drivers/media/video/mt9t031.c b/drivers/media/video/mt9t031.c
index a9061bf..e4a9095 100644
--- a/drivers/media/video/mt9t031.c
+++ b/drivers/media/video/mt9t031.c
@@ -17,6 +17,7 @@
#include
#include
+
/*
* mt9t031 i2c address 0x5d
* The platform has to define i2c_board_info and link to it from
@@ -337,15 +338,13 @@ static int mt9t031_set_params(struct i2c_client *client,
if (ret >= 0)
ret = reg_write(client, MT9T031_VERTICAL_BLANKING, vblank);
- if (yskip != mt9t031->yskip || xskip != mt9t031->xskip) {
- /* Binning, skipping */
- if (ret >= 0)
- ret = reg_write(client, MT9T031_COLUMN_ADDRESS_MODE,
- ((xbin - 1) << 4) | (xskip - 1));
- if (ret >= 0)
- ret = reg_write(client, MT9T031_ROW_ADDRESS_MODE,
- ((ybin - 1) << 4) | (yskip - 1));
- }
+ /* Binning, skipping */
+ if (ret >= 0)
+ ret = reg_write(client, MT9T031_COLUMN_ADDRESS_MODE,
+ ((xbin - 1) << 4) | (xskip - 1));
+ if (ret >= 0)
+ ret = reg_write(client, MT9T031_ROW_ADDRESS_MODE,
+ ((ybin - 1) << 4) | (yskip - 1));
dev_dbg(&client->dev, "new physical left %u, top %u\n",
rect->left, rect->top);
--
1.6.3.3
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longch...@epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEB3494, Station 9, CH-1015 Lausanne
--
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
