Re: Lenovo webcam problem which using gspca's vc032x driver
2009/7/23 Jean-Francois Moine moin...@free.fr: On Wed, 22 Jul 2009 17:15:15 +0800 AceLan Kao acelan@canonical.com wrote: I would like to know which version of vc032x.c won't make 041e:405b device display upside down. And have you let the 041e:405b device owner to test the SXGA setting and with the 1280x960 resolution? What's the result? Hi AceLan Kao, The 041e:405b had a good display with the current version of vc032x (i.e., including the change 'Webcam 041e:405b added and mi1310_soc updated'). I've just asked the 405b owners to test the XGA resolution. I'll give you the results as soon as I will get them. Best regards. -- Ken ar c'hentañ | ** Breizh ha Linux atav! ** Jef | http://moinejf.free.fr/ Dear Jean-Francois, It sounds like that the Lenovo webcam(0x17ef, 0x4802) sensor and the 0x041e, 0x405b device sensor doesn't be placed at the same direction and the initial tables seems not so compatible. Do you think that it would be better to split the code for these two model of webcams? If yes, I can do some help. Best regards, AceLan Kao. -- Chia-Lin Kao(AceLan) http://blog.acelan.idv.tw/ E-Mail: acelan.kaoATcanonical.com (s/AT/@/) -- 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: New tree with final (?) string control implementation
Hi Hans, On Thu, Jul 23, 2009 at 11:54:46PM +0200, ext Hans Verkuil wrote: Hi Eduardo, I've prepared a new tree: http://www.linuxtv.org/hg/~hverkuil/v4l-dvb-strctrl good. This contains the full string control implementation, including updates to the v4l2-spec, based on the RFC that I posted on Monday. Right. Can you prepare your si4713 patches against this tree and verify that everything is working well? Sure, I've been off work last two weeks. But now I'm back and will get this task soon. If it is, then I can make a pull request for this tree and soon after that you should be able to merge your si4713 driver as well. If I'm not mistaken the string controls API is the only missing bit that prevents your driver from being merged. Yeah. There use to have three dependencies: subdev changes (i2c), modulator capabilities and ext ctl string support. I recall now that subdev is already merged. I'm not sure about the modulator support. Thanks, Hans -- Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom -- Eduardo Valentin -- 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
Technical Details on Abus Digiprotect TV8802 Capture Card
Hi! I am trying to get a capture card working under linux. Ubuntu 8.09 loads bttv module but doesn´t recognize the type of the card - it is not listed on cardlist.bttv . I tried several card=XX options (with mediocre success, e.g. bad grey or green picture from only one input, random change of input by changing between NTSC/PAL) but gave up since the system often froze after closing xawtv. The card is called ABUS Digiprotect TV8802. Windows-software (including drivers and monitoring software) can be found at abus-sc.com (http://www.abus-sc.co.uk/International/Service-Downloads/Software?q=tv8802Send=Search). The card features 4 composite inputs using BNC connectors and one Cinch connector (for Video-Out i think). It has no tuner / radio / remote. There is only one chip Conexant Fusion 878A on the card. lspci identifies vendor=109E product 0878 and vendor=109E product=036E. I installed the original drivers under WinXP and used btspy which gave me the following output: General information: Name:Abus Digiprotect TV8802 Chip: Bt878 , Rev: 0x00 Subsystem: 0x Vendor: Gammagraphx, Inc. Values to MUTE audio: Mute_GPOE : 0x3c7007 Mute_GPDATA: 0x305000 Has TV Tuner: No Number of Composite Ins: 4 Composite in #1 Composite1_Mux : 2 Composite1_GPOE : 0x3c7007 Composite1_GPDATA: 0x305002 Composite in #2 Composite2_Mux : 2 Composite2_GPOE : 0x3c7007 Composite2_GPDATA: 0x305001 Composite in #3 Composite3_Mux : 2 Composite3_GPOE : 0x3c7007 Composite3_GPDATA: 0x305003 Composite in #4 Composite4_Mux : 2 Composite4_GPOE : 0x3c7007 Composite4_GPDATA: 0x305002 Has SVideo: No Has Radio: No What confuses me, are the same values for GPDATA on Composite 1 and 4, but maybe this is a problem with the software i used to select the inputs (i used the software from abus-sc.com). I wasn´t able to use the card using the drivers from btwincap.sf.net, but maybe this is because the software from abus-sc.com needs the original drivers. Maybe someone with more insight can add support for this card. I can do some more testing / research, but need advice on what exactly to do. Best regards Gregor -- Partykeller www.meineparty.at -- 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: New tree with final (?) string control implementation
Hi Hans, On Thu, Jul 23, 2009 at 11:54:46PM +0200, ext Hans Verkuil wrote: Hi Eduardo, I've prepared a new tree: http://www.linuxtv.org/hg/~hverkuil/v4l-dvb-strctrl good. This contains the full string control implementation, including updates to the v4l2-spec, based on the RFC that I posted on Monday. Right. Can you prepare your si4713 patches against this tree and verify that everything is working well? Sure, I've been off work last two weeks. But now I'm back and will get this task soon. If it is, then I can make a pull request for this tree and soon after that you should be able to merge your si4713 driver as well. If I'm not mistaken the string controls API is the only missing bit that prevents your driver from being merged. Yeah. There use to have three dependencies: subdev changes (i2c), modulator capabilities and ext ctl string support. I recall now that subdev is already merged. I'm not sure about the modulator support. That was also merged about a week ago. So this is now the only missing piece. Two things to keep in mind when preparing the new patches: 1) The v4l2-spec documentation on the new string controls must also specify what character encoding is used. In this case you can refer to the RDS standard. 2) In media/video/v4l2-common.c there is a function v4l2_ctrl_is_pointer(). This should return 1 for all string controls. It is needed to ensure that string controls are converted correctly in v4l2-compat-ioctl32.c. Not really an issue on most embedded systems, but on intel platforms it is important to get this right. Regards, Hans -- Hans Verkuil - video4linux developer - sponsored by TANDBERG -- 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: [Bug 13708] Aiptek DV-T300 support is incomplete
Andrew Morton wrote:
The patch doesn't apply to current kernels and fixing it looks non-trivial.
I've attached a patch against the latest git tree.
There's no hurry - please email us a complete (tested, changelogged,
signed-off) patch when you have time to get onto it, thanks.
I can't test it. The patch worked partially with kernel 2.6.29, but I
can't get it working with 2.6.30. With 2.6.29 the driver dies after a
few seconds, but with 2.6.30 the programs won't detect the camera.
Also I only ported the patch to later kernels. I'm not the one who made
it. The patch is originally from the creator of the driver. I also don't
know how v4l works, so I have no idea how to fix the patch.
--- a/zr364xx.c 2009-07-24 12:19:40.0 +0200
+++ b/zr364xx.c 2009-07-24 12:21:14.0 +0200
@@ -59,6 +59,7 @@
#define METHOD0 0
#define METHOD1 1
#define METHOD2 2
+#define METHOD3 3
/* Module parameters */
@@ -95,7 +96,7 @@ static struct usb_device_id device_table
{USB_DEVICE(0x06d6, 0x003b), .driver_info = METHOD0 },
{USB_DEVICE(0x0a17, 0x004e), .driver_info = METHOD2 },
{USB_DEVICE(0x041e, 0x405d), .driver_info = METHOD2 },
- {USB_DEVICE(0x08ca, 0x2102), .driver_info = METHOD2 },
+ {USB_DEVICE(0x08ca, 0x2102), .driver_info = METHOD3 },
{} /* Terminating entry */
};
@@ -213,7 +214,7 @@ static message m2[] = {
};
/* init table */
-static message *init[3] = { m0, m1, m2 };
+static message *init[4] = { m0, m1, m2, m2 };
/* JPEG static data in header (Huffman table, etc) */
@@ -347,6 +348,11 @@ static int read_frame(struct zr364xx_cam
cam-buffer[3], cam-buffer[4], cam-buffer[5],
cam-buffer[6], cam-buffer[7], cam-buffer[8]);
} else {
+ if (ptr + actual_length - jpeg MAX_FRAME_SIZE)
+ {
+DBG(frame too big!);
+return 0;
+ }
memcpy(ptr, cam-buffer, actual_length);
ptr += actual_length;
}
@@ -847,6 +853,22 @@ static int zr364xx_probe(struct usb_inte
m0d1[0] = mode;
m1[2].value = 0xf000 + mode;
m2[1].value = 0xf000 + mode;
+
+ /* special case for METHOD3, the modes are different */
+ if (cam-method == METHOD3) {
+ switch (mode) {
+ case 1:
+ m2[1].value = 0xf000 + 4;
+ break;
+ case 2:
+ m2[1].value = 0xf000 + 0;
+ break;
+ default:
+ m2[1].value = 0xf000 + 1;
+ break;
+ }
+ }
+
header2[437] = cam-height / 256;
header2[438] = cam-height % 256;
header2[439] = cam-width / 256;
[PATCH] stk-webcam: Read buffer overflow
It tested the value of stk_sizes[i].m before checking whether i was in range.
Signed-off-by: Roel Kluin roel.kl...@gmail.com
---
diff --git a/drivers/media/video/stk-webcam.c b/drivers/media/video/stk-webcam.c
index 4d6785e..b154bd9 100644
--- a/drivers/media/video/stk-webcam.c
+++ b/drivers/media/video/stk-webcam.c
@@ -1050,8 +1050,8 @@ static int stk_setup_format(struct stk_camera *dev)
depth = 1;
else
depth = 2;
- while (stk_sizes[i].m != dev-vsettings.mode
-i ARRAY_SIZE(stk_sizes))
+ while (i ARRAY_SIZE(stk_sizes)
+ stk_sizes[i].m != dev-vsettings.mode)
i++;
if (i == ARRAY_SIZE(stk_sizes)) {
STK_ERROR(Something is broken in %s\n, __func__);
--
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 driver crashes device
On Thu, Jul 23, 2009 at 8:59 PM, Mauro Carvalho Chehabmche...@infradead.org wrote: Em Thu, 23 Jul 2009 16:29:02 +0200 Markus Rechberger mrechber...@gmail.com escreveu: On Thu, Jul 23, 2009 at 4:05 PM, Devin Heitmuellerdheitmuel...@kernellabs.com wrote: On Thu, Jul 23, 2009 at 8:10 AM, Markus Rechbergermrechber...@gmail.com wrote: There's a pretty good disclosed detection from Empia available, the linux kernel driver just doesn't support it and very likely will never support it. Instead of doing it the wrong way it's better to turn it off or explicitly ask the user if he wants to do something undefined with his device. The nvidia setup tools also provide an option to force it instead of letting the software just do whatever some developers don't know what it will cause... You don't know what will happen to the device when doing that detection. The initial device in question had to be replugged after we removed the driver from the system. You shouldn't invite people to do undefined things with their hardware so they might break them I think I will submit a few photos what physically can happen to the device with wrong settings. Well, if there is a known heuristic, I would be very happy to get rid of the autodetection logic. I haven't looked at the Empia code in months so I should probably do that. Since I used to design hardware for a living, I am quite familiar with what can happen with incorrect GPIOs so I do not believe you need to attempt to convince me with photos, which is why I am in favor of removing the logic in question. We just need to figure out how to do it without causing a regression in current device support. Interesting... I took a quick look at the code, and it seems like the USB errors occur before we change any GPIOs, and more interesting it appears that the em2861 itself is wedged (which I believe is the first time I've seen that). The code in the log above suggests that the autodetection concluded that the profile was not known, so it did not arbitrarily pick some incorrect device. I am a bit surprised that just reading the eeprom once and doing a scan of the i2c bus would wedge the chip. Is there any information you can give about the board in question in terms of what product it is or what components it contains? it was a simple TVP5150 based device... I do not mean my old code either it's also a failure as I got more information for the new driver after we dropped the old project. As you know the new driver is entirely in Userpace and supported by all involved chipcompanies, it comes with its own LinuxDVB and video4linux2 Stack. Also vendors have a very low interest in supporting those devices in Kernelspace as installing devices which should be sold now are not supported by any distributions. Devices which have been sold one year ago have a very low till no motivation anymore. Most people are simply not able to compile the drivers and/or prepare the kernel development environment just for installing and using a TV Card. PLEASE STOP WITH FUD. THIS FORUM IS FOR OPEN SOURCE DRIVER DISCUSSION. AS YOU DECIDED TO GO TO THE DARK SIDE, PLEASE STOP POSTING HERE OR AT THE OPEN SOURCE #IRC CHANNEL. someone has problems here? We also support available opensource players and will contribute some patches which can be used by all devices. Markus -- 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: Lenovo webcam problem which using gspca's vc032x driver
On Fri, 24 Jul 2009 14:25:33 +0800 AceLan Kao acelan@canonical.com wrote: It sounds like that the Lenovo webcam(0x17ef, 0x4802) sensor and the 0x041e, 0x405b device sensor doesn't be placed at the same direction and the initial tables seems not so compatible. Do you think that it would be better to split the code for these two model of webcams? If yes, I can do some help. Hi Acelan Kao, An other guy with the 405b said that all modes were correct but 640x and 320x upside down. Looking at the .inf of the ms-win driver, it seems that the Mirror and Vertical controls exist for the mi1310_soc sensor. May you change them on ms-win? If yes, may you do a snoop to know which registers do the job? Then, in the vc032x subdriver, only the set h/v flip had to be inverted for the 2 webcam types. Otherwise, I compared the sequences of the ms-win files C0130Dev.inf (041e:405b) and usbvm323.inf (17ef:4802). The bridge sequences are close enough, but the sensors sequences are completely different, as if the sensors were different! So, it is not easy to find how the image may be upside down... BTW, I can't read your binary USB snoop. Have you any tool to read it or may you send me a more readable version? Best regards. -- 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
TT-Connect S2-3650 CI
Hi @all, because i'm building a new TV-Box with a new ATOM-ION-Board which doesnt have any PCI-Slots, i've been searching for a while for an USB-DVB-S-Box with a Common Interface. In the Wiki i found this: http://www.linuxtv.org/wiki/index.php/TechnoTrend_TT-connect_S2-3650_CI. But i'm a bit confused about the line: It is currently unsupported, but experimental support has been attempted. while at the bottom of this wikipage it is stated, that all parts are working, even the CI. Can someone approve that it works completely? And another question about another(?) USB-Box: I found this one: Satelco Easywatch HDTV USB CI, which looks quite similar. Is this the same? Some infos about it (sorry, only in german): http://www.satelco.de/htm/shop/easywatch_usb/details_hdtv_usb_ci.php?s=Produktinfo thanks, Jens -- 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 driver crashes device
Em Fri, 24 Jul 2009 12:54:27 +0200 Markus Rechberger mrechber...@gmail.com escreveu: someone has problems here? We also support available opensource players and will contribute some patches which can be used by all devices. This mailing list, the freenode irc channels #v4l and #linuxtv, the V4L and the LinuxTV mailing lists were created for discussing open source development related to the kernel linux media drivers, the usability of those drivers and related open source themes. Anything related to binary only userspace stuff is completely out of topic and shouldn't be posted on the above places. Despiste what you're saying, your intention to drop support to open source is clear: you are playing against open source since 2007, when you firstly proposed a frontend hook at the kernel driver for userspace. This year, you dropped all open source trees you used to have. So, it is clear that you're out of open source business, and you won't be giving any open source support. So, please stop posting at the open source forums 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: em28xx driver crashes device
On Fri, Jul 24, 2009 at 2:06 PM, Mauro Carvalho Chehabmche...@infradead.org wrote: Em Fri, 24 Jul 2009 12:54:27 +0200 Markus Rechberger mrechber...@gmail.com escreveu: someone has problems here? We also support available opensource players and will contribute some patches which can be used by all devices. Ah well Mauro, This mailing list, the freenode irc channels #v4l and #linuxtv, the V4L and the LinuxTV mailing lists were created for discussing open source development related to the kernel linux media drivers, the usability of those drivers and related open source themes. Anything related to binary only userspace stuff is completely out of topic and shouldn't be posted on the above places. Despiste what you're saying, your intention to drop support to open source is clear: you are playing against open source since 2007, when you firstly proposed a frontend hook at the kernel driver for userspace. This year, you dropped all open source trees you used to have. So, it is clear that you're out of open source business, and you won't be giving any open source support. So, please stop posting at the open source forums there's no reason to argue with you since you have your own ideas. We do give opensource support as well. So please find another target to struggle around with. Let's see who's able to deliver the better solution for endusers. Thanks, Markus -- 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 driver crashes device
Markus Rechberger wrote: there's no reason to argue with you since you have your own ideas. We do give opensource support as well. So please find another target to struggle around with. Let's see who's able to deliver the better solution for endusers. i raise to the bait every so often :-) since when was this a competition? a couple of years ago i bought a device because it was supported then you took you code away and went off and did your own thing i think that was a really immature thing to do you could help with efforts here, but you choose not to either work to add additional functionality to the in-kernel driver or just go away but please (oh please) stop spamming this list with your help -- simon -- 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 driver crashes device
Em Fri, 24 Jul 2009 14:15:16 +0200 Markus Rechberger mrechber...@gmail.com escreveu: On Fri, Jul 24, 2009 at 2:06 PM, Mauro Carvalho Chehabmche...@infradead.org wrote: Em Fri, 24 Jul 2009 12:54:27 +0200 Markus Rechberger mrechber...@gmail.com escreveu: someone has problems here? We also support available opensource players and will contribute some patches which can be used by all devices. Ah well Mauro, This mailing list, the freenode irc channels #v4l and #linuxtv, the V4L and the LinuxTV mailing lists were created for discussing open source development related to the kernel linux media drivers, the usability of those drivers and related open source themes. Anything related to binary only userspace stuff is completely out of topic and shouldn't be posted on the above places. Despiste what you're saying, your intention to drop support to open source is clear: you are playing against open source since 2007, when you firstly proposed a frontend hook at the kernel driver for userspace. This year, you dropped all open source trees you used to have. So, it is clear that you're out of open source business, and you won't be giving any open source support. So, please stop posting at the open source forums there's no reason to argue with you since you have your own ideas. We do give opensource support as well. So please find another target to struggle around with. Let's see who's able to deliver the better solution for endusers. This is not a sort of game to see who has a better solution for end users. A company that has a serious commit to open source opens their datasheets to allow public development and contributions and submit patches regularly upstream, without any userspace hooks. Closed source drivers don't fit well at open source market. There are lots of examples of failures to this approach with all sorts of vendors, and lots of buyers decision of not buying a card X because open source driver doesn't exist or is crappy. Anyway, it might have some space for your driver, but not on this forum. Cheers, Mauro --- What we're saying today is that you're either part of the solution or you're part of the problem. [1968 E. Cleaver Speech (in R. Scheer, Eldridge Cleaver (1969) 32)] -- 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: Problem with My Tuner card
HI Thanks,
But this is confusing for me. Please give a step by step instruction
to do this :
Change the vmux of card = 3 in saa7134-cards.c from one to 3
So you want me to change the line .vmux = 1,--change to
vmux = 3 in kernel source code and recompile the entire kernel ?
There is no other changes required in source code isn't it ?
I am not sure about what you mean by cold boot. Please give simple
instruction to get that done. I am new o this field, so It is
difficult to understand these stuffs that easily.
On Fri, Jul 24, 2009 at 11:36 AM, hermann pittonhermann-pit...@arcor.de wrote:
Hi,
Am Freitag, den 24.07.2009, 10:48 +0530 schrieb unni krishnan:
Hi Unni,
Hi Hermann,
we have lots of saa7130 cards without eeprom on it providing not at
least a valid PCI subvendor and subdevice, so we can't know what it is
at all, neither for the tuner type and also not for how video and audio
inputs are connected.
If you can tell a card with working video and another one with working
audio, it should not be hard to get something together for both on TV
from the tuner as a start.
The option
modprobe saa7134 card=3 tuner=55
gives me sound without much noise but no video
You need the external audio mux gpio switching of the FlyVideo2000
card=3.
This gives me video, but no audio
modprobe saa7134 card=37 tuner=55
But you also need the vmux=3 of card=37 for it.
Change the vmux of card = 3 in saa7134-cards.c from one to 3 and
recompile and install and try again with your maybe tuner.
[SAA7134_BOARD_FLYVIDEO2000] = {
/* TC Wan tc...@cs.usm.my */
.name = LifeView/Typhoon FlyVIDEO2000,
.audio_clock = 0x0020,
.tuner_type = TUNER_LG_PAL_NEW_TAPC,
.radio_type = UNSET,
.tuner_addr = ADDR_UNSET,
.radio_addr = ADDR_UNSET,
.gpiomask = 0xe000,
.inputs = {{
.name = name_tv,
.vmux = 1, --change to vmux = 3
.amux = LINE2,
.gpio = 0x,
.tv = 1,
},{
.name = name_comp1,
.vmux = 0,
.amux = LINE2,
.gpio = 0x4000,
},{
.name = name_comp2,
.vmux = 3,
.amux = LINE2,
.gpio = 0x4000,
},{
.name = name_svideo,
.vmux = 8,
.amux = LINE2,
.gpio = 0x4000,
}},
.radio = {
.name = name_radio,
.amux = LINE2,
.gpio = 0x2000,
},
.mute = {
.name = name_mute,
.amux = LINE2,
.gpio = 0x8000,
},
},
Also, if you do a cold boot without forcing any card, there might be a
slight chance, that the gpio configuration on card init has been seen
previously.
Sorry, do you want me to just reboot the system ? I have already
rebooted the system many times. Is there any other thing that I need
to do before/after reboot ? I am new to Linux devices
If you tried different cards with different gpio configurations
previously, those settings are not cleared, except you take care for it.
Easiest is to do a cold boot, to see the card coming up untouched on
gpios.
I did not care yet, if we have it already duplicate, but likely try to
look it up in the evening here.
Cheers,
Hermann
--
-
With regards,
Unni
A candle loses nothing by lighting another candle
--
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 driver crashes device
On Fri, Jul 24, 2009 at 3:06 PM, Mauro Carvalho Chehabmche...@infradead.org wrote: Em Fri, 24 Jul 2009 14:15:16 +0200 Markus Rechberger mrechber...@gmail.com escreveu: On Fri, Jul 24, 2009 at 2:06 PM, Mauro Carvalho Chehabmche...@infradead.org wrote: Em Fri, 24 Jul 2009 12:54:27 +0200 Markus Rechberger mrechber...@gmail.com escreveu: someone has problems here? We also support available opensource players and will contribute some patches which can be used by all devices. Ah well Mauro, This mailing list, the freenode irc channels #v4l and #linuxtv, the V4L and the LinuxTV mailing lists were created for discussing open source development related to the kernel linux media drivers, the usability of those drivers and related open source themes. Anything related to binary only userspace stuff is completely out of topic and shouldn't be posted on the above places. Despiste what you're saying, your intention to drop support to open source is clear: you are playing against open source since 2007, when you firstly proposed a frontend hook at the kernel driver for userspace. This year, you dropped all open source trees you used to have. So, it is clear that you're out of open source business, and you won't be giving any open source support. So, please stop posting at the open source forums there's no reason to argue with you since you have your own ideas. We do give opensource support as well. So please find another target to struggle around with. Let's see who's able to deliver the better solution for endusers. This is not a sort of game to see who has a better solution for end users. A company that has a serious commit to open source opens their datasheets to allow public development and contributions and submit patches regularly upstream, without any userspace hooks. If a kerneldriver would be required for our devices we now would definitely submit further patches to the kernel, but for USB drivers it is just not necessary at all since the entire driver can work without any complex dependencies in Userspace. Basically the historically grown v4l-dvb kernelapi is just not needed and just limits the customer base as initially pointed out that not everyone is able to compile those drivers. It is still valid for PCI devices probably until IOMMU is available. This has absolutely nothing to do with what you wrote, rather than the em28xx kerneldriver is basically not needed. If you want datasheets of various companies apply there and work for them, everyone's free to do so. regards, Markus -- 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 driver crashes device
Markus Rechberger wrote: On Fri, Jul 24, 2009 at 2:06 PM, Mauro Carvalho Chehabmche...@infradead.org wrote: Em Fri, 24 Jul 2009 12:54:27 +0200 Markus Rechberger mrechber...@gmail.com escreveu: someone has problems here? We also support available opensource players and will contribute some patches which can be used by all devices. Ah well Mauro, This mailing list, the freenode irc channels #v4l and #linuxtv, the V4L and the LinuxTV mailing lists were created for discussing open source development related to the kernel linux media drivers, the usability of those drivers and related open source themes. Anything related to binary only userspace stuff is completely out of topic and shouldn't be posted on the above places. Despiste what you're saying, your intention to drop support to open source is clear: you are playing against open source since 2007, when you firstly proposed a frontend hook at the kernel driver for userspace. This year, you dropped all open source trees you used to have. So, it is clear that you're out of open source business, and you won't be giving any open source support. So, please stop posting at the open source forums there's no reason to argue with you since you have your own ideas. We do give opensource support as well. So please find another target to struggle around with. Let's see who's able to deliver the better solution for endusers. i see that mcentral.de/hg has disappeared -- 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 driver crashes device
Am Freitag 24 Juli 2009 15:06:08 schrieben Sie: Em Fri, 24 Jul 2009 14:15:16 +0200 Markus Rechberger mrechber...@gmail.com escreveu: On Fri, Jul 24, 2009 at 2:06 PM, Mauro Carvalho Chehabmche...@infradead.org wrote: Em Fri, 24 Jul 2009 12:54:27 +0200 Markus Rechberger mrechber...@gmail.com escreveu: someone has problems here? We also support available opensource players and will contribute some patches which can be used by all devices. Ah well Mauro, This mailing list, the freenode irc channels #v4l and #linuxtv, the V4L and the LinuxTV mailing lists were created for discussing open source development related to the kernel linux media drivers, the usability of those drivers and related open source themes. Anything related to binary only userspace stuff is completely out of topic and shouldn't be posted on the above places. Despiste what you're saying, your intention to drop support to open source is clear: you are playing against open source since 2007, when you firstly proposed a frontend hook at the kernel driver for userspace. This year, you dropped all open source trees you used to have. So, it is clear that you're out of open source business, and you won't be giving any open source support. So, please stop posting at the open source forums there's no reason to argue with you since you have your own ideas. We do give opensource support as well. So please find another target to struggle around with. Let's see who's able to deliver the better solution for endusers. This is not a sort of game to see who has a better solution for end users. Wrong! For the user who does not look behind the curtain (and the majority of them do not) the recommended solution wins. The essence of the recommendation is the decisive point, nothing else. A company that has a serious commit to open source opens their datasheets to allow public development and contributions and submit patches regularly upstream, without any userspace hooks. Nonsense! How can you talk about public development if the majority of developers is forced to sign non-disclosure agreements as a necessary precondition to get access to data sheets? Closed source drivers don't fit well at open source market. There are lots of examples of failures to this approach with all sorts of vendors, and lots of buyers decision of not buying a card X because open source driver doesn't exist or is crappy. Dream on baby, I'm sure tomorrow you will tell us all that pigs can fly :) The majority is still MS, and you and I won't change that - unfortunately. Anyway, it might have some space for your driver, but not on this forum. Who gives you the right to say that to anybody? You should perhaps take some lessons about the philosophical basics of open source @ Mister Richard Stallman: There you will learn what freedom in the deeper sense of open source means: It does not mean free beer. But in fact it is equivalent to free speech. And this equivalent to freedom of speech definitely excludes fascistoid small brained gestures like I am the boss or You are not allowed to speak in that forum and other Machoist stupid omnipotence phantasies of that rather poor and primitive no brain kind. Cheers, Mauro --- What we're saying today is that you're either part of the solution or you're part of the problem. [1968 E. Cleaver Speech (in R. Scheer, Eldridge Cleaver (1969) 32)] -- I'd call that fascist crap. And to teach you, Chehab, (and of course all your brothers and sisters in mind) in how far you are a wrong and a completely displaced person I will give you a citation of John Lennon from 1966. It treats the difference of the pure idea of christian religion and small brained human hypocritic practice on the other hand: Jesus was alright, but his disciples were nothing but thick and ordinary. It's them twisting it that ruins it for me. Available here: http://quotationsbook.com/quote/21607/ So everyone reading that who can really think further without external leadership (following the studies of Immanuel Kant) will easily understand in how far Markus' decision to quit linuxtv.org was NOT a pure technical one. To make open source a real fun and pleasure we need large minded, real liberal, progressive thinking maintainers, NOT blind functioning brain-washed soldiers of the rather disgusting primitive fascistoid kind. 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 -- 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: TBS 8920 still fails to initialize - cx24116_readreg error
On 24 июля 2009 05:33:15 Mark Zimmerman wrote: Greetings: Using current current v4l-dvb drivers, I get the following in the dmesg: cx88[1]/2: subsystem: 8920:, board: TBS 8920 DVB-S/S2 [card=72] cx88[1]/2: cx2388x based DVB/ATSC card cx8802_alloc_frontends() allocating 1 frontend(s) cx24116_readreg: reg=0xff (error=-6) cx24116_readreg: reg=0xfe (error=-6) Invalid probe, probably not a CX24116 device cx88[1]/2: frontend initialization failed cx88[1]/2: dvb_register failed (err = -22) cx88[1]/2: cx8802 probe failed, err = -22 Does this mean that one of the chips on this card is different than expected? How can I gather useful information about this? -- Mark -- 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 Hi You can try: http://www.tbsdtv.com/download/tbs6920_8920_v23_linux_x86_x64.rar -- Igor M. Liplianin Microsoft Windows Free Zone - Linux used for all Computing Tasks -- 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: Problem with My Tuner card
at least you will need to recompile the modules that you changed Ho can I do that ? Standard Cold boot Method 1 do a proper shutdown of your computer 2 unplug the power from your system unit 3 make and then drink a cup of tea 4 replug your computer 5 restart your computer I have already done many reboots, that will not solve the issue. - With regards, Unni A candle loses nothing by lighting another candle -- 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 driver crashes device
This mailing list, the freenode irc channels #v4l and #linuxtv, the V4L and the LinuxTV mailing lists were created for discussing open source development related to the kernel linux media drivers, the usability of those drivers and related open source themes. Anything related to binary only userspace stuff is completely out of topic and shouldn't be posted on the above places. Markus, The Linux community supports it's in-kernel dvb / v4l trees using this channel. Your attempt to use these channels to de-value the in-kernel driver and your agenda to promote your (partially) closed source alternative it is off topic. This is not the first time people have had to say this. You're only damaging your reputation further using tactics like this. -- Steven Toth - 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
[PATCHv10 0/8] FM Transmitter (si4713) and another changes
Hello guys, Here is the version 10 of fm transmitter work. The difference between previous version is that now it is based only on http://www.linuxtv.org/hg/~hverkuil/v4l-dvb-strctrl, which contains the string support for our extended control api. Also, I've added a new extended control on the fm tx class: rds deviation. This control was missing from previous versions. It used to be set to default value. But I believe it would be good to have it configurable. Another minor change is about s_frequency call back. In the conversion from sysfs to extended control only interfaces, I forgot to keep the range check. That was missing on version #9. Now it is back. I've removed the v4l2-ctl changes, as they are no longer needed due to last re-factoring which happened there. All ext controls seams to work with v4l2-ctl, including string ones. I've also updated the documentation, including the new control and the references for character encoding of ps name and radio text. Besides that, every thing is the same. There is a needed change in v4l2-ctl regarding set/get frequency. Nowadays, v4l2-ctl queries only the tuner and forgets about modulators. That I will send an initial proposal in a separated patch (I believe it is not related to this series anymore). BR, Eduardo Valentin (8): v4l2-subdev.h: Add g_modulator callbacks to subdev api v4l2: video device: Add V4L2_CTRL_CLASS_FM_TX controls v4l2: video device: Add FM_TX controls default configurations v4l2-spec: Add documentation description for FM TX extended control class FMTx: si4713: Add files to add radio interface for si4713 FMTx: si4713: Add files to handle si4713 i2c device FMTx: si4713: Add Kconfig and Makefile entries FMTx: si4713: Add document file linux/Documentation/video4linux/si4713.txt | 175 +++ linux/drivers/media/radio/Kconfig | 22 + linux/drivers/media/radio/Makefile |2 + linux/drivers/media/radio/radio-si4713.c | 367 + linux/drivers/media/radio/si4713-i2c.c | 2034 linux/drivers/media/radio/si4713-i2c.h | 228 linux/drivers/media/video/v4l2-common.c| 63 +- linux/include/linux/videodev2.h| 34 + linux/include/media/radio-si4713.h | 30 + linux/include/media/si4713.h | 49 + linux/include/media/v4l2-subdev.h |2 + v4l2-spec/Makefile |1 + v4l2-spec/controls.sgml| 210 +++ 13 files changed, 3216 insertions(+), 1 deletions(-) create mode 100644 linux/Documentation/video4linux/si4713.txt create mode 100644 linux/drivers/media/radio/radio-si4713.c create mode 100644 linux/drivers/media/radio/si4713-i2c.c create mode 100644 linux/drivers/media/radio/si4713-i2c.h create mode 100644 linux/include/media/radio-si4713.h create mode 100644 linux/include/media/si4713.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
[PATCHv10 2/8] v4l2: video device: Add V4L2_CTRL_CLASS_FM_TX controls
This patch adds a new class of extended controls. This class
is intended to support FM Radio Modulators properties such as:
rds, audio limiters, audio compression, pilot tone generation,
tuning power levels and preemphasis properties.
Signed-off-by: Eduardo Valentin eduardo.valen...@nokia.com
---
linux/include/linux/videodev2.h | 34 ++
1 files changed, 34 insertions(+), 0 deletions(-)
diff --git a/linux/include/linux/videodev2.h b/linux/include/linux/videodev2.h
index f68d3b1..2e84ec2 100644
--- a/linux/include/linux/videodev2.h
+++ b/linux/include/linux/videodev2.h
@@ -817,6 +817,7 @@ struct v4l2_ext_controls {
#define V4L2_CTRL_CLASS_USER 0x0098/* Old-style 'user' controls */
#define V4L2_CTRL_CLASS_MPEG 0x0099/* MPEG-compression controls */
#define V4L2_CTRL_CLASS_CAMERA 0x009a /* Camera class controls */
+#define V4L2_CTRL_CLASS_FM_TX 0x009b /* FM Modulator control class */
#define V4L2_CTRL_ID_MASK(0x0fff)
#define V4L2_CTRL_ID2CLASS(id)((id) 0x0fffUL)
@@ -1156,6 +1157,39 @@ enum v4l2_exposure_auto_type {
#define V4L2_CID_PRIVACY (V4L2_CID_CAMERA_CLASS_BASE+16)
+/* FM Modulator class control IDs */
+#define V4L2_CID_FM_TX_CLASS_BASE (V4L2_CTRL_CLASS_FM_TX | 0x900)
+#define V4L2_CID_FM_TX_CLASS (V4L2_CTRL_CLASS_FM_TX | 1)
+
+#define V4L2_CID_RDS_TX_PI (V4L2_CID_FM_TX_CLASS_BASE + 1)
+#define V4L2_CID_RDS_TX_PTY(V4L2_CID_FM_TX_CLASS_BASE + 2)
+#define V4L2_CID_RDS_TX_DEVIATION (V4L2_CID_FM_TX_CLASS_BASE + 3)
+#define V4L2_CID_RDS_TX_PS_NAME
(V4L2_CID_FM_TX_CLASS_BASE + 4)
+#define V4L2_CID_RDS_TX_RADIO_TEXT (V4L2_CID_FM_TX_CLASS_BASE + 5)
+
+#define V4L2_CID_AUDIO_LIMITER_ENABLED (V4L2_CID_FM_TX_CLASS_BASE + 6)
+#define V4L2_CID_AUDIO_LIMITER_RELEASE_TIME(V4L2_CID_FM_TX_CLASS_BASE + 7)
+#define V4L2_CID_AUDIO_LIMITER_DEVIATION (V4L2_CID_FM_TX_CLASS_BASE + 8)
+
+#define V4L2_CID_AUDIO_COMPRESSION_ENABLED (V4L2_CID_FM_TX_CLASS_BASE + 9)
+#define V4L2_CID_AUDIO_COMPRESSION_GAIN
(V4L2_CID_FM_TX_CLASS_BASE + 10)
+#define V4L2_CID_AUDIO_COMPRESSION_THRESHOLD (V4L2_CID_FM_TX_CLASS_BASE + 11)
+#define V4L2_CID_AUDIO_COMPRESSION_ATTACK_TIME (V4L2_CID_FM_TX_CLASS_BASE + 12)
+#define V4L2_CID_AUDIO_COMPRESSION_RELEASE_TIME
(V4L2_CID_FM_TX_CLASS_BASE + 13)
+
+#define V4L2_CID_PILOT_TONE_ENABLED(V4L2_CID_FM_TX_CLASS_BASE + 14)
+#define V4L2_CID_PILOT_TONE_DEVIATION (V4L2_CID_FM_TX_CLASS_BASE + 15)
+#define V4L2_CID_PILOT_TONE_FREQUENCY (V4L2_CID_FM_TX_CLASS_BASE + 16)
+
+#define V4L2_CID_FM_TX_PREEMPHASIS (V4L2_CID_FM_TX_CLASS_BASE + 17)
+enum v4l2_preemphasis {
+ V4L2_PREEMPHASIS_DISABLED = 0,
+ V4L2_PREEMPHASIS_50_uS = 1,
+ V4L2_PREEMPHASIS_75_uS = 2,
+};
+#define V4L2_CID_TUNE_POWER_LEVEL (V4L2_CID_FM_TX_CLASS_BASE + 18)
+#define V4L2_CID_TUNE_ANTENNA_CAPACITOR
(V4L2_CID_FM_TX_CLASS_BASE + 19)
+
/*
* T U N I N G
*/
--
1.6.2.GIT
--
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
[PATCHv10 4/8] v4l2-spec: Add documentation description for FM TX extended control class
This single patch adds documentation description for FM Modulator (FM TX) Extended Control Class and its Control IDs. The text was added under Extended Controls section. Signed-off-by: Eduardo Valentin eduardo.valen...@nokia.com --- v4l2-spec/Makefile |1 + v4l2-spec/controls.sgml | 210 +++ 2 files changed, 211 insertions(+), 0 deletions(-) diff --git a/v4l2-spec/Makefile b/v4l2-spec/Makefile index 4f11745..7a8d161 100644 --- a/v4l2-spec/Makefile +++ b/v4l2-spec/Makefile @@ -243,6 +243,7 @@ ENUMS = \ v4l2_power_line_frequency \ v4l2_priority \ v4l2_tuner_type \ + v4l2_preemphasis \ STRUCTS = \ v4l2_audio \ diff --git a/v4l2-spec/controls.sgml b/v4l2-spec/controls.sgml index 8e0e024..791df4d 100644 --- a/v4l2-spec/controls.sgml +++ b/v4l2-spec/controls.sgml @@ -458,6 +458,12 @@ video is actually encoded into that format./para paraUnfortunately, the original control API lacked some features needed for these new uses and so it was extended into the (not terribly originally named) extended control API./para + + paraEven though the MPEG encoding API was the first effort +to use the Extended Control API, nowadays there are also other classes +of Extended Controls, such as Camera Controls and FM Transmitter Controls. +The Extended Controls API as well as all Extended Controls classes are +described in the following text./para /section section @@ -1815,6 +1821,210 @@ control must support read access and may support write access./entry /tgroup /table /section + +section id=fm-tx-controls + titleFM Transmitter Control Reference/title + + paraThe FM Transmitter (FM_TX) class includes controls for common features of +FM transmissions capable devices. Currently this class includes parameters for audio +compression, pilot tone generation, audio deviation limiter, RDS transmission and +tuning power features./para + + table pgwide=1 frame=none id=fm-tx-control-id + titleFM_TX Control IDs/title + + tgroup cols=4 + colspec colname=c1 colwidth=1* + colspec colname=c2 colwidth=6* + colspec colname=c3 colwidth=2* + colspec colname=c4 colwidth=6* + spanspec namest=c1 nameend=c2 spanname=id + spanspec namest=c2 nameend=c4 spanname=descr + thead + row + entry spanname=id align=leftID/entry + entry align=leftType/entry + /rowrow rowsep=1entry spanname=descr align=leftDescription/entry + /row + /thead + tbody valign=top + rowentry/entry/row + row + entry spanname=idconstantV4L2_CID_FM_TX_CLASS/constantnbsp;/entry + entryclass/entry + /rowrowentry spanname=descrThe FM_TX class +descriptor. Calling VIDIOC-QUERYCTRL; for this control will return a +description of this control class./entry + /row + row + entry spanname=idconstantV4L2_CID_RDS_TX_PI/constantnbsp;/entry + entryinteger/entry + /row + rowentry spanname=descrSets the RDS Programme Identification field +for transmission./entry + /row + row + entry spanname=idconstantV4L2_CID_RDS_TX_PTY/constantnbsp;/entry + entryinteger/entry + /row + rowentry spanname=descrSets the RDS Programme Type field for transmission. +This encodes up to 31 pre-defined programme types./entry + /row + row + entry spanname=idconstantV4L2_CID_RDS_TX_DEVIATION/constantnbsp;/entry + entryinteger/entry + /row + rowentry spanname=descrConfigures RDS signal frequency deviation level in Hz. +The range and step are driver-specific./entry + /row + row + entry spanname=idconstantV4L2_CID_RDS_TX_PS_NAME/constantnbsp;/entry + entrystring/entry + /row + rowentry spanname=descrSets the Programme Service name (PS_NAME) for transmission. +It is intended for static display on a receiver. It is the primary aid to listeners in programme service +identification and selection. The use of PS to transmit text other than a single eight character name is +not permitted. In Annex E of xref linkend=en50067, the RDS specification, +there is a full description of the correct character encoding for Programme Service name strings./entry + /row + row + entry spanname=idconstantV4L2_CID_RDS_TX_RADIO_TEXT/constantnbsp;/entry + entrystring/entry + /row + rowentry spanname=descrSets the Radio Text info for transmission. It is a textual description of +what is being broadcasted. RDS Radio Text can be applied when broadcaster wishes to transmit longer PS names, +programme-related information or any other text. In these cases, RadioText should be used in addition to +constantV4L2_CID_RDS_TX_PS_NAME/constant. The encoding for Radio Text strings is also fully
[PATCHv10 3/8] v4l2: video device: Add FM_TX controls default configurations
Signed-off-by: Eduardo Valentin eduardo.valen...@nokia.com
---
linux/drivers/media/video/v4l2-common.c | 63 ++-
1 files changed, 62 insertions(+), 1 deletions(-)
diff --git a/linux/drivers/media/video/v4l2-common.c
b/linux/drivers/media/video/v4l2-common.c
index bd13702..6fc0559 100644
--- a/linux/drivers/media/video/v4l2-common.c
+++ b/linux/drivers/media/video/v4l2-common.c
@@ -343,6 +343,12 @@ const char **v4l2_ctrl_get_menu(u32 id)
Sepia,
NULL
};
+ static const char *fm_tx_preemphasis[] = {
+ No preemphasis,
+ 50 useconds,
+ 75 useconds,
+ NULL,
+ };
switch (id) {
case V4L2_CID_MPEG_AUDIO_SAMPLING_FREQ:
@@ -381,6 +387,8 @@ const char **v4l2_ctrl_get_menu(u32 id)
return camera_exposure_auto;
case V4L2_CID_COLORFX:
return colorfx;
+ case V4L2_CID_FM_TX_PREEMPHASIS:
+ return fm_tx_preemphasis;
default:
return NULL;
}
@@ -479,6 +487,28 @@ const char *v4l2_ctrl_get_name(u32 id)
case V4L2_CID_ZOOM_CONTINUOUS: return Zoom, Continuous;
case V4L2_CID_PRIVACY: return Privacy;
+ /* FM Radio Modulator control */
+ case V4L2_CID_FM_TX_CLASS: return FM Radio Modulator
Controls;
+ case V4L2_CID_RDS_TX_PI:return RDS Program ID;
+ case V4L2_CID_RDS_TX_PTY: return RDS Program Type;
+ case V4L2_CID_RDS_TX_DEVIATION: return RDS Signal Deviation;
+ case V4L2_CID_RDS_TX_PS_NAME: return RDS PS Name;
+ case V4L2_CID_RDS_TX_RADIO_TEXT:return RDS Radio Text;
+ case V4L2_CID_AUDIO_LIMITER_ENABLED:return Audio Limiter Feature
Enabled;
+ case V4L2_CID_AUDIO_LIMITER_RELEASE_TIME: return Audio Limiter Release
Time;
+ case V4L2_CID_AUDIO_LIMITER_DEVIATION: return Audio Limiter
Deviation;
+ case V4L2_CID_AUDIO_COMPRESSION_ENABLED: return Audio Compression
Feature Enabled;
+ case V4L2_CID_AUDIO_COMPRESSION_GAIN: return Audio Compression Gain;
+ case V4L2_CID_AUDIO_COMPRESSION_THRESHOLD: return Audio Compression
Threshold;
+ case V4L2_CID_AUDIO_COMPRESSION_ATTACK_TIME: return Audio Compression
Attack Time;
+ case V4L2_CID_AUDIO_COMPRESSION_RELEASE_TIME: return Audio Compression
Release Time;
+ case V4L2_CID_PILOT_TONE_ENABLED: return Pilot Tone Feature
Enabled;
+ case V4L2_CID_PILOT_TONE_DEVIATION: return Pilot Tone Deviation;
+ case V4L2_CID_PILOT_TONE_FREQUENCY: return Pilot Tone Frequency;
+ case V4L2_CID_FM_TX_PREEMPHASIS:return Pre-emphasis settings;
+ case V4L2_CID_TUNE_POWER_LEVEL: return Tune Power Level;
+ case V4L2_CID_TUNE_ANTENNA_CAPACITOR: return Tune Antenna Capacitor;
+
default:
return NULL;
}
@@ -500,7 +530,18 @@ EXPORT_SYMBOL(v4l2_ctrl_is_value64);
* This information is used inside v4l2_compat_ioctl32. */
int v4l2_ctrl_is_pointer(u32 id)
{
- return 0;
+ int is_pointer;
+
+ switch (id) {
+ case V4L2_CID_RDS_TX_PS_NAME:
+ case V4L2_CID_RDS_TX_RADIO_TEXT:
+ is_pointer = 1;
+ break;
+ default:
+ is_pointer = 0;
+ }
+
+ return is_pointer;
}
EXPORT_SYMBOL(v4l2_ctrl_is_pointer);
@@ -530,6 +571,9 @@ int v4l2_ctrl_query_fill(struct v4l2_queryctrl *qctrl, s32
min, s32 max, s32 ste
case V4L2_CID_EXPOSURE_AUTO_PRIORITY:
case V4L2_CID_FOCUS_AUTO:
case V4L2_CID_PRIVACY:
+ case V4L2_CID_AUDIO_LIMITER_ENABLED:
+ case V4L2_CID_AUDIO_COMPRESSION_ENABLED:
+ case V4L2_CID_PILOT_TONE_ENABLED:
qctrl-type = V4L2_CTRL_TYPE_BOOLEAN;
min = 0;
max = step = 1;
@@ -558,12 +602,18 @@ int v4l2_ctrl_query_fill(struct v4l2_queryctrl *qctrl,
s32 min, s32 max, s32 ste
case V4L2_CID_MPEG_STREAM_VBI_FMT:
case V4L2_CID_EXPOSURE_AUTO:
case V4L2_CID_COLORFX:
+ case V4L2_CID_FM_TX_PREEMPHASIS:
qctrl-type = V4L2_CTRL_TYPE_MENU;
step = 1;
break;
+ case V4L2_CID_RDS_TX_PS_NAME:
+ case V4L2_CID_RDS_TX_RADIO_TEXT:
+ qctrl-type = V4L2_CTRL_TYPE_STRING;
+ break;
case V4L2_CID_USER_CLASS:
case V4L2_CID_CAMERA_CLASS:
case V4L2_CID_MPEG_CLASS:
+ case V4L2_CID_FM_TX_CLASS:
qctrl-type = V4L2_CTRL_TYPE_CTRL_CLASS;
qctrl-flags |= V4L2_CTRL_FLAG_READ_ONLY;
min = max = step = def = 0;
@@ -592,6 +642,17 @@ int v4l2_ctrl_query_fill(struct v4l2_queryctrl *qctrl, s32
min, s32 max, s32 ste
case V4L2_CID_BLUE_BALANCE:
case V4L2_CID_GAMMA:
case
[PATCHv10 5/8] FMTx: si4713: Add files to add radio interface for si4713
This patch adds files which creates the radio interface
for si4713 FM transmitter (modulator) devices.
In order to do the real access to device registers, this
driver uses the v4l2 subdev interface exported by si4713 i2c driver.
Signed-off-by: Eduardo Valentin eduardo.valen...@nokia.com
---
linux/drivers/media/radio/radio-si4713.c | 367 ++
linux/include/media/radio-si4713.h | 30 +++
2 files changed, 397 insertions(+), 0 deletions(-)
create mode 100644 linux/drivers/media/radio/radio-si4713.c
create mode 100644 linux/include/media/radio-si4713.h
diff --git a/linux/drivers/media/radio/radio-si4713.c
b/linux/drivers/media/radio/radio-si4713.c
new file mode 100644
index 000..34c26b7
--- /dev/null
+++ b/linux/drivers/media/radio/radio-si4713.c
@@ -0,0 +1,367 @@
+/*
+ * drivers/media/radio/radio-si4713.c
+ *
+ * Platform Driver for Silicon Labs Si4713 FM Radio Transmitter:
+ *
+ * Copyright (c) 2008 Instituto Nokia de Tecnologia - INdT
+ * Contact: Eduardo Valentin eduardo.valen...@nokia.com
+ *
+ * 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., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ */
+
+#include linux/kernel.h
+#include linux/module.h
+#include linux/init.h
+#include linux/version.h
+#include linux/platform_device.h
+#include linux/i2c.h
+#include linux/videodev2.h
+#include media/v4l2-device.h
+#include media/v4l2-common.h
+#include media/v4l2-ioctl.h
+#include media/radio-si4713.h
+
+/* module parameters */
+static int radio_nr = -1; /* radio device minor (-1 == auto assign) */
+module_param(radio_nr, int, 0);
+MODULE_PARM_DESC(radio_nr,
+Minor number for radio device (-1 == auto assign));
+
+MODULE_LICENSE(GPL);
+MODULE_AUTHOR(Eduardo Valentin eduardo.valen...@nokia.com);
+MODULE_DESCRIPTION(Platform driver for Si4713 FM Radio Transmitter);
+MODULE_VERSION(0.0.1);
+
+/* Driver state struct */
+struct radio_si4713_device {
+ struct v4l2_device v4l2_dev;
+ struct video_device *radio_dev;
+};
+
+/* radio_si4713_fops - file operations interface */
+static const struct v4l2_file_operations radio_si4713_fops = {
+ .owner = THIS_MODULE,
+ .ioctl = video_ioctl2,
+};
+
+/* Video4Linux Interface */
+static int radio_si4713_fill_audout(struct v4l2_audioout *vao)
+{
+ /* TODO: check presence of audio output */
+ strlcpy(vao-name, FM Modulator Audio Out, 32);
+
+ return 0;
+}
+
+static int radio_si4713_enumaudout(struct file *file, void *priv,
+ struct v4l2_audioout *vao)
+{
+ return radio_si4713_fill_audout(vao);
+}
+
+static int radio_si4713_g_audout(struct file *file, void *priv,
+ struct v4l2_audioout *vao)
+{
+ int rval = radio_si4713_fill_audout(vao);
+
+ vao-index = 0;
+
+ return rval;
+}
+
+static int radio_si4713_s_audout(struct file *file, void *priv,
+ struct v4l2_audioout *vao)
+{
+ return vao-index ? -EINVAL : 0;
+}
+
+/* radio_si4713_querycap - query device capabilities */
+static int radio_si4713_querycap(struct file *file, void *priv,
+ struct v4l2_capability *capability)
+{
+ struct radio_si4713_device *rsdev;
+
+ rsdev = video_get_drvdata(video_devdata(file));
+
+ strlcpy(capability-driver, radio-si4713, sizeof(capability-driver));
+ strlcpy(capability-card, Silicon Labs Si4713 Modulator,
+ sizeof(capability-card));
+ capability-capabilities = V4L2_CAP_MODULATOR | V4L2_CAP_RDS_OUTPUT;
+
+ return 0;
+}
+
+/* radio_si4713_queryctrl - enumerate control items */
+static int radio_si4713_queryctrl(struct file *file, void *priv,
+ struct v4l2_queryctrl *qc)
+{
+ /* Must be sorted from low to high control ID! */
+ static const u32 user_ctrls[] = {
+ V4L2_CID_USER_CLASS,
+ V4L2_CID_AUDIO_MUTE,
+ 0
+ };
+
+ /* Must be sorted from low to high control ID! */
+ static const u32 fmtx_ctrls[] = {
+ V4L2_CID_FM_TX_CLASS,
+ V4L2_CID_RDS_TX_PI,
+ V4L2_CID_RDS_TX_PTY,
+ V4L2_CID_RDS_TX_DEVIATION,
+
[PATCHv10 7/8] FMTx: si4713: Add Kconfig and Makefile entries
Simple add Makefile and Kconfig entries. Signed-off-by: Eduardo Valentin eduardo.valen...@nokia.com --- linux/drivers/media/radio/Kconfig | 22 ++ linux/drivers/media/radio/Makefile |2 ++ 2 files changed, 24 insertions(+), 0 deletions(-) diff --git a/linux/drivers/media/radio/Kconfig b/linux/drivers/media/radio/Kconfig index 3315cac..6c6a409 100644 --- a/linux/drivers/media/radio/Kconfig +++ b/linux/drivers/media/radio/Kconfig @@ -339,6 +339,28 @@ config RADIO_ZOLTRIX_PORT help Enter the I/O port of your Zoltrix radio card. +config I2C_SI4713 + tristate I2C driver for Silicon Labs Si4713 device + depends on I2C VIDEO_V4L2 + ---help--- + Say Y here if you want support to Si4713 I2C device. + This device driver supports only i2c bus. + + To compile this driver as a module, choose M here: the + module will be called si4713. + +config RADIO_SI4713 + tristate Silicon Labs Si4713 FM Radio Transmitter support + depends on I2C VIDEO_V4L2 + ---help--- + Say Y here if you want support to Si4713 FM Radio Transmitter. + This device can transmit audio through FM. It can transmit + EDS and EBDS signals as well. This module is the v4l2 radio + interface for the i2c driver of this device. + + To compile this driver as a module, choose M here: the + module will be called radio-si4713. + config USB_DSBR tristate D-Link/GemTek USB FM radio support depends on USB VIDEO_V4L2 diff --git a/linux/drivers/media/radio/Makefile b/linux/drivers/media/radio/Makefile index 0f2b35b..34ae761 100644 --- a/linux/drivers/media/radio/Makefile +++ b/linux/drivers/media/radio/Makefile @@ -15,6 +15,8 @@ obj-$(CONFIG_RADIO_ZOLTRIX) += radio-zoltrix.o obj-$(CONFIG_RADIO_GEMTEK) += radio-gemtek.o obj-$(CONFIG_RADIO_GEMTEK_PCI) += radio-gemtek-pci.o obj-$(CONFIG_RADIO_TRUST) += radio-trust.o +obj-$(CONFIG_I2C_SI4713) += si4713-i2c.o +obj-$(CONFIG_RADIO_SI4713) += radio-si4713.o obj-$(CONFIG_RADIO_MAESTRO) += radio-maestro.o obj-$(CONFIG_USB_DSBR) += dsbr100.o obj-$(CONFIG_USB_SI470X) += radio-si470x.o -- 1.6.2.GIT -- 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
[PATCHv10 8/8] FMTx: si4713: Add document file
This patch adds a document file for si4713 device driver. It describes the driver interfaces and organization. Signed-off-by: Eduardo Valentin eduardo.valen...@nokia.com --- linux/Documentation/video4linux/si4713.txt | 175 1 files changed, 175 insertions(+), 0 deletions(-) create mode 100644 linux/Documentation/video4linux/si4713.txt diff --git a/linux/Documentation/video4linux/si4713.txt b/linux/Documentation/video4linux/si4713.txt new file mode 100644 index 000..3843af5 --- /dev/null +++ b/linux/Documentation/video4linux/si4713.txt @@ -0,0 +1,175 @@ +Driver for I2C radios for the Silicon Labs Si4713 FM Radio Transmitters + +Copyright (c) 2009 Nokia Corporation +Contact: Eduardo Valentin eduardo.valen...@nokia.com + + +Information about the Device + +This chip is a Silicon Labs product. It is a I2C device, currently on 0Ã63 address. +Basically, it has transmission and signal noise level measurement features. + +The Si4713 integrates transmit functions for FM broadcast stereo transmission. +The chip also allows integrated receive power scanning to identify low signal +power FM channels. + +The chip is programmed using commands and responses. There are also several +properties which can change the behavior of this chip. + +Users must comply with local regulations on radio frequency (RF) transmission. + +Device driver description += +There are two modules to handle this device. One is a I2C device driver +and the other is a platform driver. + +The I2C device driver exports a v4l2-subdev interface to the kernel. +All properties can also be accessed by v4l2 extended controls interface, by +using the v4l2-subdev calls (g_ext_ctrls, s_ext_ctrls). + +The platform device driver exports a v4l2 radio device interface to user land. +So, it uses the I2C device driver as a sub device in order to send the user +commands to the actual device. Basically it is a wrapper to the I2C device driver. + +Applications can use v4l2 radio API to specify frequency of operation, mute state, +etc. But mostly of its properties will be present in the extended controls. + +When the v4l2 mute property is set to 1 (true), the driver will turn the chip off. + +Properties description +== + +The properties can be accessed using v4l2 extended controls. +Here is an output from v4l2-ctl util: + +# v4l2-ctl -d /dev/radio0 --all -l +Driver Info: +Driver name : radio-si4713 +Card type : Silicon Labs Si4713 Modulator +Bus info : +Driver version: 0 +Capabilities : 0x00080800 +RDS Output +Modulator +Audio output: 0 (FM Modulator Audio Out) +Frequency: 1545600 (96.60 MHz) +Video Standard = 0x +Modulator: +Name : FM Modulator +Capabilities : 62.5 Hz stereo rds +Frequency range : 76.0 MHz - 108.0 MHz +Available subchannels: mono rds + +User Controls + + mute (bool) : default=1 value=0 + +FM Radio Modulator Controls + + rds_program_id (int) : min=0 max=65535 step=1 default=0 value=0 + rds_program_type (int) : min=0 max=31 step=1 default=0 value=0 +rds_ps_name (str) : value='Si4713 ' len=1024 +' len=1024 rds_radio_text (str) : value='Si4713 + audio_limiter_feature_enabled (bool) : default=1 value=1 + audio_limiter_release_time (int) : min=250 max=102390 step=50 default=5010 value=5010 flags=slider +audio_limiter_deviation (int) : min=0 max=9 step=10 default=66250 value=1020 flags=slider +audio_compression_feature_enabl (bool) : default=1 value=1 + audio_compression_gain (int) : min=0 max=20 step=1 default=15 value=15 flags=slider +audio_compression_threshold (int) : min=-40 max=0 step=1 default=-40 value=-40 flags=slider + audio_compression_attack_time (int) : min=0 max=5000 step=500 default=0 value=0 flags=slider + audio_compression_release_time (int) : min=10 max=100 step=10 default=100 value=100 flags=slider + pilot_tone_feature_enabled (bool) : default=1 value=1 + pilot_tone_deviation (int) : min=0 max=9 step=10 default=6750 value=6750 flags=slider + pilot_tone_frequency (int) : min=0 max=19000 step=1 default=19000 value=19000 flags=slider + pre_emphasis_settings (menu) : min=0 max=2 default=1 value=1 + tune_power_level (int) : min=0 max=120 step=1 default=88 value=120 flags=slider + tune_antenna_capacitor (int) : min=0 max=191 step=1 default=0 value=112 flags=slider + +Here is a summary of them: + +* Pilot is an audible tone sent by the device. + +pilot_frequency - Configures the frequency of the stereo pilot tone. +pilot_deviation - Configures pilot tone frequency deviation level. +pilot_enabled - Enables or disables the pilot tone feature. + +* The si4713 device
[PATCH 1/1] v4l2-ctl: Add G_MODULATOR before set/get frequency
As there can be modulator devices with get/set frequency
callbacks, this patch adds support to them in v4l2-ctl utility.
Signed-off-by: Eduardo Valentin eduardo.valen...@nokia.com
---
v4l2-apps/util/v4l2-ctl.cpp | 10 +-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/v4l2-apps/util/v4l2-ctl.cpp b/v4l2-apps/util/v4l2-ctl.cpp
index fc9e459..ff74177 100644
--- a/v4l2-apps/util/v4l2-ctl.cpp
+++ b/v4l2-apps/util/v4l2-ctl.cpp
@@ -1962,12 +1962,16 @@ int main(int argc, char **argv)
if (options[OptSetFreq]) {
double fac = 16;
+ struct v4l2_modulator mt;
+ memset(mt, 0, sizeof(struct v4l2_modulator));
if (doioctl(fd, VIDIOC_G_TUNER, tuner, VIDIOC_G_TUNER) == 0)
{
fac = (tuner.capability V4L2_TUNER_CAP_LOW) ? 16000 :
16;
+ vf.type = tuner.type;
+ } else if (doioctl(fd, VIDIOC_G_MODULATOR, mt,
VIDIOC_G_MODULATOR) == 0) {
+ fac = (mt.capability V4L2_TUNER_CAP_LOW) ? 16000 : 16;
}
vf.tuner = 0;
- vf.type = tuner.type;
vf.frequency = __u32(freq * fac);
if (doioctl(fd, VIDIOC_S_FREQUENCY, vf,
VIDIOC_S_FREQUENCY) == 0)
@@ -2418,9 +2422,13 @@ set_vid_fmt_error:
if (options[OptGetFreq]) {
double fac = 16;
+ struct v4l2_modulator mt;
+ memset(mt, 0, sizeof(struct v4l2_modulator));
if (doioctl(fd, VIDIOC_G_TUNER, tuner, VIDIOC_G_TUNER) == 0)
{
fac = (tuner.capability V4L2_TUNER_CAP_LOW) ? 16000 :
16;
+ } else if (doioctl(fd, VIDIOC_G_MODULATOR, mt,
VIDIOC_G_MODULATOR) == 0) {
+ fac = (mt.capability V4L2_TUNER_CAP_LOW) ? 16000 : 16;
}
vf.tuner = 0;
if (doioctl(fd, VIDIOC_G_FREQUENCY, vf, VIDIOC_G_FREQUENCY)
== 0)
--
1.6.2.GIT
--
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 driver crashes device
Am Freitag 24 Juli 2009 18:42:58 schrieben Sie: This mailing list, the freenode irc channels #v4l and #linuxtv, the V4L and the LinuxTV mailing lists were created for discussing open source development related to the kernel linux media drivers, the usability of those drivers and related open source themes. Anything related to binary only userspace stuff is completely out of topic and shouldn't be posted on the above places. Markus, The Linux community supports it's in-kernel dvb / v4l trees using this channel. Your attempt to use these channels to de-value the in-kernel driver and your agenda to promote your (partially) closed source alternative it is off topic. Toth, from profound resources I do know that you personally do not know anything about what excesses your highly specific card knowledge, which definitely does not even touch Empia devices at least superficially. In other words: Your personal voice counts absolutely NOTHING as far as the discussed issue is concerned. I would personally suggest you to volunteer as ordinary soldier for Afghanistan sitting in the first row. This is the perfect place of getting rid of small brained reactionary people like you, isn't it? I decide to keep for me what I think about your physiognomy that can be seen on a photograph shot after a Linux conference somewhere in the US. You can call that a rest of politeness... I am not use to people like you in the open source movement, if not to say: I do regard you personally as a displaced impurity. This is not the first time people have had to say this. The authoritarian character (if not to say fascistoid character) described in the studies of Theodor Adorno tends very often to use we or people instead of using the I. This is a proof that the accordant person was kept down from the beginning of childhood, trained to function like a robot without any unsuppressed attempt of thinking freely. Characters of that rather distorted kind very often (but not always) become cops or soldiers as profession to earn their living. You will not help Mauro in his displaced position anyway, Toth! Lessons @ Richard Stallman would possibly help, although I am not too optimistic in your case to be honest.. You're only damaging your reputation further using tactics like this. This is what I call a (stupid) boomerang. Psychologists would call that a projection. The truth about you, Toth, is that you yourself do not only damage your personal reputation by helping reactionary people like Mauro Chehab to betray the open source philosophy in its deepest essence. But in fact you show that you are a mismatch as far as human qualifications are concerned. -- 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.31] V4L/DVB fixes
Linus, Please pull from: ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git for_linus This series adds a new gscpca sub-driver for sn9c20x webcams. There are several popular webcam models supported by those Sonix/Microdia chips. Greg can remove some linuxdriverproject.org requests from the project Wiki after this merge ;) Greg, for the USB ID details, you could take a look at Documentation/video4linux/gspca.txt changes (32 USB ID's added) or at http://linuxtv.org/wiki/index.php/Gspca. With this series, gspca alone supports 660 different webcam models. It has also the following fixes: - gspca: main: Add support for vidioc_g_chip_ident and vidioc_g/s_register; stv06xx-hdcs: update the sensor state, fix a sensor sequence bug and correct the pixelformat; m5602-s5k4aa: Remove erroneous register writes; jpeg subdrivers: Check the result of kmalloc(jpeg header); sonixj: Bad sensor init of non ov76xx sensors. - em28xx: Fixes bugs where webcams are detected, but, since there weren't any sensor code, webcams failed to work; Auto-detect mt9v011 sensors; Added support and autodetection code for mt9m001 sensors; Fixed webcam scaling; make tuning work for Terratec Cinergy T XS USB (mt352 variant); fix typo in mt352 init sequence for Terratec Cinergy T XS USB; make support work for the Pinnacle Hybrid Pro (eb1a:2881); set GPIO properly for Pinnacle Hybrid Pro analog support; Make sure the tuner is initialized if generic empia USB id was used; set demod profile for Pinnacle Hybrid Pro 320e; fix tuning problem in HVR-900 (R1). - mt9v011 (new driver on 2.6.32 added on a previous merge): implement VIDIOC_QUERYCTRL, adds function to calculate fps and adjust the frequency of the used quartz cristal; - af9013: auto-detect parameters in case of garbage given by app; - b2c2-flexcop: regression fix (BZ#13709): properly compile with builtin frontends; - bttv: fix regression: tvaudio must be loaded before tuner; - cx23885-417: fix broken IOCTL handling; - cx23885: check pointers before dereferencing in dprintk macro. Cheers, Mauro. --- Documentation/video4linux/CARDLIST.em28xx|2 +- Documentation/video4linux/gspca.txt | 32 + drivers/media/dvb/b2c2/flexcop-fe-tuner.c| 67 +- drivers/media/dvb/frontends/af9013.c | 25 +- drivers/media/video/bt8xx/bttv-cards.c | 92 +- drivers/media/video/bt8xx/bttv-driver.c |1 + drivers/media/video/bt8xx/bttv.h |1 + drivers/media/video/cx23885/cx23885-417.c|4 +- drivers/media/video/em28xx/em28xx-cards.c| 134 +- drivers/media/video/em28xx/em28xx-core.c | 22 +- drivers/media/video/em28xx/em28xx-dvb.c | 62 +- drivers/media/video/em28xx/em28xx-video.c| 16 +- drivers/media/video/em28xx/em28xx.h | 31 +- drivers/media/video/gspca/Kconfig| 16 + drivers/media/video/gspca/Makefile |2 + drivers/media/video/gspca/conex.c|2 + drivers/media/video/gspca/gspca.c| 73 + drivers/media/video/gspca/gspca.h|9 + drivers/media/video/gspca/m5602/m5602_s5k4aa.c |6 - drivers/media/video/gspca/mars.c |2 + drivers/media/video/gspca/sn9c20x.c | 2434 ++ drivers/media/video/gspca/sonixj.c |4 + drivers/media/video/gspca/spca500.c |2 + drivers/media/video/gspca/stk014.c |2 + drivers/media/video/gspca/stv06xx/stv06xx_hdcs.c | 16 +- drivers/media/video/gspca/sunplus.c |2 + drivers/media/video/gspca/zc3xx.c|2 + drivers/media/video/mt9v011.c| 69 +- include/linux/videodev2.h|1 + include/media/v4l2-chip-ident.h | 12 + 30 files changed, 2973 insertions(+), 170 deletions(-) create mode 100644 drivers/media/video/gspca/sn9c20x.c Antti Palosaari (1): V4L/DVB (12269): af9013: auto-detect parameters in case of garbage given by app Brian Johnson (2): V4L/DVB (12282): gspca - main: Support for vidioc_g_chip_ident and vidioc_g/s_register. V4L/DVB (12283): gspca - sn9c20x: New subdriver for sn9c201 and sn9c202 bridges. Devin Heitmueller (7): V4L/DVB (12257): em28xx: make tuning work for Terratec Cinergy T XS USB (mt352 variant) V4L/DVB (12258): em28xx: fix typo in mt352 init sequence for Terratec Cinergy T XS USB V4L/DVB (12260): em28xx: make support work for the Pinnacle Hybrid Pro (eb1a:2881) V4L/DVB (12261): em28xx: set GPIO properly for Pinnacle Hybrid Pro analog support V4L/DVB (12262): em28xx: Make sure the tuner is
[cron job] v4l-dvb daily build 2.6.22 and up: WARNINGS, 2.6.16-2.6.21: ERRORS
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 Jul 24 19:00:04 CEST 2009 path:http://www.linuxtv.org/hg/v4l-dvb changeset: 12324:6477aa1782d5 gcc version: gcc (GCC) 4.3.1 hardware:x86_64 host os: 2.6.26 linux-2.6.22.19-armv5: OK linux-2.6.23.12-armv5: OK linux-2.6.24.7-armv5: OK linux-2.6.25.11-armv5: OK linux-2.6.26-armv5: OK linux-2.6.27-armv5: OK linux-2.6.28-armv5: OK linux-2.6.29.1-armv5: OK linux-2.6.30-armv5: OK linux-2.6.31-rc3-armv5: OK linux-2.6.27-armv5-ixp: OK linux-2.6.28-armv5-ixp: OK linux-2.6.29.1-armv5-ixp: OK linux-2.6.30-armv5-ixp: OK linux-2.6.31-rc3-armv5-ixp: OK linux-2.6.28-armv5-omap2: OK linux-2.6.29.1-armv5-omap2: OK linux-2.6.30-armv5-omap2: OK linux-2.6.31-rc3-armv5-omap2: OK linux-2.6.22.19-i686: OK linux-2.6.23.12-i686: OK linux-2.6.24.7-i686: OK linux-2.6.25.11-i686: OK linux-2.6.26-i686: OK linux-2.6.27-i686: OK linux-2.6.28-i686: OK linux-2.6.29.1-i686: OK linux-2.6.30-i686: WARNINGS linux-2.6.31-rc3-i686: OK linux-2.6.23.12-m32r: OK linux-2.6.24.7-m32r: OK linux-2.6.25.11-m32r: OK linux-2.6.26-m32r: OK linux-2.6.27-m32r: OK linux-2.6.28-m32r: OK linux-2.6.29.1-m32r: OK linux-2.6.30-m32r: OK linux-2.6.31-rc3-m32r: OK linux-2.6.30-mips: WARNINGS linux-2.6.31-rc3-mips: WARNINGS linux-2.6.27-powerpc64: WARNINGS linux-2.6.28-powerpc64: WARNINGS linux-2.6.29.1-powerpc64: WARNINGS linux-2.6.30-powerpc64: WARNINGS linux-2.6.31-rc3-powerpc64: OK linux-2.6.22.19-x86_64: OK linux-2.6.23.12-x86_64: OK linux-2.6.24.7-x86_64: OK linux-2.6.25.11-x86_64: OK linux-2.6.26-x86_64: OK linux-2.6.27-x86_64: OK linux-2.6.28-x86_64: OK linux-2.6.29.1-x86_64: OK linux-2.6.30-x86_64: WARNINGS linux-2.6.31-rc3-x86_64: OK sparse (linux-2.6.30): OK sparse (linux-2.6.31-rc3): OK linux-2.6.16.61-i686: ERRORS linux-2.6.17.14-i686: ERRORS linux-2.6.18.8-i686: ERRORS linux-2.6.19.5-i686: ERRORS linux-2.6.20.21-i686: OK linux-2.6.21.7-i686: OK linux-2.6.16.61-x86_64: ERRORS linux-2.6.17.14-x86_64: ERRORS linux-2.6.18.8-x86_64: ERRORS linux-2.6.19.5-x86_64: ERRORS linux-2.6.20.21-x86_64: OK linux-2.6.21.7-x86_64: OK 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 V4L2 specification from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/v4l2.html The DVB API specification from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/dvbapi.pdf -- 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 driver crashes device
On 7/24/09 1:34 PM, cyber.bogh wrote: Am Freitag 24 Juli 2009 18:42:58 schrieben Sie: This mailing list, the freenode irc channels #v4l and #linuxtv, the V4L and the LinuxTV mailing lists were created for discussing open source development related to the kernel linux media drivers, the usability of those drivers and related open source themes. Anything related to binary only userspace stuff is completely out of topic and shouldn't be posted on the above places. Markus, The Linux community supports it's in-kernel dvb / v4l trees using this channel. Your attempt to use these channels to de-value the in-kernel driver and your agenda to promote your (partially) closed source alternative it is off topic. Toth, snip But in fact you show that you are a mismatch as far as human qualifications are concerned. This is indeed high praise coming from such a fine and noble gentlemen like yourself. I find myself truly humbled, nay, honored that you've chosen to grace us with your presence and thoughts today. I'm probably not alone when I say that we look forward to your monumental words of wisdom, charm and enlightenment that you've recently chosen to share with us all. You have a true gift and I can only hope that you continue to share it with us all. Happy Christmas, please give my regards to the wife and kids. -- Steven Toth - 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: [GIT PATCHES for 2.6.31] V4L/DVB fixes
On Fri, Jul 24, 2009 at 02:40:20PM -0300, Mauro Carvalho Chehab wrote: Linus, Please pull from: ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git for_linus This series adds a new gscpca sub-driver for sn9c20x webcams. There are several popular webcam models supported by those Sonix/Microdia chips. Greg can remove some linuxdriverproject.org requests from the project Wiki after this merge ;) Greg, for the USB ID details, you could take a look at Documentation/video4linux/gspca.txt changes (32 USB ID's added) or at http://linuxtv.org/wiki/index.php/Gspca. With this series, gspca alone supports 660 different webcam models. That's great to see. As it's a wiki, could someone who knows these ids go through and mark off those devices on the linuxdriverproject.org site? 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: [GIT PATCHES for 2.6.31] V4L/DVB fixes
On Fri, Jul 24, 2009 at 4:50 PM, Greg KHgre...@suse.de wrote: On Fri, Jul 24, 2009 at 02:40:20PM -0300, Mauro Carvalho Chehab wrote: Linus, Please pull from: ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git for_linus This series adds a new gscpca sub-driver for sn9c20x webcams. There are several popular webcam models supported by those Sonix/Microdia chips. Greg can remove some linuxdriverproject.org requests from the project Wiki after this merge ;) Greg, for the USB ID details, you could take a look at Documentation/video4linux/gspca.txt changes (32 USB ID's added) or at http://linuxtv.org/wiki/index.php/Gspca. With this series, gspca alone supports 660 different webcam models. That's great to see. As it's a wiki, could someone who knows these ids go through and mark off those devices on the linuxdriverproject.org site? thanks, greg k-h I looked at it a few weeks ago, and the V4L section is in pretty bad shape. Lots of the devices in DriversNeeded are now supported. http://linuxdriverproject.org/twiki/bin/view/Main/DriversNeeded?sortcol=table;up=#Video_for_Linux_devices_Input I'm going to try to take a pass over it in the next few days and do some cleanup. 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: [GIT PATCHES for 2.6.31] V4L/DVB fixes
On Fri, Jul 24, 2009 at 05:32:23PM -0400, Devin Heitmueller wrote: On Fri, Jul 24, 2009 at 4:50 PM, Greg KHgre...@suse.de wrote: On Fri, Jul 24, 2009 at 02:40:20PM -0300, Mauro Carvalho Chehab wrote: Linus, Please pull from: ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git for_linus This series adds a new gscpca sub-driver for sn9c20x webcams. There are several popular webcam models supported by those Sonix/Microdia chips. Greg can remove some linuxdriverproject.org requests from the project Wiki after this merge ;) Greg, for the USB ID details, you could take a look at Documentation/video4linux/gspca.txt changes (32 USB ID's added) or at http://linuxtv.org/wiki/index.php/Gspca. With this series, gspca alone supports 660 different webcam models. That's great to see. As it's a wiki, could someone who knows these ids go through and mark off those devices on the linuxdriverproject.org site? thanks, greg k-h I looked at it a few weeks ago, and the V4L section is in pretty bad shape. Lots of the devices in DriversNeeded are now supported. http://linuxdriverproject.org/twiki/bin/view/Main/DriversNeeded?sortcol=table;up=#Video_for_Linux_devices_Input I'm going to try to take a pass over it in the next few days and do some cleanup. That would be much appreciated, 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: TBS 8920 still fails to initialize - cx24116_readreg error
On Fri, Jul 24, 2009 at 07:06:11PM +0300, Igor M. Liplianin wrote: On 24 2009 05:33:15 Mark Zimmerman wrote: Greetings: Using current current v4l-dvb drivers, I get the following in the dmesg: cx88[1]/2: subsystem: 8920:, board: TBS 8920 DVB-S/S2 [card=72] cx88[1]/2: cx2388x based DVB/ATSC card cx8802_alloc_frontends() allocating 1 frontend(s) cx24116_readreg: reg=0xff (error=-6) cx24116_readreg: reg=0xfe (error=-6) Invalid probe, probably not a CX24116 device cx88[1]/2: frontend initialization failed cx88[1]/2: dvb_register failed (err = -22) cx88[1]/2: cx8802 probe failed, err = -22 Does this mean that one of the chips on this card is different than expected? How can I gather useful information about this? Hi You can try: http://www.tbsdtv.com/download/tbs6920_8920_v23_linux_x86_x64.rar This code did not compile as-is, but after I commented out some things in drivers I do not need, I managed to build something. The TBS card now seems to be initialized, but it also broke support for my DViCO FusionHDTV7 Dual Express card, which also uses a cx23885. I am going to move this card to another machine that does not have any other capture cards and repeat the process. This should make it easier to know what the TBS card/driver is doing. I am assuming that you are interested in using me to gather information to update the v4l-dvb drivers so that this card can be supported properly. Is this correct? Please let me know what I can do to assist. -- Mark -- 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 driver crashes device
Am Freitag, den 24.07.2009, 12:42 -0400 schrieb Steven Toth: This mailing list, the freenode irc channels #v4l and #linuxtv, the V4L and the LinuxTV mailing lists were created for discussing open source development related to the kernel linux media drivers, the usability of those drivers and related open source themes. Anything related to binary only userspace stuff is completely out of topic and shouldn't be posted on the above places. Markus, The Linux community supports it's in-kernel dvb / v4l trees using this channel. Your attempt to use these channels to de-value the in-kernel driver and your agenda to promote your (partially) closed source alternative it is off topic. This is not the first time people have had to say this. You're only damaging your reputation further using tactics like this. there are also SILVERCREST empia webcams with older revisions of the sensor chip going over the desk here for 5€ already 18 months back. Really interesting bullshit. The vista driver took more than one year to be present ... Great stuff ! Chears, 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
