[linux-dvb] Pinnacle PCTV DUAL DVB-T DIVERSITY STICK supported?
Hi, does anyone know,whether the Pinnacle PCTV DUAL DVB-T DIVERSITY STICK works under linux or (better) owns this usb dvb-t stick? tnx regards, Tobias ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] JustDVb 2.0 released today..
hi we want you to know that Cineca just released the 2.0 version of the JustDvb-It suite. It's a set of tools useful for DVB stream creation and manipulation, expecially for the italian interactive digital television world (DVB MHP), but we are moving to OCAP and BD-J too.. Many more info here: http://www.cineca.tv/labs/mhplab/JustDVb-It%202.0.html There are many new features, like more DVB ASI cards supported, compressed modules, LCN EPG and a new live cd very useful as a starting demo. you can get it freely, as usual, here; you just need to get an username by email: http://www.cineca.tv/labs/mhplab/index-en.html bye andrea venturi ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] IVTV pci riser problem
Mark Buechler wrote: This looks like the same problem I was having when I tried using a PCI bus expander (Magma). I assumed it was related to the PCI bridge not allocating resources properly with PnP. - Mark. Sounds like a reasonable assumption. - Was this behaviour the same under a Windows OS? - Is there any driver related to the PCI bridge that might be the source of the problem? (I'm assuming the expander contains the PCI bridge I'm not familiar) - Do you think its possible that it might BIOS related ... i.e PCI bridge correctly passes off info for two devices but mobo/BIOS only accepts info for one device (or doesn't know what to do with a second set of info) for that populated PCI slot ? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Fix of enum usage in tzap
Hi, 2007/6/14, [EMAIL PROTECTED] [EMAIL PROTECTED]: Hi, Please find attached the patch that corrects enum usage in tzap code. The problem is that the code passes enum references as int*, which is not correct in some cases. There are ABIs for which sizeof(int) != sizeof(enum), so a function using the pointer for writing to an enum field as int* clobbers nearby data (other structure members, in this case). One example of such an ABI is ARMs EABI and I'm using tzap on one embedded box based on ARM EABI (Buffalo LinkStation Pro). Original tzap code was not able to tune (passing e.g. code_rate_HP as invalid FEC_NONE, while channels.conf contained FEC_2_3), after the patch, it works for me. I applied your patch (some white-space stuff fixed), as nobody else seems to take care of it ... I didn't inspect othet code too carefully, but it seems that other channels file parsers in dvb-apps are OK (except czap?). Ok, will have a (quick) look. Nenik Signed-off-by: Petr Nejedly [EMAIL PROTECTED] Thanks :) Christoph ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Patch adding extern C to lib/libdvben50221/en50221_stdcam.h
Hi. This has given me some grey hairs a couple of times. Mentioned in #linuxtv earlier, but this time I send a patch. Thanks for all help! -Morgan- Morgan.patch Description: Binary data ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] LifeView TV Walker - Model LR506
On Wed, 20 Jun 2007 14:14:14 +0200 Daniel Weigl [EMAIL PROTECTED] wrote: Hello Nick, Thx for your replies! Take a look at http://www.rasterburn.org/~aet/m920x/m920x-twalker-rl506.patch This driver should not belong to m920x.c since it's not based on m920x (noticed that afterwards). Couple notes: - m920x_identify_state will most likely not work for your device - m920x_firmware_download routine should not be used for this device(assuming you have to dl firmware) - you need to make sure adapter field of tvwalker_lr506_properties is properly filled You can examine other drivers that use CY7C68013A(FX2) to figure out what still needs to be done. Couple pointers: 19:30 mkrufky most likely, the dvb-usb-firmware's default CYPRESS_FX2 handling should do the job 19:31 mkrufky you may want to look at the FIRST entry in cxusb, for the medion 95700, for an example of what a typical dvb_usb_device_properties struct looks like for an FX2 device 19:31 mkrufky (dont look at the bluebird ones -- we had to override the firmware download routing with a USB PID firmware patch) Are you able to open it up and find out what chips are inside? Okay... I already posted some bits about it in my first post - but this may be a bit messy... english is not my native language. So here are the ICs I have found inside: On the Top (or I just call it top) Phillips 8275AC1 CY7C68013A (Cypress?) And on the bottom: TDA1004GHT SA1371.1 Additionally ther is also a small 8pin SMD chip, where I cant read the number/id, because ther is a blue color-spot on it. Maybe it is a i2c (or 1-wire or similiar) flash, which stores the firmware? So that ther is no download needed at all... But Iam just guessing right into the blue. I have made some pictures of the device (and its inside), you can find it under: http://danyserv.selfip.org/pic/thumbnails.php?album=27 You should try to extract your device's firmware from that dvbsnoop output so you won't be dependent on Windows when you get the device working. Oh... did i write _dvb_snoop... of course i meant _usb_snoop... sorry for that, but i guess you thought the same thing, i was meaning. Okay, I will try, but I have no (deeper) experiences with USB nor DVB(-drivers), so Iam not sure, if ill get anything :) The logfile: http://nopaste.info/eead046817.html I couldn't download this; it is wrapped in HTML. Okay, here i have it as plaintext again: I started the usbsnoop ( http://benoit.papillault.free.fr/usbsnoop/ ) befor i connected the stick and stoped it some seconds after i had plugged it in. The log file can be found under: http://danyserv.selfip.org/dir/LifeView/usbsnoop.log (~600kb) I made a second log, which includes the plugin and the start of the DVB-App and some seconds of the TV-stream: http://danyserv.selfip.org/dir/LifeView/usbsnoop_tv.log.bz2 (~200kb) (I truncated the log after some big packets, bec. the whole log had ~200MiB) So, thats all for now, i thank you for any help you (or anybody else) can provide. Daniel Weigl -- Aapo Tahkola ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Patch adding extern C to lib/libdvben50221/en50221_stdcam.h
Hi, 2007/6/27, Morgan Tørvolt [EMAIL PROTECTED]: Hi. This has given me some grey hairs a couple of times. Mentioned in #linuxtv earlier, but this time I send a patch. Thanks for all help! Applied, thanks :) -Morgan- Christoph ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Unfetchable firmware file tt_budget_217g.zip / tda10045tda10046
Hi there! Next bad news about unfetchable file for get_dvb_firmware. The file http://www.technotrend.de/new/217g/tt_budget_217g.zip is disappeared like the tt_Premium_217g.zip file some days ago. The file tt_budget_217g.zip is used for da10045 and tda10046. @adq: Is it possible (or have you already done that) to ask technotrend if they could provide just the needed (small) file, or allow redistribution? As that should be cheeper with respect to used download-bandwidth to fetch just some 100kB than 10 or 20 MB for the zipfiles. Matthias -- Matthias Schwarzott (zzam) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] m920x device: Genius TVGo DVB-T02Q
On Wed, 20 Jun 2007 18:09:50 +0200 Pere Blay [EMAIL PROTECTED] wrote: well, i still can't even scan channels... i lack the /dev/dvb/adapter0/frontend0 device (that's what 'scan' from dvb-utils complains for... and actually that os what dmesg tells me in the output: [ 297.476000] dvb-usb: no frontend was attached by 'MSI Mega Sky 580 DVB-T USB2.0' (that was already in the dmesg dump i sent before) so... 1) how to make this device be happy with its own firmware? (or how to check that if the firmware i got through snoopypro and m920_sp_parse is ok or needs to be improved?) Firmware you found was most likely too short. Binary file size should be about 3.3K. Take a look at http://rafb.net/p/0t085M48.html Line 000439: OUT: 01 ms 000439 ms 40 22 01 00 69 ff 00 00 is the important one here that you need to find in order to verify that you havent missed anything. I think m920_sp_parse one bug that prevents it from generating proper file when reading from usbsnoop. Anyway, let me know when you find a dump with either 69ff(usbsnoop uses different byte ordering) or ff69. 2) what kind of test can i apply to guess what is the right frontend and what parameters to use in the m920.c file in order to get it loaded when the device is connected? Used components can be identified by looking at usb dumps. You can also open your device if you wish. Though, we will need some logs anyway. -- Aapo Tahkola ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NDAs - ANY KNOWN RULES?
Am Dienstag, den 26.06.2007, 19:37 -0700 schrieb Arjan van de Ven: Thanks for your explanations, but I know for sure it does't work. then.. do you have an actual question or are you just trying to troll? and yes there have been several such trolls lately on this list, and so far your postings have all the signs of being just another one.. DO NOT FEED THE TROLLS Hello, thanks ;), you might help me to decide if somebody abuses a list already for free advertising or is still contributing. http://marc.info/?l=linux-videom=118289479416612w=2 Sorry, my question is, where one can look up if the pinning of a newer chip we support is also only under NDA available. Previously often at least that was public. (examples now saa7131e, tda10046a, tda8275ac1) If I don't find anything on the web, whom I have to ask that question, the NDA holder, the manufacturer or do we have a list, because everybody knows that this can be helpful to identify hardware differences and this question is always asked already? Thanks, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] What adapter to use with Swedish Comhem
Sven Karlsson wrote: 1) Works without hitches under Linux and MythTV. The stability is of outmost importance. 2) Works with Com hem and has good and stable CI support. 3) Is not too expensive. MPEG playback functionality is not needed. 4) Can be bought in Sweden. I'm using two Terratec Cinergy 1200 DVB-C in Linux (2.6.21 has native support for the new MK3 version) with MythTV. Can't answer for it's CI support, I'm using a softcam/Phoenix interface solution since I had the Phoenix lying around already and I wanted a dual-tuner solution. They were about 600 + VAT from Deltaco when I bought them. See URL: http://www.prisjakt.nu/produkt.php?p=62357 I've had them in my Myth box for three or four months now, haven't had any trouble. They are a bit pickier about signal quality than Comhem's old Sagem box, but if you have good signal (or get yourself an amplifier) you're home free. Also, can someone recommend a CAM that works with Com hem without problems. Any original Conax cam will work. Check the wiki for recommended CAMs. Finally, I would also like to hear about any experiences people might have using MythTV to receive digital TV from Com hem. I have used VDR to receive TV from Com hem with my Siemens card and MythTV to receive analog TV but never MythTV to receive DVB streams... DVB in Myth is incredibly easy. All in all, after getting used to Myth (which took a while), the complete installation from compiling SVN to watching TV probably took me an hour or two. Scanning channels can't be easier, swedb has all the listings.. everything basically just works. /fnord ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
