Re: TBS 8920 still fails to initialize - cx24116_readreg error
On 25 июля 2009 05:22:06 Mark Zimmerman wrote: > 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. I've changed tbs 8920 initialization in http://mercurial.intuxication.org/hg/s2-liplianin. I ask you to try it. If it works, then I will commit it to linuxv. Also pay attention to remote. > > -- 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 -- 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
linuxtv.org downtime today due to software updates
Hi, sorry for short notice, but today I have enough spare time to do the long overdue Etch -> Lenny update on linuxtv.org. ssh and http access wil be blocked during the update. I'll start in one or two hours from now and expect it to take about two hours. Cheers, Johannes -- 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] Help Request: DM1105 STV0299 DVB-S PCI - Unable to tune
On 26 июля 2009 01:12:14 Shaun Murdoch wrote: > Hi Igor, > > I've taken some photos of the tuner so that hopefully you'll be able > to help work out why it won't tune in Linux. > > Please see the following link for the images: > http://www.flickr.com/photos/7690...@n04/sets/72157621703527801/ I have a few dm1105 based cards, but yours looks different from mine. > > The only chip on display is: > SDMC > DM1105N > D735 E280034 Please try recent v4l-dvb, as I've commited some change. Now You can try modprobe dm1105 card=1 > > Also - I tested the card in a Windows box today, so I am now certain > that both the card and the satellite connection are OK. The settings > that work with Windows (frequency, etc), don't lock in Linux. (I do > get a good signal reading in Kaffeine that is the same as Windows > gives, but no lock.) > > I hope this will help you work out what is wrong. > > Thanks! > Shaun > > 2009/7/22 Igor M. Liplianin : > > On 22 июля 2009 21:43:01 Shaun Murdoch wrote: > >> Hi, > >> > >> Thanks for the suggestion. > >> > >> I think there's something a bit weird with dvbtune. According to it's > >> man page the units for frequency (-f) are Hz. I am trying to tell it > >> 11.778 GHz - but you get errors if you do -f 1177800. Equally you > >> also get errors if you assume it is MHz, i.e. -f 11778. Anyway, if > >> it prints FE_HAS_SIGNAL and FE_HAS_CARRIER that must mean the > >> frequency I gave it is OK? > >> > >> In any case, scan doesn't work, nor does Kaffeine, so I don't think > >> it's that my use of dvbtune is wrong. > >> > >> Anyone got any other suggestions on what I can do to get this to lock? > >> > >> Thanks, > >> Shaun > >> > >> 2009/7/22 Seyyed Mohammad mohammadzadeh : > >> > Hello, > >> > > >> > I don't know what is the exact cause of your problem but I think you > >> > are tuning to a wrong frequency. You wrote: > >> > > >> > dvbtune -f 1177800 -s 27500 -p v -m > >> > > >> > in which the frequency parameters has two extra zeros which cause the > >> > frequency to interpret as : 1,177,800 MHz !!! > >> > > >> > 2009/7/22 Shaun Murdoch > >> > > >> >> Hi everyone, > >> >> First post so please be gentle :-) > >> >> I was wondering if anyone can help me please - I am trying to get a > >> >> DVB-S PCI card working with Linux (Ubuntu 9.04). So far I can get the > >> >> card recognised by Linux, but it won't tune - Kaffeine does tell me > >> >> that there is 95% signal and 80% SNR, and I am using the same > >> >> frequencies etc that a standard Sky box uses. The card is very common > >> >> on eBay so I am sure there are plenty people who have tried this / > >> >> would want this working. Some details that I hope will help someone > >> >> who knows more than I do about this! The card is one of these: > >> >> http://cgi.ebay.co.uk/DVB-S-Satellite-TV-Tuner-Video-Capture-PCI-Card > >> >>-Re > >> >> mote_W0QQitemZ130314645048QQcmdZViewItemQQptZUK_Computing_Computer_Co > >> >>mpon > >> >> ents_Graphics_Video_TV_Cards_TW?hash=item1e575bae38&_trksid=p3286.c0. > >> >>m14& _trkparms=65:12|66:2|39:1|72:1690|293:1|294:50 lspci: > >> >> 03:09.0 Ethernet controller: Device 195d:1105 (rev 10) > >> >> My dmesg output - looks ok?: > >> >> > >> >> $ dmesg | grep DVB > >> >> [ 12.174738] DVB: registering new adapter (dm1105) > >> >> [ 12.839501] DVB: registering adapter 0 frontend 0 (ST STV0299 > >> >> DVB-S)... [ 12.839633] input: DVB on-card IR receiver as > >> >> /devices/pci:00/:00:1e.0/:03:09.0/input/input > >> >> > >> >> My output from scan - the problem: > >> >> > >> >> $ sudo scan -vv /usr/share/dvb/dvb-s/Astra-28.2E > >> >> scanning /usr/share/dvb/dvb-s/Astra-28.2E > >> >> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > >> >> > >> >> >>> tune to: 11778:v:0:27500 > >> >> > >> >> DiSEqC: switch pos 0, 13V, hiband (index 2) > >> >> diseqc_send_msg:56: DiSEqC: e0 10 38 f1 00 00 > >> >> DVB-S IF freq is 1178000 > >> >> > >> >> >>> tuning status == 0x03 > >> >> >>> tuning status == 0x03 > >> >> >>> tuning status == 0x03 > >> >> >>> tuning status == 0x03 > >> >> >>> tuning status == 0x03 > >> >> >>> tuning status == 0x03 > >> >> >>> tuning status == 0x03 > >> >> >>> tuning status == 0x03 > >> >> >>> tuning status == 0x03 > >> >> >>> tuning status == 0x03 > >> >> > >> >> WARNING: >>> tuning failed!!! > >> >> > >> >> This is the correct satellite for my location (south UK), I believe. > >> >> Have tried plenty. Nothing locks. I'm using the latest liplianin > >> >> drivers - did a mercurial checkout and build today: > >> >> > >> >> $ modinfo dm1105 > >> >> filename: > >> >> /lib/modules/2.6.28-13-server/kernel/drivers/media/dvb/dm1105/dm1105. > >> >>ko license:GPL > >> >> description:SDMC DM1105 DVB driver > >> >> author: Igor M. Liplianin > >> >> srcversion: 46C1B3C3627D1937F75D732 > >> >> alias: pci:v195Dd1105sv*sd*bc*sc*i* > >> >> alias: pci:v109Fd036Fsv*sd*bc*sc*i* > >> >> depends:ir-
[PULL] http://www.kernellabs.com/hg/~stoth/hvr1700
Mauro, Please pull from http://www.kernellabs.com/hg/~stoth/hvr1700 - cx25840: Bugfix for no DVB-T on the Hauppauge HVR-1700 cx25840-core.c | 15 +-- cx25840-firmware.c | 13 - 2 files changed, 21 insertions(+), 7 deletions(-) This fixes a HVR1700 related regression, which occurred after the subdev conversion. In essence the order of initialization changed and I have to preserve GPIO settings before we load the firmware. Thanks to Sohail for raising this and mkrufky for doing the early analysis. -- 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: linuxtv.org downtime today due to software updates
On Sun, Jul 26, 2009 at 02:37:09PM +0200, Johannes Stezenbach wrote: > > sorry for short notice, but today I have enough spare time > to do the long overdue Etch -> Lenny update on linuxtv.org. > ssh and http access wil be blocked during the update. > I'll start in one or two hours from now and expect it to > take about two hours. Mission accomplished. Please note that I installed mercurial-1.3.1 on the server and used the default "paper" style in favour of the linuxtv-customized gitweb style, because it has this nice merge graph feature. Let me know if something isn't working as expected. Johannes -- 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, > It seems to me we have to add a new entry for your card. > Does it have a unique name they sell it, do you know the manufacturer? Yes, card is called SSD-TV-675 ( http://www.techcomindia.com/home.php?vaction=showprodd&cat=102&catt=TV%20Tuners&subcat=&subcatt=&prodid=501 ) > Is there a website or did you investigate all the printings on the PCB > already. > The tuner type label is often hidden under a OEM vendor label. > Sometimes a drop of salad oil is enough to make the upper sticker > transparent. Tuner factory label underneath is in most cases close to > the antenna connector. I got that : QSD-MT-S73 BD . I think this is the site http://www.szqsd.cn/en/product_show.asp?id=89 > Since 0x8000 does not work for mute on your card, you can try 0x4000 and > 0x2000 in the mute section. Note sure how I can do that. Need more help :-) > For example, if you have missing channels between 450 and 471.25 MHz, > you can try with tuner=69 again. It was my problem. The tvtime chooses the default frequency as us-cable network. I used --frequency=custom to fix that. Its working now. > Is for that card FM radio support announced? Not sure about that. Its not working I think. Again, thanks for all your help. You are a genius :-) - 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
Ancient hg repositories: delete?
Hi, A number of user repositories on linuxtv.org haven't been updated for years: http://linuxtv.org/hg?sort=-lastchange I suspect that most of them have become totally irrelevant and just clutter up the repository list, making it less user friendly, and using up disk space. Probably the changes they contain have been merged long ago and the user just forgot to delete the repo? Can somebody tell me please why I shouldn't go and just delete all repositories which haven't been touched in the last 12 months? IOW, unless I hear otherwise, I'm going to delete the cruft after Sep. 1. Thanks, Johannes -- 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
old V4L Wiki
Hi, the merge of the content from the old V4L Wiki into the V4L-DVB Wiki has been nearly completed, but seems to have come to a halt? I would like to kill off the old V4L Wiki soon. IMHO most of the remaining pages are old user discussions, maybe it's best if the users themselves take care of copying it over to the V4L-DVB Wiki if they think their content is still relevant. My plan is to delete the old Wiki soon after Sep. 1. New account creation in the V4L Wiki has been disabled. List of remaining pages: http://linuxtv.org/v4lwiki/index.php/Special:AllPages Namespace Main: Em2880/remote Firewire devices People behind V4L Wiki merger Namespace Talk: Em2820 Namespace User: Fabien Gouchi Hthevath IDamir Jkrzyszt Lucarasp Lux MarkusRechberger/Bugs Mpapet Navratil Peter Sakis Satarsa SunnyBUG Tobru TvY2k Varogami Namespace User-talk: Heiner Liplianin Luckyboy Nvicf Santod Satarsa Uniface Thanks Johannes -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH] uvcvideo: Really don't apply the FIX_BANDWIDTH quirk to all ViMicro devices
I forgot to change USB_DEVICE_ID_MATCH_VENDOR to USB_DEVICE_ID_MATCH_DEVICE in
the last commit, defeating its whole purpose. Fix this.
Signed-off-by: Laurent Pinchart
Mauro, can you merge this with the "Don't apply the FIX_BANDWIDTH quirk to all
ViMicro devices" commit (changeset 12328:da81aafb9c5d) and keep the commit
message of the first when you push them upstream ? As this is a 2.6.30
regression it would be nice to get the fix in 2.6.31.
diff -r f8f134705b65 -r 2b37d4d66c1a
linux/drivers/media/video/uvc/uvc_driver.c
--- a/linux/drivers/media/video/uvc/uvc_driver.cFri Jul 24 16:19:39
2009
-0300
+++ b/linux/drivers/media/video/uvc/uvc_driver.cSun Jul 26 18:30:02
2009
+0200
@@ -1852,7 +1852,7 @@
.bInterfaceProtocol = 0,
.driver_info = UVC_QUIRK_STREAM_NO_FID },
/* ViMicro Vega */
- { .match_flags = USB_DEVICE_ID_MATCH_VENDOR
+ { .match_flags = USB_DEVICE_ID_MATCH_DEVICE
| USB_DEVICE_ID_MATCH_INT_INFO,
.idVendor = 0x0ac8,
.idProduct= 0x332d,
@@ -1861,7 +1861,7 @@
.bInterfaceProtocol = 0,
.driver_info = UVC_QUIRK_FIX_BANDWIDTH },
/* ViMicro - Minoru3D */
- { .match_flags = USB_DEVICE_ID_MATCH_VENDOR
+ { .match_flags = USB_DEVICE_ID_MATCH_DEVICE
| USB_DEVICE_ID_MATCH_INT_INFO,
.idVendor = 0x0ac8,
.idProduct= 0x3410,
@@ -1870,7 +1870,7 @@
.bInterfaceProtocol = 0,
.driver_info = UVC_QUIRK_FIX_BANDWIDTH },
/* ViMicro Venus - Minoru3D */
- { .match_flags = USB_DEVICE_ID_MATCH_VENDOR
+ { .match_flags = USB_DEVICE_ID_MATCH_DEVICE
| USB_DEVICE_ID_MATCH_INT_INFO,
.idVendor = 0x0ac8,
.idProduct= 0x3420,
--
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: 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:Sun Jul 26 19:00:03 CEST 2009 path:http://www.linuxtv.org/hg/v4l-dvb changeset: 12339:f8f134705b65 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/Sunday.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Sunday.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: Problem with My Tuner card
Hi Unni, Am Sonntag, den 26.07.2009, 21:11 +0530 schrieb unni krishnan: > Hi, > > > > It seems to me we have to add a new entry for your card. > > Does it have a unique name they sell it, do you know the manufacturer? > > Yes, card is called SSD-TV-675 ( > http://www.techcomindia.com/home.php?vaction=showprodd&cat=102&catt=TV%20Tuners&subcat=&subcatt=&prodid=501 > ) good. > > Is there a website or did you investigate all the printings on the PCB > > already. > > The tuner type label is often hidden under a OEM vendor label. > > Sometimes a drop of salad oil is enough to make the upper sticker > > transparent. Tuner factory label underneath is in most cases close to > > the antenna connector. > > I got that : > > QSD-MT-S73 BD . I think this is the site > http://www.szqsd.cn/en/product_show.asp?id=89 Very good. You digged out another new tuner manufacturing conglomerate there. Unless they provide internals, we can only run in compatible mode. > > Since 0x8000 does not work for mute on your card, you can try 0x4000 and > > 0x2000 in the mute section. > > Note sure how I can do that. Need more help :-) The FV2K mutes on 0x8000 high. Yours not. Just try with 0x2000 and 0x4000 in the mute section of the card entry. If it should be true, that either or the other pin is needed to be low, that should work. Else, you can change it to LINE1 to get it calm. > > For example, if you have missing channels between 450 and 471.25 MHz, > > you can try with tuner=69 again. > > It was my problem. The tvtime chooses the default frequency as > us-cable network. I used --frequency=custom to fix that. Its working > now. Even better. We must look out for others failing for some frequencies close to the takeovers globally, but looks good. > > Is for that card FM radio support announced? > > Not sure about that. Its not working I think. That tuner you pointed to has no radio support. Also, it is mostly that the driver becomes better over times. There is no indication yet, that there could be a separate radio tuner on a different valid address yet. > Again, thanks for all your help. You are a genius :-) For sure not. But I know, looking at the full moon from southern India compared to my place, really makes a difference. With a cup of tea or not. 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: TBS 8920 still fails to initialize - cx24116_readreg error
On Sun, Jul 26, 2009 at 03:29:13PM +0300, Igor M. Liplianin wrote: > On 25 2009 05:22:06 Mark Zimmerman wrote: > > 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. > I've changed tbs 8920 initialization in > http://mercurial.intuxication.org/hg/s2-liplianin. > I ask you to try it. > If it works, then I will commit it to linuxv. > Also pay attention to remote. > Unfortunately, there appears to be no change: cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.7 loaded cx88[0]: subsystem: 8920:, board: TBS 8920 DVB-S/S2 [card=72,autodetected], frontend(s): 1 cx88[0]: TV tuner type 4, Radio tuner type -1 input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input5 cx88/0: cx2388x v4l2 driver version 0.0.7 loaded input: cx88 IR (TBS 8920 DVB-S/S2) as /devices/pci:00/:00:08.2/input/input6 cx88[0]/2: cx2388x 8802 Driver Manager alloc irq_desc for 17 on cpu 0 node 0 alloc kstat_irqs on cpu 0 node 0 cx88-mpeg driver manager :00:08.2: PCI INT A -> GSI 17 (level, low) -> IRQ 17 cx88[0]/2: found at :00:08.2, rev: 5, irq: 17, latency: 32, mmio: 0xf900 IRQ 17/cx88[0]: IRQF_DISABLED is not guaranteed on shared IRQs cx8800 :00:08.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 cx88[0]/0: found at :00:08.0, rev: 5, irq: 17, latency: 32, mmio: 0xfa00 IRQ 17/cx88[0]: IRQF_DISABLED is not guaranteed on shared IRQs cx88[0]/0: registered device video0 [v4l2] cx88[0]/0: registered device vbi0 cx88/2: cx2388x dvb driver version 0.0.7 loaded cx88/2: registering cx8802 driver, type: dvb access: shared cx88[0]/2: subsystem: 8920:, board: TBS 8920 DVB-S/S2 [card=72] cx88[0]/2: cx2388x based DVB/ATSC card cx8802_alloc_frontends() allocating 1 frontend(s) ACPI: PCI Interrupt Link [ALKC] enabled at IRQ 22 alloc irq_desc for 22 on cpu 0 node 0 alloc kstat_irqs on cpu 0 node 0 VIA 82xx Audio :00:11.5: PCI INT C -> Link[ALKC] -> GSI 22 (level, low) -> IRQ 22 VIA 82xx Audio :00:11.5: setting latency timer to 64 cx24116_readreg: reg=0xff (error=-6) cx24116_readreg: reg=0xfe (error=-6) Invalid probe, probably not a CX24116 device cx88[0]/2: frontend initialization failed cx88[0]/2: dvb_register failed (err = -22) cx88[0]/2: cx8802 probe failed, err = -22 Just for reference, here is how it looks when using the drivers compiled from the source in tbs6920_8920_v23_linux_x86_x64.rar: cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded cx88/0: cx2388x v4l2 driver version 0.0.6 loaded cx88[0]: subsystem: 8920:, board: TBS 8920 DVB-S/S2 [card=72,autodetected], frontend(s): 1 cx88[0]: TV tuner type 4, Radio tuner type -1 input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input5 cx88[0]/2: cx2388x 8802 Driver Manager alloc irq_desc for 17 on cpu 0 node 0 alloc kstat_irqs on cpu 0 node 0 cx88-mpeg driver manager :00:08.2: PCI INT A -> GSI 17 (level, low) -> IRQ 17 cx88[0]/2: found at :00:08.2, rev: 5, irq: 17, latency: 32, mmio: 0xf900 IRQ 17/cx88[0]: IRQF_DISABLED is not guaranteed on shared IRQs cx8800 :00:08.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 cx88[0]/0: found at :00:08.0, rev: 5, irq: 17, latency: 32, mmio: 0xfa00 IRQ 17/cx88[0]: IRQF_DISABLED is not guaranteed on shared IRQs cx88[0]/0: registered device video0 [v4l2] cx88[0]/0: registered device vbi0 cx88/2: cx2388x dvb driver
Re: Lenovo webcam problem which using gspca's vc032x driver
Dear Jean-Francois,
I put the USB snoop log here
http://people.canonical.com/~acelan/bugs/lp310760/UsbSnoop_{1,2,3,4,89}.log.gz
The utility, USB Snoop, seems to have some problem with the camera
preview utility, so the log may not so complete.
And the dmslog is the USB traffic in binary form, you can read all USB
traffic from dmslog by hexdump the files.
Best regards,
AceLan Kao.
2009/7/25 Jean-Francois Moine :
> Hi Acelan Kao,
>
> I got news from a person who has the sensor mi1320_soc and had a
> vertical flip problem. She found that the sensor register 0x20 sets the
> image flips: bit 0 = vertical, bit 1 = horizontal.
>
> Comparing the sequences of the mi1310_soc, the bit 0 is inverted in the
> sxga (0x0303 instead of 0x0302). May you change it and see if the image
> is normal? (line ~ 706 {0x20, 0x03, 0x03, 0xbb}, -> 0x03, 0x02)
>
> Best regards.
>
> --
> Ken ar c'hentañ | ** Breizh ha Linux atav! **
> Jef | http://moinejf.free.fr/
>
--
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
