Your description of the behaviour is correct assuming you are a PAL user. It writes to the top 480 lines which is the complete screen for NTSC but theres still another 100 below that for PAL. So actually I think this is ok. I believe 0.2 rc candidates all work for 64bit ok as does the x driver. So I don't think there is anything completely broken other than the fact that you suffer hangs with encode/decode working together and if that's the case there are likely to be problems with decode/frame buffer.
So I believe that as long as you are using the 0.6 version of the ivtvdev x driver you should be able to get X running. John > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:ivtv-devel- > [EMAIL PROTECTED] On Behalf Of Rutger Hendriks > Sent: 03 December 2004 16:32 > To: [EMAIL PROTECTED] > Subject: Re: [ivtv-devel] #0.2.0-rcv dma sync patch > > On Thursday 02 December 2004 21:34, John Harvey wrote: > > Nothing that I know of that would cause this. > > The x driver hasn't changed for ages. > > > > Try > > > > ivtvfbctl /dev/fb/1 -prepdma > > > > This should display an image that gradually gets darker on the frame > buffer > > and should prove whether ivtv-fb is working. > > > > > > John > > Okay, bugreport again :) > > I loaded ivtv, that gave quite some memory allocation errors (box was up > for > coule of hours) and trying to load ivtv-fb then failed (it was only then > that > I saw the memory allocation failures, so no wonder it failed:P) > unloading all ivtv modules and modprobe ivtv-fb gave a hard crash > > so I rebooted and loaded ivtv, that worked okay, then loaded ivtv-fb, no > problems there. > Then I tried your > ivtvfbctl /dev/fb/1 -prepdma > and ran downstairs :) > the tv showed 2 things: > - the upper 80% of the screen gradually changed color from dark to white a > couple of times (this is oposite of what you describe it should do?!) and > after a while it stopped and just showed a white screen (important:P) > > - the remaining 20% (at the bottom of the screen) showed... > well...something > like noise, but it wasn't moving, it where horizontal white lines > alternating > with black lines, they were not moving and not completely homogeneously > filled (I hope you're still with me after this great explanation :P) > > I ran back upstairs and tried to fbgrab it, but then what I see is a black > screen with noise under it (and not a white screen with noise under it as > it > shows on the tv!) > > Isn't that interesting! I know nothing of the inner workings, but it > seemed to > me there is at least one and maybe multiple offsets > > Remember, this is on 64-bit. > > the dd if=/dev/video0 of=/dev/video16 I did yesterday worked okay then > (for a > couple of hours then it hang the machine), I mean it gave a good picture, > no > shifts, so it seems ivtv doesn't have this problem > > I hope you understood, if you need any more info or want me to test stuff, > please gimme a yell > > Thanks, > > Rutger > > > ------------------------------------------------------- > 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://productguide.itmanagersjournal.com/ > _______________________________________________ > ivtv-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/ivtv-devel ------------------------------------------------------- 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://productguide.itmanagersjournal.com/ _______________________________________________ ivtv-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
