[linux-dvb] Update to au-Melbourne scan list
Hi, Back in November, channel Seven changed their fec_hi from 2/3 to 3/4 causing scans to not pick it up ( http://www.dba.org.au/index.asp?sectionID=39newsID=982display=news ). The new entry in the au-Melbourne file for channel seven should be: # Seven T 17750 7MHz 3/4 NONE QAM64 8k 1/16 NONE I attached the complete updated file anyway. Jeff au-Melbourne Description: Binary data ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] linux device ordering at boot time
Dear Alan, dear kernel dvb hackers, Am Sonntag, 20. Januar 2008 schrieb Alan Cox: Well, it's a major pain in the a**. I've no idea, what reversed the order of PCI devices, but I had to disable the automatic dvb driver loading in order It depends on the order you load the modules Sure, but given, that userspace didn't changed meanwhile, I relied on some hotplug figure before (in openSUSE 10.2 with 2.6.18) to load the modules in the correct order which itself surely enumerates the PCI bus in some way. After switching to 2.6.24-rc this order was reversed. At least, my budget card was first now, while the ff dvb card second, which resulted in a working vdr, unfortunately without picture and sound (that dropped the WAF immensely 8-|). I solved this issue by blacklisting both cards in /etc/modprobe.d/blacklist, and manually determined the order and which modules to load, only to discover, that the system won't wake up on the scheduled times anymore. Ahh, /proc/acpi/alarm disappeared and needed adaption to /sys/class/rtc/rtc0/wakealarm. That move seems to have (yet to examine, but easy to work around) timezone issues. On the bright side, this new interface doesn't interfere with setting the c-mos clock on power down anymore. One gross hack down. Cool. The last regressions awaiting to get tackled are: - rewind is somewhat broken: after a few seconds rewinding correctly, the pictures stutter, and vdr uses cpu like mad. - from time to time, the same happens for a few seconds on simple replay. Both issues _feel_ like locking artefacts, which 2.6.18 (with http://linuxtv.org/hg/v4l-dvb drivers) didn't suffer from (my vdr operates mostly on nfs3 mounted files). I'm trying to explore these problems in more detail and will come back. For the record, these issues happen with the factory drivers/media modules and with drivers from v4l-dvb tree. Please don't get me wrong, I'm not whining about all this, it's just a report from user side about what happens, if one tries to follow a strong moving target. Take it as a reminder, that some decisions during (kernel) development does have an wider impact on us poor users out there, as it seems. The only thing, what makes me really sad, is that current dvb development is distracted by political and emotional (ego-logical) reasons, repressing the full potential in this area. Pete ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Update to au-Melbourne scan list
On Sunday 20 January 2008, Jeff Bailes wrote: Hi, Back in November, channel Seven changed their fec_hi from 2/3 to 3/4 causing scans to not pick it up ( http://www.dba.org.au/index.asp?sectionID=39newsID=982display=news ). The new entry in the au-Melbourne file for channel seven should be: # Seven T 17750 7MHz 3/4 NONE QAM64 8k 1/16 NONE I attached the complete updated file anyway. Jeff They are a pain. Anyway, according to the web site that you quoted, all tuners that comply with Australian standards will cope without adjustment. Unfortunately not all tuners comply with Australian standards. :-( Presumably all au-tuning_files should have their channel 7 entry updated. Can this be done at the data base end, or do all files have to be re-submitted? Also the GI in Brisbane is noted as changing as well. -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [v4l-dvb-maintainer] [PATCH 1/2] bt878: remove handcrafted PCI subsystem ID check
On Sat, 19 Jan 2008 05:28:49 -0800 (PST)
Trent Piepho [EMAIL PROTECTED] wrote:
I wish people would use the patch creating system from Hg, since it would
the format mistakes evident in this patch.
1. no patch title
2. s-o-b's in wrong order
3. diffstat included
4. patch against git source and not hg
On Sat, 19 Jan 2008, Akinobu Mita wrote:
From: Akinobu Mita [EMAIL PROTECTED]
This patch moves the subsystem ID and subsystem vendor ID check from probing
function to the PCI generic function by describing subsystem IDs in
pci_device_id table. This enables to add new PCI IDs to a device driver
pci_ids
table at runtime by new_id file in sysfs pci driver tree.
This patch also changes the driver from having a pci alias to auto-load for
all bt878 cards to instead only auto-load for specific cards. Some
distributions will probably want to adjust their modprobe rules. I know
some have delt with both snd-bt87x and bt878 loading for the same devices
in various ways, e.g. adding one or the other to their modprobe blacklist
files.
The proper solution here seems to be moving snd-bt87x to our tree, and create
some shared code to be used by snd-bt87x, dvb-bt8xx, to avoid the
driver conflicts.
I think that new_id will only work if hotplug is turned on. Without
hotplug, there will be no way to load the driver for other devices (such as
those with eprom trouble).
+static const char * __devinit card_name(const struct pci_device_id *id)
+{
+ if (id = bt878_pci_tbl
+ id bt878_pci_tbl + ARRAY_SIZE(bt878_pci_tbl) - 1)
+ return (const char *)id-driver_data;
Are you sure this is safe? I don't remember reading that the pci_device_id
passed to the pci driver probe method must be from the device id table.
Couldn't the device id be a local variable from whatever calls probe, as
long as driver_data is set to the correct value? I looked at the current
pci bus code, and it does always pass a pointer into the driver's pci id
table. But that could change.
It seems like a better method would just be to check if driver_data is 0,
which will be the case if the id was added dynamically.
This data can't be changed by pci core, since driver_data is a priv element. It
is used as a pointer on some drivers, while others use it as an integer value to
an array (like most V4L/DVB and ALSA drivers). The above code should work
properly. If pci touches on this value, it would break the support for the rest
of v4l/dvb drivers, so I think we don't need to worry about this.
Cheers,
Mauro
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] AverMedia DVB-S Pro Howto?
Hi, I'm try to make this card work using the lastest patches that has been published in this list. However, I'm somewhat lost about what patches and in which order must be applied to a clean HG tree. I've tried to apply the patches mentiones in these threads: - Analog inputs: http://www.mail-archive.com/linux-dvb@linuxtv.org/msg27833.html - zl10036 driver: http://www.mail-archive.com/linux-dvb@linuxtv.org/msg28565.html - zl10313 into mt312: http://www.mail-archive.com/linux-dvb@linuxtv.org/msg28566.html - DVB-S support for A700: http://www.mail-archive.com/linux-dvb@linuxtv.org/msg28567.html However, almost none of they apply cleanly into a freshly download HG tree. I'm willing to help on this card, at least as a beta-tester. I'm a C++ developer, so I'm not scared about compiling, repositories, patches, etc... Best regards, Eduard ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [Patch] kernel crash when using a dvb usb stick on a mips platform
Hi, I post this patch that fixes a kernel crash that happens when using a dvb usb stick on a mips platform and I think even on other platforms on which the dma access in not cache-coherent. The problem's origin is that, inside the method usb_bulk_urb_init of file drivers/media/dvb/dvb-usb/usb-urb.c, stream-urb_list[i]-transfer_buffer points to a memory area that has been allocated to be dma-coherent but stream-urb_list[i]-transfer_flags doesn't include the URB_NO_TRANSFER_DMA_MAP flag and stream-urb_list[i]-transfer_dma is not set. When later on the stream-urb_list[i]-transfer_buffer pointer is used inside function usb_hcd_submit_urb of file drivers/usb/core/hcd.c since the flag URB_NO_TRANSFER_DMA_MAP is not set the urb-transfer_buffer pointer is passed to the dma_map_single function that since the address is dma-coherent returns a wrong tranfer_dma address that later on leads to the kernel crash. The problem is solved by setting the URB_NO_TRANSFER_DMA_MAP flag and the stream-urb_list[i]-transfer_dma address. Perhaps to be more safe the URB_NO_TRANSFER_DMA_MAP flag can be set only if stream-urb_list[i]-transfer_dma != 0. I don't know if half of the fault can be of the dma_map_single function that should anyway returns a valid address both for a not dma-coherent and a dma-coherent address. Just to be clear: I've done this patch to solve my problem and I tested it only on a mips platform but I think it should not cause any problems on other platforms. I posted it here to help someone else that can have my same problem and to point it out to the mantainer of this part of code. You can use it at your own risk and I'm not resposible in any way for any problem or damage that it can cause. I'm available to discuss about it Bye Michele Scorcia --- linux-2.6.20.4.orig/drivers/media/dvb/dvb-usb/usb-urb.c 2007-03-23 20:52:51.0 +0100 +++ linux-2.6.20.4/drivers/media/dvb/dvb-usb/usb-urb.c 2007-10-25 12:19:50.0 +0200 @@ -152,7 +152,8 @@ stream-props.u.bulk.buffersize, usb_urb_complete, stream); - stream-urb_list[i]-transfer_flags = 0; + stream-urb_list[i]-transfer_flags = URB_NO_TRANSFER_DMA_MAP; + stream-urb_list[i]-transfer_dma = stream-dma_addr[i]; stream-urbs_initialized++; } return 0; ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] AverMedia DVB-S Pro Howto?
On Sonntag, 20. Januar 2008, Eduard Huguet wrote: Hi, I'm try to make this card work using the lastest patches that has been published in this list. However, I'm somewhat lost about what patches and in which order must be applied to a clean HG tree. I've tried to apply the patches mentiones in these threads: - Analog inputs: http://www.mail-archive.com/linux-dvb@linuxtv.org/msg27833.html - zl10036 driver: http://www.mail-archive.com/linux-dvb@linuxtv.org/msg28565.html - zl10313 into mt312: http://www.mail-archive.com/linux-dvb@linuxtv.org/msg28566.html - DVB-S support for A700: http://www.mail-archive.com/linux-dvb@linuxtv.org/msg28567.html However, almost none of they apply cleanly into a freshly download HG tree. I'm willing to help on this card, at least as a beta-tester. I'm a C++ developer, so I'm not scared about compiling, repositories, patches, etc... Hi Eduart! I try to make it easier for users to try out the patches. I try to document the necessary steps in the wiki on this page: http://www.linuxtv.org/wiki/index.php/AVerMedia_AVerTV_DVB-S_Pro_(A700) I like to create one large patch to be applied against latest hg version and hope to get this finished these days. But please mind that the drivers really are development status only. So they work most of the time but I cannot tell why if not :) Matthias -- Matthias Schwarzott (zzam) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Fwd: [Kaffeine-user] frequency DVB-T it-Pisa tested on 2008-01-16
From a kaffeine user ... Christoph -- Weitergeleitete Nachricht -- Betreff: [Kaffeine-user] frequency DVB-T it-Pisa tested on 2008-01-16 Datum: Mittwoch 16 Januar 2008 Von: [EMAIL PROTECTED] An: [EMAIL PROTECTED] Hi I've tested channel on my DVB-t card. I'am in Italy, in Pisa. Tested 100%. Thank for your attention. --- it-Pisa Description: Binary data ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Update to au-Melbourne scan list
On 20/01/08 20:47, Peter D. wrote: On Sunday 20 January 2008, Jeff Bailes wrote: Hi, Back in November, channel Seven changed their fec_hi from 2/3 to 3/4 causing scans to not pick it up ( http://www.dba.org.au/index.asp?sectionID=39newsID=982display=news ). The new entry in the au-Melbourne file for channel seven should be: # Seven T 17750 7MHz 3/4 NONE QAM64 8k 1/16 NONE I attached the complete updated file anyway. Jeff They are a pain. Anyway, according to the web site that you quoted, all tuners that comply with Australian standards will cope without adjustment. Unfortunately not all tuners comply with Australian standards. :-( Presumably all au-tuning_files should have their channel 7 entry updated. Can this be done at the data base end, or do all files have to be re-submitted? Also the GI in Brisbane is noted as changing as well. I can confirm that the au-Brisbane scan file needs to change. It works now for me with the same channel 7 line that Jeff included above. Scan wasn't finding channel 7 without the change. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle 310e / ULi M9207
Hello again, I just talked to somebody @ Pinnacle. I asked them if I could receive some info about the M9207 chip or/and the source code of the windows driver ... They made a case of it and I will hear a response within 2 days :) Lets hope I get some information so we can get this thing working on linux ! Sincerely, Jean-Louis Dupond Jean-Louis Dupond schreef: Hello, I have a Pinnacle 310e Analog/DVB TV device. But I can't get it working. Checked for drivers for it, and all the drivers seems to be in the linux kernel, but only driver for the ULi M9207 chip seems missing. It seems somebody is developping one (http://mcentral.de/wiki/index.php5/M9207) but seems developping stopped 8 months ago :( More info about the card: http://www.linuxtv.org/v4lwiki/index.php/Pinnacle/310e Now I tought that if somebody with some driver writing skills could write some code, I could help to test/debug the code. Sincerely, Jean-Louis Dupond ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle 800i - obsolete tuner i2c address?
Tim, In the future, please don't dropp cc from the mailing list. Steve, Chaogui's patch fixed Tim's XC5000 initialization problem -- we should merge it if all is well with it. Please see below. -Mike Timothy E. Krantz wrote: John, Sorry for sending this twice -- I sent it the first time from an email address not subscribed to linux-dvb :-/ John Massengale wrote: I got the Pinnacle 800i working on Mythbuntu, I can tune both analog and digital channels, but if I reboot, for some reason it starts having problems. Thanks for sending in the obsolete tuner address message -- I'll remove this warning for the XC5000 tuners. Unfortunately, I don't know why your tuner isn't working after a reboot... Perhaps the device gets held in reset after a reboot, and it isn't properly being taken out as needed? Try the patch in this email and let us know if that fixes the problem: http://linuxtv.org/pipermail/linux-dvb/2008-January/022977.html Regards, Mike That patch resolved the problem for me. Tim ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] AverMedia DVB-S Pro Howto?
Thanks! I'll try those patches as soon as they get posted. I'll provide all the feedback I can. And don't worry about they being beta: after spending one entire year fighting against the Nova-T 500 disconnects I think I'm ready for everything... Best regards, and thanks again for your work. Eduard 2008/1/20, Matthias Schwarzott [EMAIL PROTECTED]: On Sonntag, 20. Januar 2008, Eduard Huguet wrote: Hi, I'm try to make this card work using the lastest patches that has been published in this list. However, I'm somewhat lost about what patches and in which order must be applied to a clean HG tree. I've tried to apply the patches mentiones in these threads: - Analog inputs: http://www.mail-archive.com/linux-dvb@linuxtv.org/msg27833.html - zl10036 driver: http://www.mail-archive.com/linux-dvb@linuxtv.org/msg28565.html - zl10313 into mt312: http://www.mail-archive.com/linux-dvb@linuxtv.org/msg28566.html - DVB-S support for A700: http://www.mail-archive.com/linux-dvb@linuxtv.org/msg28567.html However, almost none of they apply cleanly into a freshly download HG tree. I'm willing to help on this card, at least as a beta-tester. I'm a C++ developer, so I'm not scared about compiling, repositories, patches, etc... Hi Eduart! I try to make it easier for users to try out the patches. I try to document the necessary steps in the wiki on this page: http://www.linuxtv.org/wiki/index.php/AVerMedia_AVerTV_DVB-S_Pro_(A700) I like to create one large patch to be applied against latest hg version and hope to get this finished these days. But please mind that the drivers really are development status only. So they work most of the time but I cannot tell why if not :) Matthias -- Matthias Schwarzott (zzam) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Recents kernels and multiproto ?
Hello, I would like to be abble to use zen-source which are really good for multimedia desktop but curently miss multiproto. Does anyone made some works in order to support it ? git repo : http://repo.or.cz/w/linux-2.6/zen-sources.git STABLE SNAPSHOTS PATCHES: http://zen.waninkoko.info/patches Thank you very much, -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DiBcom 3000MC/P LITEON lossing it's id.
Hi, I got a LITE-ON USB2.0 DVB-T Tune that loose it's cold state vid/pid and got FX2 dev kit one (0x04b4,0x8613). I suppose the cypress chip doesn't manage to read the pid from i2c eeprom and give the default id. I patch the driver to replace USB_VID_LITEON, USB_PID_LITEON_DVB_T_COLD by 0x04b4,0x8613. And now my device work like before. That a bit strange because this mean the uploaded firmware manage to read the i2c from eeprom (it does USB_PID_LITEON_DVB_T_COLD+1) I wonder if a module option can be added for such case ? Matthieu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Kaffeine 0.8.6 released
See http://kaffeine.kde.org -- Christophe Thommeret ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] RTL2831U driver
Did anyone ever distribute the code for this driver mentioned here: http://www.linuxtv.org/pipermail/linux-dvb/2007-November/022031.html If so, are there any plans for integration? _ Get Hotmail on your mobile, text MSN to 63463! http://mobile.uk.msn.com/pc/mail.aspx ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Which soft for a quick test (TT S2-3200 and multiproto)
Hi, As I write last week, I've tried to install the driver for my TT S2-3200 card, on Debian. I have an error at the end (see below), but I'd like to do a quick test to see if the card is OK. Do you know which soft can I use for this test ? Thank you very much. David. P.S. : my dmesg... saa7146: register extension 'budget_ci dvb'. ACPI: PCI Interrupt :05:01.0[A] - GSI 22 (level, low) - IRQ 22 saa7146: found saa7146 @ mem c20001450c00 (revision 1, irq 22) (0x13c2,0x1019). saa7146 (0): dma buffer size 192512 DVB: registering new adapter (TT-Budget S2-3200 PCI) adapter has MAC addr = 00:d0:5c:0b:a5:8b input: Budget-CI dvb ir receiver saa7146 (0) as /class/input/input4 budget_ci: CI interface initialised ACPI: PCI Interrupt :00:1b.0[A] - GSI 22 (level, low) - IRQ 22 PCI: Setting latency timer of device :00:1b.0 to 64 stb0899_write_regs [0xf1b6]: 02 stb0899_write_regs [0xf1c2]: 00 stb0899_write_regs [0xf1c3]: 00 _stb0899_read_reg: Reg=[0xf000], data=81 stb0899_get_dev_id: ID reg=[0x81] stb0899_get_dev_id: Device ID=[8], Release=[1] _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf334], Data=[0x444d4431] _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf33c], Data=[0x0001] stb0899_get_dev_id: Demodulator Core ID=[DMD1], Version=[1] _stb0899_read_s2reg Device=[0xfafc], Base address=[0x0800], Offset=[0xfa2c], Data=[0x46454331] _stb0899_read_s2reg Device=[0xfafc], Base address=[0x0800], Offset=[0xfa34], Data=[0x0001] stb0899_get_dev_id: FEC Core ID=[FEC1], Version=[1] stb0899_attach: Attaching STB0899 stb6100_attach: Attaching STB6100 DVB: registering frontend 0 (STB0899 Multistandard)... EXT3 FS on dm-0, internal journal loop: module loaded kjournald starting. Commit interval 5 seconds EXT3 FS on sda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-5, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-3, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-4, internal journal EXT3-fs: mounted filesystem with ordered data mode. Adding 2097144k swap on /dev/mapper/VG_Wilco-LV_Swap. Priority:-1 extents:1 across:2097144k ip_tables: (C) 2000-2006 Netfilter Core Team Netfilter messages via NETLINK v0.30. nf_conntrack version 0.5.0 (8192 buckets, 65536 max) ip6_tables: (C) 2000-2006 Netfilter Core Team skge eth1: enabling interface NET: Registered protocol family 10 lo: Disabled Privacy Extensions ADDRCONF(NETDEV_UP): eth1: link is not ready ctnetlink v0.93: registering with nfnetlink. ClusterIP Version 0.8 loaded successfully skge eth1: Link is up at 1000 Mbps, full duplex, flow control both ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready dvb_ca adaptor 0: PC card did not respond :( signature.asc Description: PGP signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Is this a bug ?
Hi, I'm using mythtv (020.2 on ubuntu gutsy) to watch amongst others DVB-S channels. I'm getting this log from mythbackend while tuning to an encrypted channel. My hardware is a nexus-s tuner with the dual CI module attached. In slot 0 I have a ZCAS (Matrix reloaded) CAM which has an official SECA2 licence. In that CAM I have an official subscription card Must say that I can see the encrypted channels fine under Kaffeine or vdr. Is the way mythtv addresses the CI interface incompatible with my hardware or is there something else going on? I will provide other logs if I can, but this is one taken with mythtvbackend -v channel thanks, Johan 2008-01-16 15:31:03.169 TVRec(8): HW Tuner: 8-8 2008-01-16 15:31:03.169 DVBChan(0): Opening DVB channel 2008-01-16 15:31:03.169 DVBChan(0): SetChannelByString(4): 2008-01-16 15:31:03.169 DVBChan(0): SetChannelByString(4): Already on channel 2008-01-16 15:31:03.183 DVBChan(0): Opening DVB channel 2008-01-16 15:31:03.185 SM(0)::AddFlags: Seen() Match() Wait(Sig,SNR,BER,UB,) 2008-01-16 15:31:03.185 DVBSM(0)::constructor(): initial flags 0x740 2008-01-16 15:31:03.488 DTVSM(0)::SetDVBService(transport_id: 1097, network_id: 53, service_id: 2004): 2008-01-16 15:31:03.488 SM(0)::RemoveFlags: Seen(PMT,SDT,) Match(PMT,SDT,) Wait() 2008-01-16 15:31:03.488 SM(0)::AddFlags: Seen() Match() Wait(PMT,SDT,) 2008-01-16 15:31:03.488 SM(0)::AddFlags: Seen() Match() Wait(PMT,SDT,) 2008-01-16 15:31:03.488 SM(0)::AddFlags: Seen() Match() Wait() 2008-01-16 15:31:03.488 SM(0)::Start: begin 2008-01-16 15:31:03.488 SM(0)::Start: end 2008-01-16 15:31:03.490 DVBSM(0)::UpdateValues: Signal Locked 2008-01-16 15:31:03.490 DVBSM(0)::UpdateValues: Waiting for table monitor to start 2008-01-16 15:31:03.490 DVBSM(0)::UpdateValues: Table monitor started 2008-01-16 15:31:03.490 DTVSM(0)::GetStatusList: WaitForPMT seen(0) matching(0) 2008-01-16 15:31:03.491 DVBSM(0)::AddPIDFilter(0x0): 2008-01-16 15:31:03.498 DVBSM(0)::RemovePIDFilter(0x0): 2008-01-16 15:31:03.508 DVBSM(0): RunTableMonitorTS(): begin (# of pids 3) 2008-01-16 15:31:03.508 DVBSM(0)::AddPIDFilter(0x0): 2008-01-16 15:31:03.514 DVBSM(0)::AddPIDFilter(0x10): 2008-01-16 15:31:03.522 DVBSM(0)::AddPIDFilter(0x11): 2008-01-16 15:31:03.552 SM(0)::AddFlags: Seen(SDT,) Match() Wait() 2008-01-16 15:31:03.553 DTVSM(0)::SetSDT(): tsid = 1097 orig_net_id = 53 2008-01-16 15:31:03.553 SM(0)::AddFlags: Seen() Match(SDT,) Wait() 2008-01-16 15:31:03.654 SM(0)::AddFlags: Seen(PAT,) Match() Wait() 2008-01-16 15:31:03.654 SM(0)::AddFlags: Seen() Match(PAT,) Wait() 2008-01-16 15:31:03.654 DVBSM(0)::AddPIDFilter(0x7d4): 2008-01-16 15:31:03.714 SM(0)::AddFlags: Seen(PMT,) Match() Wait() 2008-01-16 15:31:03.714 SM(0)::AddFlags: Seen() Match(PMT,) Wait() 2008-01-16 15:31:03.791 DTVSM(0)::GetStatusList: WaitForPMT seen(1) matching(1) 2008-01-16 15:31:03.791 DVBSM(0)::Stop: begin 2008-01-16 15:31:03.791 SM(0)::Stop: begin 2008-01-16 15:31:04.091 SM(0)::Stop: end 2008-01-16 15:31:04.130 DVBSM(0): RunTableMonitorTS(): shutdown 2008-01-16 15:31:04.130 DVBSM(0)::RemovePIDFilter(0x0): 2008-01-16 15:31:04.138 DVBSM(0)::RemovePIDFilter(0x10): 2008-01-16 15:31:04.146 DVBSM(0)::RemovePIDFilter(0x11): 2008-01-16 15:31:04.154 DVBSM(0)::RemovePIDFilter(0x7d4): 2008-01-16 15:31:04.162 DVBSM(0): RunTableMonitorTS(): end 2008-01-16 15:31:04.162 DVBSM(0)::Stop: end 2008-01-16 15:31:04.164 Finished recording RTL Travel: channel 3004 2008-01-16 15:31:04.190 Finished recording RTL Travel: channel 3004 2008-01-16 15:31:04.198 Preview Error: Previewer file '/var/lib/mythtv/recordings/3004_20080116153103.mpg' is not valid. 2008-01-16 15:31:04.200 DVB#0 CA: SetPMT() program num #2004 2008-01-16 15:31:04.232 DVB#0 CA: CiHandler needs CA_PMT 2008-01-16 15:31:04.232 DVB#0 CA: Creating CA_PMT, ServiceID = 2004 2008-01-16 15:31:04.232 Adding CA descriptor: CASID(0x622), ECM PID(0x565) 2008-01-16 15:31:04.232 Adding elementary stream: video-mpeg2, pid(0x200) 2008-01-16 15:31:04.232 Adding elementary stream: audio-mp2-layer[1,2,3] (dut), pid(0x50) 2008-01-16 15:31:04.232 Adding elementary stream: private-data, pid(0x20) 2008-01-16 15:31:04.232 Adding elementary stream: unknown, pid(0xd0) 2008-01-16 15:31:04.232 Adding elementary stream: unknown, pid(0xfa) 2008-01-16 15:31:04.232 DVB#0 CA: Sending CA_PMT with CPLM_ONLY to CI slot #0 2008-01-16 15:31:04.392 DVB#0 CA Error: GetCaSystemIds returned NULL! (Slot #1) 2008-01-16 15:31:05.673 DVB#0 CA: CAM: Menu Title: ZCAS 2008-01-16 15:31:05.673 DVB#0 CA: CAM: Menu SubTitle: 2008-01-16 15:31:05.673 DVB#0 CA: CAM: Menu BottomText: Press 'OK' to continue 2008-01-16 15:31:05.673 DVB#0 CA: CAM: Menu Entry: No right to watch this program 2008-01-16 15:31:05.674 DVB#0 CA: CAM: Selecting first entry 2008-01-16 15:31:23.335 TVRec(8): Changing from WatchingLiveTV to None 2008-01-16 15:31:23.554 Finished recording RTL Travel: channel 3004 ___ linux-dvb mailing list linux-dvb@linuxtv.org
[linux-dvb] [PATCH] ansonic branded dvb-t usb stick support in the af9005 driver
Hello,
a user (Marcos Melero, marcosmelero at gmail.com) reported he could make
his dvb-t usb stick work with the af9005 driver by changing the device
ids (10b9:6000).
The stick is branded Ansonic (one of the brands of a spanish chain of
supermarkets) with no other identification of the model.
Since neither Marcos nor me know the OEM for the stick, in the attached
patch I used Ansonic for the ids/description.
Feel free to change the ids or add to the description if you know the
real OEM.
Signed-off-by: Luca Olivetti [EMAIL PROTECTED]
Bye
--
Luca
diff -r 7564c110491e linux/drivers/media/dvb/dvb-usb/af9005.c
--- a/linux/drivers/media/dvb/dvb-usb/af9005.c Sun Jan 20 09:13:44 2008 -0200
+++ b/linux/drivers/media/dvb/dvb-usb/af9005.c Sun Jan 20 21:42:48 2008 +0100
@@ -1026,6 +1026,7 @@ static struct usb_device_id af9005_usb_t
static struct usb_device_id af9005_usb_table[] = {
{USB_DEVICE(USB_VID_AFATECH, USB_PID_AFATECH_AF9005)},
{USB_DEVICE(USB_VID_TERRATEC, USB_PID_TERRATEC_CINERGY_T_USB_XE)},
+ {USB_DEVICE(USB_VID_ANSONIC, USB_PID_ANSONIC_DVBT_USB)},
{0},
};
@@ -1075,7 +1076,7 @@ static struct dvb_usb_device_properties
.rc_key_map_size = 0,
.rc_query = af9005_rc_query,
- .num_device_descs = 2,
+ .num_device_descs = 3,
.devices = {
{.name = Afatech DVB-T USB1.1 stick,
.cold_ids = {af9005_usb_table[0], NULL},
@@ -1083,6 +1084,10 @@ static struct dvb_usb_device_properties
},
{.name = TerraTec Cinergy T USB XE,
.cold_ids = {af9005_usb_table[1], NULL},
+ .warm_ids = {NULL},
+ },
+ {.name = Ansonic DVB-T USB1.1 stick,
+ .cold_ids = {af9005_usb_table[2], NULL},
.warm_ids = {NULL},
},
{NULL},
diff -r 7564c110491e linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
--- a/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h Sun Jan 20 09:13:44 2008 -0200
+++ b/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h Sun Jan 20 18:07:31 2008 +0100
@@ -15,6 +15,7 @@
#define USB_VID_ALCOR_MICRO 0x058f
#define USB_VID_ALINK0x05e3
#define USB_VID_ANCHOR0x0547
+#define USB_VID_ANSONIC0x10b9
#define USB_VID_ANUBIS_ELECTRONIC 0x10fd
#define USB_VID_AVERMEDIA 0x07ca
#define USB_VID_COMPRO0x185b
@@ -53,6 +54,7 @@
#define USB_PID_ADSTECH_USB2_WARM 0xa334
#define USB_PID_AFATECH_AF90050x9020
#define USB_VID_ALINK_DTU0xf170
+#define USB_PID_ANSONIC_DVBT_USB 0x6000
#define USB_PID_AVERMEDIA_DVBT_USB_COLD 0x0001
#define USB_PID_AVERMEDIA_DVBT_USB_WARM 0x0002
#define USB_PID_AVERMEDIA_DVBT_USB2_COLD 0xa800
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] atsc closed captions
Jonathan Isom wrote: Hi I was wondering if anyone on the list knows of an app the displays atsc closed captions. I have a kworld atsc 110 and 115. Mythtv used to display cc data with the 110 but now doesn't which leads me to believe that locally they are broadcasting eia-708 now. Am I in the boat of waiting for this to be implemented or is there a way to get it working( preferably without mythtv required.). any ideas would be appreciated There is some introductory info about closed captions for digital in an v4l wiki article: http://www.linuxtv.org/v4lwiki/index.php/Text_capture I had begun editing it a while ago, but haven't got back to it. I don't really know/remember how helpful its contents would be for you. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle dual Hybrid pro PCI-express - linuxTV!
[EMAIL PROTECTED] wrote: Okay, I did everything you ask, here is the link to the wiki page : http://www.linuxtv.org/wiki/index.php/Pinnacle_Dual_Hybrid_Pro_PCI_Express If something is missing, don't hesitate to tell me! Selon CityK [EMAIL PROTECTED]: [EMAIL PROTECTED] wrote: Hello I red this on the wiki of Linuxtv.org: If you own one or more devices from the following list and you want to help with support development, please contact the linux-dvb Mailing list. Actually I own a Pinnacle dual hybrid pro PCIe (3010i) that is not supported by linux. I must watch TV under windows, and I hope one day I could watch it under Linux (my os = ubuntu x64) ! Therefore, I propose my help to develop the linuxTV project, even if I don't really know what I can do... Hi Romain, Thank you for contacting the list. The initial steps you can take to help are: a) provide the relevant output of: lspci -vvn -- which will provide the subsystem ID info, as well as confirm the PCIe bridge and from dmesg -- which may provide some other info about detected components upon the card b) visually identify and report what components are being used on the card c) start off an article for the card in the wiki (http://www.linuxtv.org/wiki/index.php/Pinnacle_Dual_Hybrid_Pro_PCI_Express) and hopefully also be able to upload some images of the device to that article. After which, everyone will be in a much better position to advise from there. Hopefully the components are similar to other supported devices, and it may be a question of some minor tinkering to get it supported. However, as support for PCIe based devices is relatively immature, it is more likely not to be such a case. But still, your device may be decently similar or related to someone's work (or interests) that they may be able to help you out in regards to support development -- but there is no guarantee. First things first though; lets see what info you can provide. Cheers Hi Romain, 1) Please don't top post 2) Please don't drop the mailing list from your reply (use the reply all feature of your email client) 3) To more accurately reflect the device's name, I've moved the wiki page to: http://www.linuxtv.org/wiki/index.php/Pinnacle_PCTV_Dual_Hybrid_Pro_PCI_Express_%283010i%29 In addition, I've applied our standard formatting for device articles. As opposed to external links to your page, would you like to upload the pictures to the wiki, as well as transfer over the text of the lspci output etc.. Thanks ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR-4000
Craig Whitmore wrote: Of course - it is a wiki after all! I updated the Wiki (http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-4000) with a lot of information Thanks Craig ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Which DVB-T on mips Arch. (openwrt) for wlan-dvb-streaming
Hi,
i want to stream dvb over air, using wgt634u and a dvb-usb stick in
combi with tzap,
dvbstream and mplayer (an my laptop) .
has anybody successfully used any usb-dvb-t device ...
I can compile and insmod (modprobe) the modules, firmware is loaded
successful (? as long
as dmesg is concerned) but i found no channels, cannot cat device
nor using dvbstream
(dvb_demux_feed_del: feed not in list (type=0 state=0 pid=)).
Thanks for any help.
Martin
here is my post on openwrt.org
i want to stream dvb over air, using wgt634u and a dvb-usb stick in
combi with tzap,
dvbstream and mplayer (an my laptop) .
i managed to compile i2c, the last dvb-modules and dvb-utils/apps.
I can load all modules without probs. i tried, two adapters
Afatech AF9005
and
AVerMedia AVerTV DVB-T Volar
the first prob. was that i the device-nodes where none standard.
so i put the following script
mkdir -p /dev/dvb/adapter0
ln -sf /dev/dvb0.frontend0 /dev/dvb/adapter0/frontend0
ln -sf /dev/dvb0.net0 /dev/dvb/adapter0/net0
ln -sf /dev/dvb0.demux0 /dev/dvb/adapter0/demux0
ln -sf /dev/dvb0.dvr0 /dev/dvb/adapter0/dvr0
when i use
./scan de-Muenchen
... i get no channel, but when i use
./tzap zdf -c channels.conf -r # with a channels.conf from my laptop
i get a lock, so i think something works
when i try now
cat /dev/dvb/adapter0/dvr0
i get nothing...
I assume a problem with i2c, usb, or udev (device-nodes).
using dvbstream, wasnt successful neither:
error: dvb_demux_feed_del: feed not in list (type=0 state=0 pid=)
./dvbstream -f 578000 -a 337 -v 338 -o tt2.mpg
dvbstream v0.7 - (C) Dave Chapman 2001-2004
Released under the GPL.
Latest version available from http://www.linuxstb.org/
Tuning to 578000 Hz
MT2060: successfully identified (IF1 = 1216)
Using DVB card AF9005 USB DVB-T, freq=578000
tuning DVB-T (in United Kingdom) to 57800 Hz, Bandwidth: 8
Getting frontend status
Event: Frequency: 57800
Bit error rate: 0
Signal strength: 40320
UNC: 0
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_VITERBI FE_HAS_SYNC
dvbstream will stop after -1 seconds (71582788 minutes)
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=)
Failed setting filter for pid 337: DMX SET PES FILTER: Invalid argument
Output to stdout
Streaming 3 streams
tt2.mpg is empty ... on my laptop, with the same usb-card, antenna
and at the same
location, everything works?
maybe somebody can help,
With udev and the following rule, dvb-devices named now correctly,
cat /etc/udev/rules.d/udev.rules
SUBSYSTEM==dvb, PROGRAM=/bin/sh -c 'X=%k; X=$${X#dvb};
A=$${X.*}; D=$${X#*.}; echo
dvb/adapter$$A/$$D', NAME=%c
ls /dev/dvb/adapter0/ -la
drwxr-xr-x2 root root 120 Jan 1 00:03 .
drwxr-xr-x3 root root 60 Jan 1 00:01 ..
crw-rw1 root root 212, 4 Jan 1 00:03 demux0
crw-rw1 root root 212, 5 Jan 1 00:03 dvr0
crw-rw1 root root 212, 3 Jan 1 00:03 frontend0
crw-rw1 root root 212, 7 Jan 1 00:03 net0
but the problems with zapping and dvbstream persists:
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=)
Failed setting filter for pid 337: DMX SET PES FILTER: Invalid argument
Output to stdout
Streaming 3 streams
Could it be a problem with loading the firmware. I wrote s.th. about
probs with firmware
and 64bit os.
? any ideas?
dvb-usb: found a 'Afatech DVB-T USB1.1 stick' in cold state, will try
to load a firmware
dvb-usb: downloading firmware from file 'af9005.fw'
dvb-usb: found a 'Afatech DVB-T USB1.1 stick' in warm state.
dvb-usb: will use the device's hardware PID filter (table count: 32).
DVB: registering new adapter (Afatech DVB-T USB1.1 stick)
DVB: registering frontend 0 (AF9005 USB DVB-T)...
input: IR-receiver inside an USB DVB receiver as /class/input/input1
dvb-usb: schedule remote query interval to 200 msecs.
dvb-usb: Afatech DVB-T USB1.1 stick successfully initialized and connected.
MT2060: successfully identified (IF1 = 1216)
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=)
dvb_demux_feed_del: feed not in list (type=0 state=0 pid=)
This message was sent using IMP, the Internet Messaging Program.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR-4000
On Sat, Jan 19, 2008 at 09:36:08PM +1300, Craig Whitmore wrote: I updated the Wiki (http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-4000) with a lot of information I can't test the multiproto stuff as the latest kernel doesn't work correctly with the latest kernel (2.6.23.14). I use the HVR4000 every day with these drivers with no problems at all. I should have written that I use 2.6.23 which compil fine... and because an HVR-4000 without DVB-S2 isn't usefull at all for me I stay with this kernel as long as I can't compil multiproto against a newer kernel. What we need is someone to start to write the support for multiple frontends so we can get the DVB-S and DVB-T enabled at the same time. (Steven's patches for multiple frontends for the HVR3000 work but they are very out of date and don't work with the latest kernels) Why aren't you trying with 2.6.23 for a start ??? Feel free to edit all changes I did, like you did for multiproto and firmware :-) -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] build system: fix for kernel output dir != kernel source dir
Hi,
I'd really like to get some feedback from people who are used to
the build system.
Reinhard Nissl schrieb:
most distributions use separate kernel output directories to be
able to build several kernels from the same source tree.
Building the multiproto tree in such an environment fails either
as .config is not found or some kernel source files are not found
(i. e. compiler.h).
The attached patch therefore introduces SDIR which points to the
kernel sources and passes it as an additional argument to some
scripts which need to access .config or source files for example.
The patch is still incomplete i. e. not all references to kernel
source or output directories have been adapted and tested. But
the patch is sufficient for successfully running make and make
distclean in such an environment.
Would some developers with deeper knowledge about the kernel
build system comment whether my patch is going in the right
direction and how to solve other references (e. g. the lxdialog
stuff)?
Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:[EMAIL PROTECTED]
diff --git a/v4l/Makefile b/v4l/Makefile
--- a/v4l/Makefile
+++ b/v4l/Makefile
@@ -16,11 +16,14 @@ else
ifneq ($(SRCDIR),)
KDIR := $(SRCDIR)
+SDIR := $(SRCDIR)
else
ifneq ($(KERNELRELEASE),)
KDIR := /lib/modules/$(KERNELRELEASE)/build
+SDIR := /lib/modules/$(KERNELRELEASE)/source
else
KDIR := /lib/modules/$(shell uname -r|perl -ne 'if (/^([0-9]*)\.([0-9])*\.([0-9]*)(.*)$$/) { printf (%s.%s.%s%s\n,$$1,$$2,$$3,$$4); };')/build
+SDIR := /lib/modules/$(shell uname -r|perl -ne 'if (/^([0-9]*)\.([0-9])*\.([0-9]*)(.*)$$/) { printf (%s.%s.%s%s\n,$$1,$$2,$$3,$$4); };')/source
endif
endif
@@ -239,7 +242,7 @@ oss:
ln -sf . oss
config-compat.h:: $(obj)/.version .myconfig
- perl scripts/make_config_compat.pl $(KDIR) $(obj)/.myconfig $(obj)/config-compat.h
+ perl scripts/make_config_compat.pl $(KDIR) $(SDIR) $(obj)/.myconfig $(obj)/config-compat.h
kernel-links makelinks::
cd ..; v4l/scripts/makelinks.sh $(KDIR)
@@ -309,10 +312,10 @@ endif
$(obj)/.config: $(obj)/.version
@echo Updating/Creating .config
@if [ -e $(obj)/.config ]; then touch $(obj)/.config ; else \
- ./scripts/make_kconfig.pl $(KDIR) ; fi
+ ./scripts/make_kconfig.pl $(KDIR) $(SDIR) ; fi
$(obj)/Kconfig: $(obj)/.version
- ./scripts/make_kconfig.pl $(KDIR)
+ ./scripts/make_kconfig.pl $(KDIR) $(SDIR)
# With make -j, it's possible that both the .config and Kconfig rules
# will run at the same time, running make_kconfig.pl twice. There
@@ -332,7 +335,7 @@ menuconfig:: $(MCONF) lxdialog $(obj)/Kc
$(MCONF) $(obj)/Kconfig
allyesconfig allmodconfig:: $(obj)/.version
- ./scripts/make_kconfig.pl $(KDIR) 1
+ ./scripts/make_kconfig.pl $(KDIR) $(SDIR) 1
# rule to build kernel conf programs
KMAKEVARS := config-targets=1 mixed-targets=0 dot-config=0
diff --git a/v4l/scripts/make_config_compat.pl b/v4l/scripts/make_config_compat.pl
--- a/v4l/scripts/make_config_compat.pl
+++ b/v4l/scripts/make_config_compat.pl
@@ -1,7 +1,8 @@
#!/usr/bin/perl
use strict;
-my $kdir=shift or die should specify a kernel dir;
+my $kdir=shift or die should specify a kernel output dir;
+my $sdir=shift or die should specify a kernel source dir;
my $infile=shift or die should specify an input config file;
my $outfile=shift or die should specify an output config file;
@@ -9,7 +10,7 @@ my $out;
sub check_spin_lock()
{
- my $file = $kdir/include/linux/netdevice.h;
+ my $file = $sdir/include/linux/netdevice.h;
my $old_syntax = 1;
open INNET, $file or die File not found: $file;
diff --git a/v4l/scripts/make_kconfig.pl b/v4l/scripts/make_kconfig.pl
--- a/v4l/scripts/make_kconfig.pl
+++ b/v4l/scripts/make_kconfig.pl
@@ -13,7 +13,8 @@ my %depmods = ();
my %depmods = ();
my ($version, $level, $sublevel, $kernver);
-my $kernel = shift;
+my $kdir = shift;
+my $sdir = shift;
my $force_kconfig = shift;
my $debug=0;
@@ -480,7 +481,7 @@ print Preparing to compile for kernel v
print Preparing to compile for kernel version $kernver\n;
# Get Kernel's config settings
-%kernopts = process_config($kernel/.config);
+%kernopts = process_config($kdir/.config);
# Modules must be on, or building out of tree drivers makes no sense
if(!$kernopts{MODULES}) {
@@ -542,7 +543,7 @@ disable_config('VIDEO_HELPER_CHIPS_AUTO'
disable_config('VIDEO_HELPER_CHIPS_AUTO');
# ACI needs some kernel includes that might not be there
-disable_config('SOUND_ACI_MIXER') if (! -e $kernel/sound/oss/sound_config.h);
+disable_config('SOUND_ACI_MIXER') if (! -e $sdir/sound/oss/sound_config.h);
# Check dependencies
my %newconfig = checkdeps();
@@ -595,7 +596,7 @@ if ($force_kconfig==1 || !-e '.config')
# Check for full kernel sources and print a warning
sub kernelcheck()
{
- my $fullkernel=$kernel/fs/fcntl.c;
+ my $fullkernel=$sdir/fs/fcntl.c;
if (! -e $fullkernel) {
print EOF2;
___
linux-dvb mailing list
linux-dvb@linuxtv.org
Re: [linux-dvb] Update to au-Melbourne scan list
On Monday 21 January 2008, Bruce Schultz wrote: On 20/01/08 20:47, Peter D. wrote: On Sunday 20 January 2008, Jeff Bailes wrote: Hi, Back in November, channel Seven changed their fec_hi from 2/3 to 3/4 causing scans to not pick it up ( http://www.dba.org.au/index.asp?sectionID=39newsID=982display=news ). The new entry in the au-Melbourne file for channel seven should be: # Seven T 17750 7MHz 3/4 NONE QAM64 8k 1/16 NONE I attached the complete updated file anyway. Jeff They are a pain. Anyway, according to the web site that you quoted, all tuners that comply with Australian standards will cope without adjustment. Unfortunately not all tuners comply with Australian standards. :-( Presumably all au-tuning_files should have their channel 7 entry updated. Can this be done at the data base end, or do all files have to be re-submitted? Also the GI in Brisbane is noted as changing as well. I can confirm that the au-Brisbane scan file needs to change. It works now for me with the same channel 7 line that Jeff included above. Scan wasn't finding channel 7 without the change. Did you just change fec_hi, or did you change the Guard Interval as well? The quoted web page states that the GI is now 1/16. (It is possible that your card is smart enough to sort out GI by itself, but not fec_hi.) -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] atsc closed captions
Jonathan Isom wrote: Thanks The only program data is a patch by Scott Larson from 2005 for mplayer. Other than that the wikipedia links may be useful for implementing it in other programs. I think it would be nice to write a library that every one could use but it wouldn't be to complicated to adapt the code once completed to other programs. That said if a channel isn't already broadcasting 708 in the us they probably will within about a year or so. I guess I may bug someone else about this as I don't think the driver level is the best place for the aforementioned code. I was just hoping someone hear may have knew something as this is somewhat dvb related. though not driver layer. Provided that the drivers are currently capable of serving up the data, then yes, this really isn't the place to pester/bug. However, your idea of a library for which all viewing apps could make use of is interesting. This might even be suitable for a GSoC project, but then again I'm uncertain whether this would actually be something that would take up most of a summer to implement. Others on the list most certainly would have some more concrete thoughts on this suggestion. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] atsc closed captions
CityK wrote: Jonathan Isom wrote: Hi I was wondering if anyone on the list knows of an app the displays atsc closed captions. I have a kworld atsc 110 and 115. Mythtv used to display cc data with the 110 but now doesn't which leads me to believe that locally they are broadcasting eia-708 now. Am I in the boat of waiting for this to be implemented or is there a way to get it working( preferably without mythtv required.). any ideas would be appreciated There is some introductory info about closed captions for digital in an v4l wiki article: http://www.linuxtv.org/v4lwiki/index.php/Text_capture I had begun editing it a while ago, but haven't got back to it. I don't really know/remember how helpful its contents would be for you. They're buried in the video stream, 708 format IIRC. It's pretty trivial to extract them and it should be done but the application (shared library?), it's not a kernel - Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [v4l-dvb-maintainer] [PATCH 1/2] bt878: remove handcrafted PCI subsystem ID check
On Sun, 20 Jan 2008, Mauro Carvalho Chehab wrote:
On Sat, 19 Jan 2008 05:28:49 -0800 (PST)
Trent Piepho [EMAIL PROTECTED] wrote:
I wish people would use the patch creating system from Hg, since it would
the format mistakes evident in this patch.
1. no patch title
2. s-o-b's in wrong order
3. diffstat included
4. patch against git source and not hg
On Sat, 19 Jan 2008, Akinobu Mita wrote:
From: Akinobu Mita [EMAIL PROTECTED]
This patch moves the subsystem ID and subsystem vendor ID check from
probing
function to the PCI generic function by describing subsystem IDs in
pci_device_id table. This enables to add new PCI IDs to a device driver
pci_ids
table at runtime by new_id file in sysfs pci driver tree.
This patch also changes the driver from having a pci alias to auto-load for
all bt878 cards to instead only auto-load for specific cards. Some
distributions will probably want to adjust their modprobe rules. I know
some have delt with both snd-bt87x and bt878 loading for the same devices
in various ways, e.g. adding one or the other to their modprobe blacklist
files.
The proper solution here seems to be moving snd-bt87x to our tree, and create
some shared code to be used by snd-bt87x, dvb-bt8xx, to avoid the
driver conflicts.
That doesn't solve the problem. It's inherent in the bt878 design, as it
uses the same pci function for either sound or dvb. So a bt878 chip
function 1 can load one and only one driver from ALSA, OSS, or DVB. For
most chips, there is only one driver that applies to a given pci device and
function.
In some cases it is possible to tell which driver to use via
sub-vendor/device data, but not always. The ALSA driver only auto-loads
for known good subdata, and has a module option to force loading when that
won't work. The DVB driver has the wildcard sub-vendor/device in the alias
table, IMHO a mistake, and will try to load for for all bt878 chips.
The DVB driver used to load for cards with sub-vendor/device 0x,0x,
but a previous patch changed that. An effect that that _should_ have been
mentioned in the description of the patch responsible, but was not.
This patch changes the DVB driver to not auto-load for all bt878 chips. A
rather significant change that should be described in the patch
description, but is not.
+static const char * __devinit card_name(const struct pci_device_id *id)
+{
+ if (id = bt878_pci_tbl
+ id bt878_pci_tbl + ARRAY_SIZE(bt878_pci_tbl) - 1)
+ return (const char *)id-driver_data;
Are you sure this is safe? I don't remember reading that the pci_device_id
passed to the pci driver probe method must be from the device id table.
Couldn't the device id be a local variable from whatever calls probe, as
long as driver_data is set to the correct value? I looked at the current
pci bus code, and it does always pass a pointer into the driver's pci id
table. But that could change.
It seems like a better method would just be to check if driver_data is 0,
which will be the case if the id was added dynamically.
This data can't be changed by pci core, since driver_data is a priv element.
It
is used as a pointer on some drivers, while others use it as an integer value
to
an array (like most V4L/DVB and ALSA drivers). The above code should work
properly. If pci touches on this value, it would break the support for the
rest
of v4l/dvb drivers, so I think we don't need to worry about this.
I don't think you understand. That code checks if the pci_device_id
pointer passed to the probe function points to a spot in the driver's pci
id table. It has nothing to do with the driver_data field being modified.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] AVermedia M791 Combo OEM TV Card
[EMAIL PROTECTED] wrote: [UPDATE] XCeive XC3028 (tuner) analog MicroTune MT2131 (tuner) digital LG LGDT3303 (8VSB/QAM demodulator) Conexant CX23887-14z (A/V Decoder PCIe bridge) Conexant CX23417-11z (MPEG-2 A/V Encoder) ESMT M12L04322A-AZG1P633X (SDRAM used by encoder) also have inf if any one is intrested I see from the inf that AVer actually have two M791 cards - one with MPEG-2 encoder (your model) and one without Anyway, getting your card to work is going to involve stringing together the above combination of ICs together (all of which are supported, to one degree or another) in the existing drivers: - the MT2131 appears on a number of the new Hauppauge cards (hvr-1800, 1600, 1250,..) - the CX23887 CX23417 combination on the Hauppauge hvr-1800 - the LGDT3303 on a number of devices (in particular interest should be the F5 Express, because of its LGDT3303 CX23885 .. though note that its a '885, as opposed to being the '887) - XC3028 appears in a number of devices, an analogue support for it should work (provided firmware is provided ... maybe found in the *.sys file or perhaps the merlin.rom file, though I think the merlin rom is related to the '417 iirc) You might also want to identify: - From the photo you uploaded to the wiki, it appears that the card also has two audio ADCs for the external A/V inputs ... (you can find them on the top right area of the face of the PCB ... long, rectangular ICs near the white A/V expansion connectors - the 8pin EEPROM IC (bottom right on face of the PCB)...likely an Atmel, and likely not really a worry (should just work), but nice to know I rolled back you edit from yesterday (re: cx23888 ... despite what the inf states, it is readily apparent that its the cx23887 that is being employed on the card) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle 800i - obsolete tuner i2c address?
On Jan 20, 2008 7:20 AM, Michael Krufky [EMAIL PROTECTED] wrote: Tim, In the future, please don't dropp cc from the mailing list. Steve, Chaogui's patch fixed Tim's XC5000 initialization problem -- we should merge it if all is well with it. Please see below. -Mike Timothy E. Krantz wrote: John, Sorry for sending this twice -- I sent it the first time from an email address not subscribed to linux-dvb :-/ John Massengale wrote: I got the Pinnacle 800i working on Mythbuntu, I can tune both analog and digital channels, but if I reboot, for some reason it starts having problems. Thanks for sending in the obsolete tuner address message -- I'll remove this warning for the XC5000 tuners. Unfortunately, I don't know why your tuner isn't working after a reboot... Perhaps the device gets held in reset after a reboot, and it isn't properly being taken out as needed? Try the patch in this email and let us know if that fixes the problem: http://linuxtv.org/pipermail/linux-dvb/2008-January/022977.html Regards, Mike That patch resolved the problem for me. Tim That patch seems to have made the card stable on my system now. I have my fingers crossed. Thanks! I can't tell you guys how much I appreciate the help with this. Where my other cards, the ATI HDTV Wonder and the Kworld 110 ATSC can barely pick up anything over the air, even with a good antenna, the Pinnacle 800i picks up pretty much everything using an antenna I made from 6 coat hangers and a 2x4! (and it's not even amplified, no pre-amp, nothing) Amazing! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle dual Hybrid pro PCI-express - linuxTV!
CityK wrote: I've moved the wiki page to: http://www.linuxtv.org/wiki/index.php/Pinnacle_PCTV_Dual_Hybrid_Pro_PCI_Express_%283010i%29 In addition, I've applied our standard formatting for device articles. As opposed to external links to your page, would you like to upload the pictures to the wiki, as well as transfer over the text of the lspci output etc.. Hi Romain, I just noticed you applied those changes - Thanks. I made a few minor corrections (removed use of the first person, image arrangements, removed proprietary image of the RC (we would need Pinnacle's permission for use), id'ed the demod). Unfortunately, the Philips saa7162 is currently a roadblock for your card (i.e. no support for that IC yet). However, I suspect that situation will resolve itself in the coming months. Until then you're stuck with having to use Windows. One other thing you might want to try to find is what tuners the card is using -- try searching through the Windows driver inf file for mention of such ... quite likely they used a Philips ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [v4l-dvb-maintainer] [PATCH 1/2] bt878: remove handcrafted PCI subsystem ID check
Trent Piepho wrote:
On Sun, 20 Jan 2008, Mauro Carvalho Chehab wrote:
On Sat, 19 Jan 2008 05:28:49 -0800 (PST)
Trent Piepho [EMAIL PROTECTED] wrote:
I wish people would use the patch creating system from Hg, since it would
the format mistakes evident in this patch.
1. no patch title
2. s-o-b's in wrong order
3. diffstat included
4. patch against git source and not hg
On Sat, 19 Jan 2008, Akinobu Mita wrote:
From: Akinobu Mita [EMAIL PROTECTED]
This patch moves the subsystem ID and subsystem vendor ID check from
probing
function to the PCI generic function by describing subsystem IDs in
pci_device_id table. This enables to add new PCI IDs to a device driver
pci_ids
table at runtime by new_id file in sysfs pci driver tree.
This patch also changes the driver from having a pci alias to auto-load for
all bt878 cards to instead only auto-load for specific cards. Some
distributions will probably want to adjust their modprobe rules. I know
some have delt with both snd-bt87x and bt878 loading for the same devices
in various ways, e.g. adding one or the other to their modprobe blacklist
files.
The proper solution here seems to be moving snd-bt87x to our tree, and create
some shared code to be used by snd-bt87x, dvb-bt8xx, to avoid the
driver conflicts.
That doesn't solve the problem. It's inherent in the bt878 design, as it
uses the same pci function for either sound or dvb. So a bt878 chip
function 1 can load one and only one driver from ALSA, OSS, or DVB. For
most chips, there is only one driver that applies to a given pci device and
function.
In some cases it is possible to tell which driver to use via
sub-vendor/device data, but not always. The ALSA driver only auto-loads
for known good subdata, and has a module option to force loading when that
won't work. The DVB driver has the wildcard sub-vendor/device in the alias
table, IMHO a mistake, and will try to load for for all bt878 chips.
True.
The DVB driver used to load for cards with sub-vendor/device 0x,0x,
but a previous patch changed that. An effect that that _should_ have been
mentioned in the description of the patch responsible, but was not.
This doesn't have anything to do with accessing the wrong PCI function
as what
you have been trying to explain, as PCI function is based on Device ID
and not
SubDevice ID .. (pointless)
This patch changes the DVB driver to not auto-load for all bt878 chips. A
rather significant change that should be described in the patch
description, but is not.
A noise out for nothing, that shouldn't have mattered ? But anyhow, the
patch a
while back changed that behaviour, the driver being loaded for all the
devices.
So how come this patch needs to have that description ?
+static const char * __devinit card_name(const struct pci_device_id *id)
+{
+ if (id = bt878_pci_tbl
+ id bt878_pci_tbl + ARRAY_SIZE(bt878_pci_tbl) - 1)
+ return (const char *)id-driver_data;
Are you sure this is safe? I don't remember reading that the pci_device_id
passed to the pci driver probe method must be from the device id table.
Couldn't the device id be a local variable from whatever calls probe, as
long as driver_data is set to the correct value? I looked at the current
pci bus code, and it does always pass a pointer into the driver's pci id
table. But that could change.
It seems like a better method would just be to check if driver_data is 0,
which will be the case if the id was added dynamically.
This data can't be changed by pci core, since driver_data is a priv element.
It
is used as a pointer on some drivers, while others use it as an integer
value to
an array (like most V4L/DVB and ALSA drivers). The above code should work
properly. If pci touches on this value, it would break the support for the
rest
of v4l/dvb drivers, so I think we don't need to worry about this.
I don't think you understand. That code checks if the pci_device_id
pointer passed to the probe function points to a spot in the driver's pci
id table. It has nothing to do with the driver_data field being modified.
what's the harm in it ?
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] AVermedia M791 Combo OEM TV Card
On Sun, 2008-01-20 at 18:24 -0500, CityK wrote: [EMAIL PROTECTED] wrote: [UPDATE] XCeive XC3028 (tuner) analog MicroTune MT2131 (tuner) digital LG LGDT3303 (8VSB/QAM demodulator) Conexant CX23887-14z (A/V Decoder PCIe bridge) Conexant CX23417-11z (MPEG-2 A/V Encoder) ESMT M12L04322A-AZG1P633X (SDRAM used by encoder) also have inf if any one is intrested I see from the inf that AVer actually have two M791 cards - one with MPEG-2 encoder (your model) and one without Anyway, getting your card to work is going to involve stringing together the above combination of ICs together (all of which are supported, to one degree or another) in the existing drivers: - the MT2131 appears on a number of the new Hauppauge cards (hvr-1800, 1600, 1250,..) - the CX23887 CX23417 combination on the Hauppauge hvr-1800 - the LGDT3303 on a number of devices (in particular interest should be the F5 Express, because of its LGDT3303 CX23885 .. though note that its a '885, as opposed to being the '887) - XC3028 appears in a number of devices, an analogue support for it should work (provided firmware is provided ... maybe found in the *.sys file or perhaps the merlin.rom file, though I think the merlin rom is related to the '417 iirc) You might also want to identify: - From the photo you uploaded to the wiki, it appears that the card also has two audio ADCs for the external A/V inputs ... (you can find them on the top right area of the face of the PCB ... long, rectangular ICs near the white A/V expansion connectors - the 8pin EEPROM IC (bottom right on face of the PCB)...likely an Atmel, and likely not really a worry (should just work), but nice to know I rolled back you edit from yesterday (re: cx23888 ... despite what the inf states, it is readily apparent that its the cx23887 that is being employed on the card) thanx for clarifiying that issue. why it would mention the cx23888 is beyound me. On line 60 it mentions XC3028+23417, MT2131+LG3303 at the end of the line but i have no idea what it means the cx23417 is an encoder and the lg3303 is a vsb/qam reciever. - The merlinC.rom has some thing to do with the audio as mentioned in the inf file line numbers 648 and 649 ; Merlin Rev. C audio firmware merlinC.rom I thought maybe the cx416enc.rom was the firmware but i might be wrong. How do you remove firmware from a *.sys file. what should its name be so the drivers can find it. i know i goes in the /lib/firmware directory --- Also if i load the driver with the option card=4 $ sudo modprobe -v cx23885 card=4 i get this as the dmesg output $ dmesg | grep cx [ 2184.687447] cx23885 driver version 0.0.1 loaded [ 2184.687514] CORE cx23885[0]: subsystem: 1461:d439, board: DViCO FusionHDTV5 Express [card=4,insmod option] [ 2184.787753] cx23885[0]: i2c bus 0 registered [ 2184.787906] cx23885[0]: i2c bus 1 registered [ 2184.787957] cx23885[0]: i2c bus 2 registered [ 2184.814898] cx23885[0]: cx23885 based dvb card [ 2184.815360] DVB: registering new adapter (cx23885[0]) [ 2184.815538] cx23885_dev_checkrevision() Hardware revision = 0xb1 [ 2184.815549] cx23885[0]/0: found at :03:00.0, rev: 15, irq: 17, latency: 0, mmio: 0x9300 but if i try any of the other card=1 options: $ sudo modprobe -v cx23885 card=1 i get this as my dmesg output: $ dmesg | grep cx [ 2617.106716] cx23885 driver version 0.0.1 loaded [ 2617.106779] CORE cx23885[0]: subsystem: 1461:d439, board: Hauppauge WinTV-HVR1800lp [card=1,insmod option] [ 2617.207017] cx23885[0]: i2c bus 0 registered [ 2617.207172] cx23885[0]: i2c bus 1 registered [ 2617.207322] cx23885[0]: i2c bus 2 registered [ 2617.234336] cx23885[0]: warning: unknown hauppauge model #0 [ 2617.234337] cx23885[0]: hauppauge eeprom: model=0 [ 2617.234338] cx23885[0]: cx23885 based dvb card [ 2617.265140] cx23885[0]: frontend initialization failed [ 2617.265144] cx23885_dvb_register() dvb_register failed err = -1 [ 2617.265147] cx23885_dev_setup() Failed to register dvb adapters on VID_C [ 2617.265152] cx23885_dev_checkrevision() Hardware revision = 0xb1 [ 2617.265158] cx23885[0]/0: found at :03:00.0, rev: 15, irq: 17, latency: 0, mmio: 0x9300 card=2: $ sudo modprobe -v cx23885 card=2 dmesg output $ dmesg | grep cx [ 2799.798252] cx23885 driver version 0.0.1 loaded [ 2799.798322] CORE cx23885[0]: subsystem: 1461:d439, board: Hauppauge WinTV-HVR1800 [card=2,insmod option] [ 2799.958512] cx23885[0]: i2c bus 0 registered [ 2799.958671] cx23885[0]: i2c bus 1 registered [ 2799.958729] cx23885[0]: i2c bus 2 registered [ 2799.985743] cx23885[0]: warning: unknown hauppauge model #0 [ 2799.985746] cx23885[0]: hauppauge eeprom: model=0 [ 2799.985791] cx23885[0]/0: registered device video0 [v4l2] [ 2799.985797]
Re: [linux-dvb] Which soft for a quick test (T T S2-3200 and multiproto)
szap2 can help you http://abraham.manu.googlepages.com/szap.c Igor As I write last week, I've tried to install the driver for my TT S2-3200 card, on Debian. I have an error at the end (see below), but I'd like to do a quick test to see if the card is OK. Do you know which soft can I use for this test ? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] AVermedia M791 Combo OEM TV Card
On Sun, 2008-01-20 at 18:24 -0500, CityK wrote: [EMAIL PROTECTED] wrote: [UPDATE] XCeive XC3028 (tuner) analog MicroTune MT2131 (tuner) digital LG LGDT3303 (8VSB/QAM demodulator) Conexant CX23887-14z (A/V Decoder PCIe bridge) Conexant CX23417-11z (MPEG-2 A/V Encoder) ESMT M12L04322A-AZG1P633X (SDRAM used by encoder) also have inf if any one is intrested I see from the inf that AVer actually have two M791 cards - one with MPEG-2 encoder (your model) and one without Anyway, getting your card to work is going to involve stringing together the above combination of ICs together (all of which are supported, to one degree or another) in the existing drivers: - the MT2131 appears on a number of the new Hauppauge cards (hvr-1800, 1600, 1250,..) - the CX23887 CX23417 combination on the Hauppauge hvr-1800 - the LGDT3303 on a number of devices (in particular interest should be the F5 Express, because of its LGDT3303 CX23885 .. though note that its a '885, as opposed to being the '887) - XC3028 appears in a number of devices, an analogue support for it should work (provided firmware is provided ... maybe found in the *.sys file or perhaps the merlin.rom file, though I think the merlin rom is related to the '417 iirc) You might also want to identify: - From the photo you uploaded to the wiki, it appears that the card also has two audio ADCs for the external A/V inputs ... (you can find them on the top right area of the face of the PCB ... long, rectangular ICs near the white A/V expansion connectors - the 8pin EEPROM IC (bottom right on face of the PCB)...likely an Atmel, and likely not really a worry (should just work), but nice to know I rolled back you edit from yesterday (re: cx23888 ... despite what the inf states, it is readily apparent that its the cx23887 that is being employed on the card) Uploaded pictuers to the and information to the AVermedia M791 Combo OEM TV Card wiki the two audio ADC's AVerMedia_M791-A_OEM_74HC4052D.jpg there both the same the eeprom AVerMedia_M791-A_OEM_S24CS0.jpg ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] AVermedia M791 Combo OEM TV Card
Eric wrote: thanx for clarifiying that issue. why it would mention the cx23888 is beyound me. the cx2388[5-8] are of the same family, so perhaps they've just decided to use cx23888 for their notation. Although imprecise, it is their option ... not really a big deal though ... nor different from all the other mistakes found in inf files from various vendors On line 60 it mentions XC3028+23417, MT2131+LG3303 at the end of the line but i have no idea what it means the cx23417 is an encoder and the lg3303 is a vsb/qam reciever. its just their notation for the signal flow for analog and digital functions respectively. Note that line 60 begins with mention of the the A/V decoder, so they've just truncated the actual pathway. The real signal path for analog would be: xc3028 (tuning and IF demodulation) - '887 ( A/V decoding) - '417 (MPEG-2 encoding of A/V) - '887 (bridge to PCIe) or if you want to run it in raw mode (i.e. circumvent the encoder): xc3028 (tuning and IF demodulation) - '887 ( A/V decoding bridge to PCIe) For digital: MT2131 (tuning) - lg3303 (IF demodulation, outputs Transport Stream) - '887 (bridge to PCIe) - The merlinC.rom has some thing to do with the audio as mentioned in the inf file line numbers 648 and 649 ; Merlin Rev. C audio firmware merlinC.rom ahh, looks like the MerlinC.rom will be the firmware for the XC3028 that provides analog functionality I thought maybe the cx416enc.rom was the firmware but i might be wrong. The cx416enc.rom is the firmware for the encoder '417 encoder ... I don't think there is much or any change in the encoder between the '416 and '417, hence the firmware name How do you remove firmware from a *.sys file. There is no real easy answer. It is, however, somewhat of a FAQ (I think you're the 3rd or 4th person to ask in this past month alone)and consequently why the following article has been commenced: http://www.linuxtv.org/wiki/index.php/Development:_How_to_extract_a_firmware For examples with the XC3028, see this thread for some info: http://marc.info/?l=linux-videom=119907938422926w=2 what should its name be so the drivers can find it. i know i goes in the /lib/firmware directory What the name should be will depend upon how its coded as in the drivers. Besides for the xc3028, this also holds true for the '417 firmware too. Check the source for hvr-1800 card to see what the name for the '417's firmware should be (look in an stoth repo, the name of which should likely be self explanatory) Also if i load the driver with the option card=4 $ sudo modprobe -v cx23885 card=4 i get ...[snip]... and soforth for the rest of them. Things won't work that way -- you have to make the changes in the drivers --- tie all the pieces together ... and even after doing that, you make need to do some fiddling to get everything working properly, as the way things are implemented on your card might not be exactly as they have been done so on other cards using the same chips would the firmware for the card=4 - DViCO FusionHDTV5 Express work and which firmware would it be. No. First, the F5 Express doesn't use any firmware. Second, as just mentioned, its a case of being a little more involved then just putting a firmware in place.consider it like this: you've assembled before yourself a steering wheel, 4 tires, an engine and etc etc etc . Do you have a car? No. You have all the pieces for a car, but you're still going to have to put them all together before you have a working car. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [v4l-dvb-maintainer] [PATCH 1/2] bt878: remove handcrafted PCI subsystem ID check
On Mon, 21 Jan 2008, Manu Abraham wrote:
Trent Piepho wrote:
The DVB driver used to load for cards with sub-vendor/device 0x,0x,
but a previous patch changed that. An effect that that _should_ have been
mentioned in the description of the patch responsible, but was not.
This doesn't have anything to do with accessing the wrong PCI function
as what
you have been trying to explain, as PCI function is based on Device ID
and not
SubDevice ID .. (pointless)
I never said anything about access the wrong pci function. That's not a
problem. The problem is that there are different mutually exclusive
drivers for the same pci function.
This patch changes the DVB driver to not auto-load for all bt878 chips. A
rather significant change that should be described in the patch
description, but is not.
A noise out for nothing, that shouldn't have mattered ? But anyhow, the
patch a
while back changed that behaviour, the driver being loaded for all the
devices.
So how come this patch needs to have that description ?
No, the previous patch changed a different behavior. You don't seem to be
aware there is a difference between what the pci driver's probe function
will pass, and what PCI aliases are encoded into the module for
auto-loading purposes. An older applied patch had the *undocumented
side-effect* of changing the pci probe function to not drive devices with
the sub-vendor and sub-device of 0. This patch has the undocumented
side-effect of changing the pci aliases embedded in the module so that it
will not be auto-loaded for all sub-vendors/devices.
+static const char * __devinit card_name(const struct pci_device_id *id)
+{
+if (id = bt878_pci_tbl
+id bt878_pci_tbl + ARRAY_SIZE(bt878_pci_tbl) - 1)
+return (const char *)id-driver_data;
Are you sure this is safe? I don't remember reading that the
pci_device_id
passed to the pci driver probe method must be from the device id table.
Couldn't the device id be a local variable from whatever calls probe, as
long as driver_data is set to the correct value? I looked at the current
pci bus code, and it does always pass a pointer into the driver's pci id
table. But that could change.
It seems like a better method would just be to check if driver_data is 0,
which will be the case if the id was added dynamically.
This data can't be changed by pci core, since driver_data is a priv
element. It
is used as a pointer on some drivers, while others use it as an integer
value to
an array (like most V4L/DVB and ALSA drivers). The above code should work
properly. If pci touches on this value, it would break the support for the
rest
of v4l/dvb drivers, so I think we don't need to worry about this.
I don't think you understand. That code checks if the pci_device_id
pointer passed to the probe function points to a spot in the driver's pci
id table. It has nothing to do with the driver_data field being modified.
what's the harm in it ?
If the pci layer ever changes certain internal implementation details it
will stop working. AFAIK, there is no guarantee that the pci_device_id
must point to in the driver's table. Only that is points to the correct id
for the pci_device that was passed and that the driver_data is correct.
It's poor programming to assume otherwise. It's obviously better to just
check if driver_data is NULL. That makes no unnecessary assumptions about
internal details and is simpler to boot.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
