RE: [ivtv-devel] #0.3.6p recent patches, digitizer reset improvements
#0.3.6p: http://www.ivtv.tv/releases/ivtv-0.3/ Glad to see the .id stuff is fixed. Not really sure what the point of all the (unsigned)sizeof(I2C_NAME(client)) are though (also all the snprintfs are reserving an extra byte at the end that they don't need to). Can at least the .id changes be pushed out into a new 0.2.0? -- Anduin Withers --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
RE: [ivtv-devel] #0.3.6n
This has all the recent patches plus fixes to encoder buffering, I hope, trying to make that more stable, added more buffers when statically allocated or to keep around by startup default, also bigger buffers if statically allocated on module load to ease encoder DMA and reading from the buffers. So... do I need to redo the i2c_client.id patch? (I think a new 0.2.0 should actually be made, thus the patch against 0.2.0) -- Anduin Withers --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
[ivtv-devel] [patch] i2c_client.id is dead, long live i2c_client.id.
The i2c_client id field has been removed recently. Like most other drivers that had it removed I punted on replacing it with bus id/address. -- Anduin Withers i2cnoid.patch Description: Binary data
RE: [ivtv-devel] PVR250 - no sound - ready to ditch this card
Here's the compilation error: cx25840-driver.c:258:1: warning: i2c_master_send That module shouldn't be used in your configuration anyway. Are you capturing from the F-type connector or from S-Video? When you modinfo msp3400 are you sure the filename: is pointing to the right file? While a bad card is possible, at a minimum I'd try both input sources before considering that possibility. -- Anduin Withers --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
RE: [ivtv-devel] #0.3.2f recent patches merged
Oh, I'd take any patches that apply cleanly I guess. Attached. Really three small patches: 1. Make newer kernel msp3400 drivers just work (no more ivtv msp3400) 2. Increase the mpeg buffer size (the current default is too small) 3. Patch chann.c so you can pass in the device (and switch it to use NTSC cable frequencies by default) -- Anduin Withers mspchannmpegbuf.patch Description: Binary data
[patch] RE: [ivtv-devel] #0.2.0-rc3g and #0.3.2e fixes
These add most of the recent patches, if not then please resubmit patches to these versions, either they didn't apply clean or fell through the cracks... Patch attached. 1 - Makes it work with the kernel msp3400 when available. 2 - Fixes chann.c to allow the device to be passed in (and change the default from NTSC broadcast to NTSC cable). 3 - Up the size of the mpeg stream buffer. -- Anduin Withers kernmspchann.patch Description: Binary data
RE: [ivtv-devel] virtual consoles on TV-out
However, the text is black on a black background so all I see is the cursor - I've seen this reported before, but not the solution if there is one. Does anyone know how to change the character color to white so text appears? I didn't think this was still a problem (I'm guessing it is only on 2.4 these days). I don't actually have my 350 in use at the moment but a long time ago I did bother to track this one down. The color map is still used in 32bpp mode to get the foreground/background colors for font display. Sadly while my memory survives the code doesn't (it was trivial). Hope this is enough for someone else to fix it. -- Anduin Withers --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] [patch] better kernel msp3400 support, chann with -d, larger mpg buffer
Have you included some fixes to improve handling of multiple PVR's? I found that with on my system with 2 PVRs i could not use the kernel msp34xx and still have dependable sound. At irregular times sound would be absent. Using the ivtv msp version it works flawless. Not that it will help you much, but I've been using the kernel msp3400 for 23 days now (the machine I'm testing it on has three pvr-250's) and I haven't had a single sound problem (using the patch at the top of this thread). When was the last time you tried the kernel driver? I was responsible for several of the changes to the ivtv version of the driver, currently I'm happy with how Gerd Knorr has integrated them (those that made the other changes have yet to report). -- Anduin Withers __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] Problem loading ivtv with the old initrd trick
So I naively thought this would work without a hitch. What I don't get is how the modules are loaded into the ram disk if the file system isn't mounted. Hmm, perhaps some sort of image was made when I ran mkinitrd. I can't believe I'm the only person who did this. The person who wrote that guide was nice enough to post including a reference to a bug with further directions, those directions tell you to put the firmware on the initial ram disk (and how). Initial RAM disks are there so kernels can be built with many key drivers built as modules. The mkinitrd script uses your system information and supplied parameters to build an image with those key drivers. While you certainly aren't the only one going down that road I'd still term it an uncommon setup. I think I have bigger problems, though. I get nothing from the TV out when I try to start X. This is when you load the driver normally? Or still w/o the firmware? -- Anduin Withers __ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Re: [ivtv-devel] Problem loading ivtv with the old initrd trick
I find this most odd. Is it possible the file system isn't mounted? That makes no sense. It's able to load the ivtv module. The module does end up loaded, but non-functional. I can remove it and reload it and it seems fine, then. initrd = Initial RAM Disk Yes, your fs isn't there in that case. Luckily that probably has nothing to do with your actual problem (as ivtv isn't loading there anyway unless you have gone far out of your way). Did you build the driver yourself? (If not where did you get it from?) What version is it? I don't use packaged versions but if you're using one they may have turned on HP_FWLOAD, in which case the driver would expect /lib/firmware/ivtv-fw-enc.bin (on FC3). -- Anduin Withers __ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250 --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ ivtv-devel mailing list ivtv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ivtv-devel
RE: [ivtv-devel] Driver version is 0.2.0-rc3d, IVTV_DRIVER_VERSION_COMMENT is ??
After upgrading from rc3b to rc3c to rc3d I noticed that the IVTV internal version does not seem to be changing. Is this an oversight or am I missing something? Oversight. -- Anduin Withers --- 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:[patch] [ivtv-devel] question about msp3400.ko versions
If the kernel version works, yes. For me, at the moment , it does not. I can record all right, but at undefined moments i lose sound. i will initially record with sound, and after some recordings i lose sound. re-tuning to the tuned frequency will enable sound again. That problem used to happened with the ivtv msp3400 as well. The causes were: stereo detection failing (generally worked around by passing once=1 as a module param) and the msp ACB wasn't reset after an msp reset (some chips persist ACB others reinitialize it). Judging from what changes are present in the 2.6.10 msp3400 it looks like Gerd Knorr is receptive to fixes. I'm willing to risk a few recordings without sound in an attempt to track it down if it is a problem. I'm attaching a patch which does two things: 1) init video_audio before we call msp3400 2) unmute the audio on driver load 0) fix the driver version Another change not in the kernel msp3400 driver was the msp3400c_setvolume patch (it should be vol * 0x7F not vol * 0x73 at least according to what I've seen). This patch when using the ivtv msp3400 version should do nothing, with the kernel ivtv recordings will be quieter. -- Anduin Withers kernmspfixes.patch Description: Binary data
RE: [ivtv-devel] question about msp3400.ko versions
Ah, ok, so it might be that opmode=1 works report doesn't apply to all ivtv-supported cards, right? I don't know, I have three different types of cards, it seems to work on them. Then again simple always worked for me in the past. I was really hoping Chris or someone would chime in. The i2c helpers modules must not clear the structs. That would kill any data filled by the v4l driver in step (b). Thats why some drivers clear the structs and some don't. And at least bttv must do (a) and (b) itself. Moving (a)+(b) into the msp3400 module isn't an option as not all bt878 cards have a msp3400 chip. I hope the issues here are a bit more clear now ... Ok, that actually makes sense (when viewing through the somewhat narrow requirements of ivtv it seemed a bit cumbersome). I'm pretty sure everyone would love to see the ivtv msp3400 variant die. -- Anduin Withers --- 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
