RE: [ivtv-devel] New Q&A round with Hauppauge? (was: Hauppauge specific questions)
Hi, One of the things I have noticed is the number of Tuners that are on the boards and they keep changing and not all are supported.. How about better Tuner support or documents or patches etc? The reason I say that is I have a PVR-500 that is all but running but the reception is very average because I have Philips FQ1216AME MK4 Tuners (Tuner 91) that don't seem to be supported that well yet. I have looked at patches and all over the net and don't seem to be able to find much out about them. Any help appreciated of course :-) Cheers Grant -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Axel Thimm Sent: Tuesday, 18 January 2005 3:00 p.m. To: ivtv-devel@lists.sourceforge.net Subject: [ivtv-devel] New Q&A round with Hauppauge? (was: Hauppauge specific questions) I suggest to collect questions on current ivtv issues that Hauppauge engineering and development can help solving. Hauppauge is open to the Linux community, nevertheless the process to acquire and clear out information is slow. It pays off to do so for a set of questions IMHO, at least that was the experience with the former Q&A (not QA ;) sessions. Can you formulate your questions appropriately (assume full knowledge on any hardware detail, but little on ivtv and Linux kernel drivers)? You can send them as reply to this post or off-list and I will create a summary. Thanks! On Wed, Jan 05, 2005 at 10:03:17PM -, John Harvey wrote: > Axel > The question I have I think was asked by Hans but I never saw an > answer. I have been trying to get UYV playback to work. If you > initiate a YUV dma request and then query the status it says that it > need 622080 bytes (for PAL) which is correct but it says that the > address to transfer to is 0 and that the dma type is 0(mpeg). > If it transfer a small amount say 4 bytes then query the status on > the interrupt for dma completing it says it need 622076 bytes to an > address 0f 4 and type 0. > > I don't believe we should be transferring to address 0 so we > presumably need to add some offset to this (just like the osd has to > add the osd base address) but there doesn't appear to be an api to find the offset. > > Can Hauppauge help us to understand how to use the YUV dma transfer? > > Alternatively there are 9 yuv buffers pointed to from the 9 words at > 0x0100140. If I modify the driver to continue to display the last > frame it is displaying the yuv from one of these buffers and if I > write yuv (in Hauppauge style yuv) to the correct buffer it is displayed on the output. > However I cant determine which of the 9 buffers is the correct one to > write to or to control which one to use. If we cant make the api work > then possibly we might be able to find a way to control which of these > buffers is used and then we could control this ourselves. > > Do you think Hauppauge will be able to help us with this? > > Thanks > > John > > > From: [EMAIL PROTECTED] [mailto:ivtv-devel- > > [EMAIL PROTECTED] On Behalf Of Axel Thimm > > Sent: 28 August 2004 22:39 > > To: ivtv-devel@lists.sourceforge.net > > Subject: [ivtv-devel] Re: Hauppauge specific questions (was: > > Hauppauge's commitment to Linux support) > > > > Hans Verkuil wrote: > > > Axel Thimm wrote: > > > > If you need information from Hauppauge or one of its suppliers, > > > > e.g. for the ivtv project, Conexant, there are two cases: > > > > > > > > o if the information is under Hauppauge's authority, it can and will > > > > be disclosed. > > > > o if the information is under Conexant's authority, Hauppauge will try > > > > to mediate, so you don't get stuck with a sales person at Conexant > > > > again. > > > > > OK, here is the first set of questions. These questions are all > > Hauppauge > > > specific (except perhaps for the last question). I'll post a > > > separate > > list > > > with Conexant questions. The autodetect questions have the highest > > priority. > > > > Here are the answers to Hans' questions, the refined questions based > > on these answers, the refined answers based on these refined > > questions and so on ;) > > > > Some of the tuner documentation has already been used in current > > ivtv snapshots, hopefully more will follow. > > > > Thanks for your patience! > > > > The SF.Net email is sponsored by: Beat the post-holiday blues Get a > FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt > ___ > ivtv-devel mailing list > ivtv-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ivtv-devel -- Axel.Thimm at ATrpms.net --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___
Re: [ivtv-devel] problem with IVTV drivers
that looks fine, are you in the US? your card is NTSC what exactly is not working? you may want to disable 4kstacks in your kernel also (requires kernel recompile).. though i haven't heard of it causing problems with pvr250's, just 150s -tmk --- [EMAIL PROTECTED] wrote: > Here is my debug information, can you help? I have > been trying to get > this Mythtv box running for a few days. Thanks in > advance!!! > > vtv: START INIT IVTV > > ivtv: version 0.1.10 > (0.1.10-48.4_pre2_ck100zz.rhfc2.at) loading > ivtv: Linux version: 2.6.10-1.9_FC2 686 REGPARM > 4KSTACKS gcc-3.3 > ivtv: In case of problems please include the debug > info > ivtv: between the START INIT IVTV and END INIT IVTV > lines when > ivtv: mailing the ivtv-devel mailinglist. > ivtv: Autodetected WinTV PVR 250 card > ivtv: Found an iTVC16 based chip > ACPI: PCI interrupt :01:08.0[A] -> GSI 5 (level, > low) -> IRQ 5 > ivtv: pci: PCIBUS detected device: 0x2560 vendor: > 0x8086 > tveeprom: Hauppauge: model = 32032, rev = B182, > serial# = 2832305 > tveeprom: tuner = LG NTSC (newer TAPC series) (idx = > 82, type = 39) > tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = > 0x1000) > tveeprom: audio_processor = MSP3440 (type = 11) > ivtv: i2c attach [client=tveeprom[1],ok] > tuner: chip found at addr 0xc2 i2c-bus ivtv i2c > driver #0 > ivtv: i2c attach [client=(tuner unset),ok] > saa7115: starting probe for adapter ivtv i2c driver > #0 (0x10005) > saa7115: detecting saa7115 client on address 0x42 > saa7115: writing init values > ivtv: i2c attach [client=saa7115[1],ok] > saa7115: status: (1E) 0x89, (1F) 0xb1 > msp34xx: init: chip=MSP3448W-B3 +nicam +simple > +simpler +radio > mode=simple > ivtv: i2c attach [client=MSP3448W-B3,ok] > msp3410: daemon started > ivtv: Tuner Type 39, Tuner formats 0x1000, > Radio: yes, Model > 0x00891612, Revision 0x > ivtv: NTSC tuner detected > ivtv: Radio detected > ivtv: Encoder revision: 0x02040024 > ivtv: Configuring WinTV PVR 250 card with 5 streams > ivtv: Create DMA stream 0 using 128 buffers of size > 32768 > ivtv: Create DMA stream 1 using 128 buffers of size > 32768 > ivtv: Create stream 2 using 128 buffers of size > 52224 > ivtv: Create DMA stream 3 using 128 buffers of size > 32768 > ivtv: Create stream 4 > ivtv: Setting Tuner 39 > tuner: type set to 39 (LG NTSC (newer TAPC series)) > by ivtv i2c driver > #0 > ivtv: Setting audio matrix to input 3, output 1 > ivtv: Switching standard to NTSC. > saa7115: decoder set norm NTSC > saa7115: set audio: 0x01 > ivtv: Initialized WinTV PVR 250, card #0 > ivtv: END INIT IVTV > > -- > > [EMAIL PROTECTED] > > > > --- > The SF.Net email is sponsored by: Beat the > post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt > from ThinkGeek. > It's fun and FREE -- well, > almosthttp://www.thinkgeek.com/sfshirt > ___ > ivtv-devel mailing list > ivtv-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ivtv-devel > --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] X working on PVR-350 but MPEG decoder doesn't
It seems I can get rid of the ENC IRQ OVERFLOW message by raising the pci latency timer but it didn't improve the poor framerate :-( Nicolas --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] problem with IVTV drivers
On Tuesday 18 January 2005 07:48, kevin thayer wrote: > you may want to disable 4kstacks in your kernel also > (requires kernel recompile).. though i haven't heard > of it causing problems with pvr250's, just 150s Yeah, 4kstacks are just fine with my PVR-250, 350, AVerMedia M179 or Yuan MPG600GR. But very nasty hard-locks with my PVR-150 and PVR-500. -- Jarod C. Wilson, RHCE [EMAIL PROTECTED] pgpoBiCLxTEQj.pgp Description: PGP signature
Re: [ivtv-devel] PVR-150MCE PAL - Mono audio
Are you sure you've got mono audio? I'v got the same tuner (LG is a part of philips) and it does do stereo. Maybe you're looking at your dmesg during load of cx25840 module.>>> I think it's normal for the driver to detect mono audio when the tuner is not yet tuned into a channel :) also audio_mode wil not be detected Check dmesg when you're once tuned into a working channel. You should see some responce from the cx driver saying "stereo" (detected audio mode) - Original Message - From: "Jaap Braam" <[EMAIL PROTECTED]> To: Sent: Tuesday, January 18, 2005 2:00 AM Subject: Re: [ivtv-devel] PVR-150MCE PAL - Mono audio Update: It turns out that I use the tuner.ko from the 2.6.10 kernel. (didn't rename the kernel provided tuner.ko) In tuner.c this tuner is called 'Philips PAL/SECAM_D (FM 1256 I-H3)' but the label on my card sais 'TAPE-S001D' (as does tveeprom) I'm confused: the LG tuner seems to work quite well with the Philips tuner type... Can the lack of stereo sound have anything to do with this??? Jaap Braam wrote: Hi All, I've finally managed to get my PRV-150MCE PAL working under Fedora Core 3. It's working, but I only get mono audio when recording television programs... Does someone know what can be done to fix this Jaap. BTW: I'm using ivtv-0.3.2b... --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.13 - Release Date: 16-1-2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.13 - Release Date: 16-1-2005 --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] no sound in recordings with rc2z (Axel) versus ck100zz
On Thu, 2004-12-09 at 10:54 -0600, Aran Cox wrote: > I upgraded to rc2z on the 6th and haven't gotten sound in a recording > since. What follows is the initialization from rc2z and ck100zz. I am > using all RPM's from Axel's repo, including the firmware. The only > thing I noticed about the following is that ivtv thinks the firmware is > buggy. Is there some disagreement on this matter, perhaps? > > In any case, I guess I'll try ck100zz for a while. Or maybe I'll try > and compile rc3* something later... So, after dealing with my ck100zz problems for a while I thought I'd try a newer release (rc3b.) I still get no audio in the recordings. Revert to ck100zz and sound returns. Since my previous posting I upgraded to kernel-2.6.10-1.737_FC3 and used the Axel packages for ivtv (both rc3b and ck100zz.) Otherwise the system hasn't changed from below. I tried looking for threads regarding audio problems but nothing quite matches my situation, that I noticed anyway. I'll attach my two ivtv init sequences, one for rc3b and one for ck100zz if that's helpful to anyone. The reason I need want to get away from ck100zz is that I get the ivtv: needed 1 bufs for stream 0, received 0 differ by (1) bufs message and subsequently have to restart mythbackend. Any suggestions appreciated... thanks. > FC3 > Epox 8RDA+ (nforce2) > Athlon 1400 (not XP) > 2xPVR-250 > kernel-2.6.9-1.667 > > broken: > ivtv-0.2.0-56_rc2z.rhfc3.at.i386.rpm > ivtv-firmware-1.8a-4.at.i386.rpm > ivtv-firmware-dec-2.02.023-4.at.i386.rpm > ivtv-firmware-enc-2.04.024-4.at.i386.rpm > kernel-module-ivtv-2.6.9-1.667-0.2.0-56_rc2z.rhfc3.at.i686.rpm > > > functional: > ivtv-0.1.10-48.4_pre2_ck100zz.rhfc3.at > ivtv-firmware-1.8a-4.at > ivtv-firmware-dec-2.02.023-4.at > ivtv-firmware-enc-2.04.024-4.at > kernel-module-ivtv-2.6.9-1.667-0.1.10-48.4_pre2_ck100zz.rhfc3.at > > > -- Aran Cox <[EMAIL PROTECTED]> Jan 17 21:47:32 cain kernel: ivtv: START INIT IVTV Jan 17 21:47:32 cain kernel: ivtv: version 0.1.10 (0.1.10-48.4_pre2_ck100zz.rhfc3.at) loading Jan 17 21:47:32 cain kernel: ivtv: Linux version: 2.6.10-1.737_FC3 686 REGPARM 4KSTACKS gcc-3.4 Jan 17 21:47:32 cain kernel: ivtv: In case of problems please include the debug info Jan 17 21:47:32 cain kernel: ivtv: between the START INIT IVTV and END INIT IVTV lines when Jan 17 21:47:32 cain kernel: ivtv: mailing the ivtv-devel mailinglist. Jan 17 21:47:32 cain kernel: ivtv: Autodetected WinTV PVR 250 card Jan 17 21:47:32 cain kernel: ivtv: Found an iTVC15 based chip Jan 17 21:47:32 cain kernel: ivtv: Unreasonably low latency timer, setting to 64 (was 32) Jan 17 21:47:32 cain kernel: ivtv: pci: PCIBUS detected device: 0x01e0 vendor: 0x10de Jan 17 21:47:32 cain kernel: tveeprom: Hauppauge: model = 48432, rev = I110, serial# = 6142020 Jan 17 21:47:32 cain kernel: tveeprom: tuner = Philips FI1236 MK2 (idx = 10, type = 2) Jan 17 21:47:32 cain kernel: tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x1000) Jan 17 21:47:32 cain kernel: tveeprom: audio_processor = MSP3440 (type = 11) Jan 17 21:47:32 cain kernel: ivtv: i2c attach [client=tveeprom[0],ok] Jan 17 21:47:32 cain kernel: ivtv: Tuner Type 2, Tuner formats 0x1000, Radio: yes, Model 0x00a51450, Revision 0x Jan 17 21:47:32 cain kernel: ivtv: NTSC tuner detected Jan 17 21:47:32 cain kernel: ivtv: Radio detected Jan 17 21:47:32 cain kernel: tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 Jan 17 21:47:32 cain kernel: ivtv: i2c attach [client=(tuner unset),ok] Jan 17 21:47:32 cain kernel: saa7115: Ignoring new-style parameters in presence of obsolete ones Jan 17 21:47:32 cain kernel: saa7115: starting probe for adapter SMBus nForce2 adapter at 5000 (0x0) Jan 17 21:47:33 cain kernel: saa7115: starting probe for adapter SMBus nForce2 adapter at 5100 (0x0) Jan 17 21:47:33 cain kernel: saa7115: starting probe for adapter ISA main adapter (0x0) Jan 17 21:47:33 cain kernel: saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005) Jan 17 21:47:33 cain kernel: saa7115: detecting saa7115 client on address 0x42 Jan 17 21:47:33 cain kernel: saa7115: writing init values Jan 17 21:47:33 cain kernel: ivtv: i2c attach [client=saa7115[0],ok] Jan 17 21:47:33 cain kernel: saa7115: status: (1E) 0x09, (1F) 0xc0 Jan 17 21:47:33 cain kernel: msp34xx: init: chip=MSP3448W-A2 +nicam +simple +simpler +radio mode=simple Jan 17 21:47:33 cain kernel: ivtv: i2c attach [client=MSP3448W-A2,ok] Jan 17 21:47:33 cain kernel: msp3410: daemon started Jan 17 21:47:34 cain kernel: ivtv: Encoder revision: 0x02040024 Jan 17 21:47:34 cain kernel: ivtv: Decoder revision: 0x02020023 Jan 17 21:47:34 cain kernel: ivtv: Configuring WinTV PVR 250 card with 5 streams Jan 17 21:47:34 cain kernel: ivtv: Create DMA stream 0 using 128 buffers of size 32768 Jan 17 21:47:34 cain kernel: ivtv: Create DMA stream 1 using 128 buffers of size 32768 Jan 17 21:47:34 cain kernel: ivtv: Create stream 2 using 128
RE: [ivtv-devel] X working on PVR-350 but MPEG decoder doesn't
No real idea but if you want to try turning on all debugging and sendming a short segment from the messages file it may highlight something. Probably best to send it direct to me or make it available on a web site. John > -Original Message- > From: [EMAIL PROTECTED] [mailto:ivtv-devel- > [EMAIL PROTECTED] On Behalf Of Nicolas Mainil > Sent: 18 January 2005 17:04 > To: ivtv-devel@lists.sourceforge.net > Subject: Re: [ivtv-devel] X working on PVR-350 but MPEG decoder doesn't > > It seems I can get rid of the ENC IRQ OVERFLOW message by raising the > pci latency timer but it didn't improve the poor framerate :-( > > Nicolas > > > --- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt > ___ > ivtv-devel mailing list > ivtv-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ivtv-devel --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] New Q&A round with Hauppauge? (was: Hauppauge specific questions)
I seem to be in the same spot with my PVR-500. The tuners appear to be labeld FQ1236A/R and I haven't found a single combination of tuner/ivtv modules that will give me a usable picture. I, once, was able to get what appeared to be a signal with tuner type 43, but that was only on the first tuner and it stopped working when I tried to change the channel. Any help is greatly appreciated. * Grant <[EMAIL PROTECTED]> [2005-01-18 04:24:41]: > Hi, > > One of the things I have noticed is the number of Tuners that are on the > boards and they keep changing and not all are supported.. > > How about better Tuner support or documents or patches etc? > > The reason I say that is I have a PVR-500 that is all but running but the > reception is very average because I have Philips FQ1216AME MK4 Tuners (Tuner > 91) that don't seem to be supported that well yet. I have looked at patches > and all over the net and don't seem to be able to find much out about them. > Any help appreciated of course :-) > > Cheers > Grant pgpCsk8D3aQ9f.pgp Description: PGP signature
Re: [ivtv-devel] problem with IVTV drivers
On Tue, 18 Jan 2005, Jarod Wilson wrote: > Yeah, 4kstacks are just fine with my PVR-250, 350, AVerMedia M179 or Yuan > MPG600GR. But very nasty hard-locks with my PVR-150 and PVR-500. I've also seen advice about disabling smp and preemption for the pvr-150 (which includes the 500). A bit OT, perhaps, but here's a 'light' overview of 4k stacks: http://lwn.net/Articles/84583/ Best regards Peter K -- We Can Put an End to Word Attachments: http://www.fsf.org/philosophy/no-word-attachments.html --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
RE: [ivtv-devel] X working on PVR-350 but MPEG decoder doesn't
Check hdparm to see if your disks are working in DMA mode. R. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] X working on PVR-350 but MPEG decoder doesn't
Already done and they are. Nicolas Roger James wrote: Check hdparm to see if your disks are working in DMA mode. R. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] X working on PVR-350 but MPEG decoder doesn't
hi, did you try mpg_buffers=30 ? adding it to the line ... options ivtv tuner=38 ivtv_std=3 tda9887=0 mpg_buffers=30 and hdparm tuning ? i use this one : all_args="-d1 -W0" d1 is for enable ultra dma W0 is disable cache of the hard disk i diisable the cache cause i think it's useless... i doesn't acces repeatitively to the same data... the result with the cache is that data transit via the cache it takes time and make hard drive geeting heat for nothing... i ve had ENC IRQ OVERFLOW too but not since i did the changes... maybe it's just coincidence... time will say it to me :) ++ --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
