I think my original cx25840 module actually did scaling like this, using both registers, at least from what I remember. So that code may be of use, at least I first did it and it cropped like it does in the current module, then had to set another 2 registers to make it scale instead. So maybe I'm mistaken, not sure, but that should have been correct originally.
I'm confused still about the way the cx25840 driver is currently written, where it is very hard to go by register spec sheets and know what/how to change, debug values, since everything has a label which doesn't point to the real register name by hex at all. I've really wanted to dig in more but kinda got thown a loop there in development for it to be so far from the way the other digitizer module is written and has alot of extra layers over the raw registers being manipulated, and something about dynamic generated code which we have no tool to do that with at our disposal. Just some of my observations on the module, plus how it no longer works on the OEM cards tuner and did at first without much regiser poking at all, like there's a bit too much overkill in i2c poking, and I do get lockups randomly on load from the heavy i2c traffic it makes now (think it's trying to do as much as the windows drivers, which always do too much default resetting registers to values they are anyways, I tried to avoid that in my reverse engineering). So this is something that someone could cleanup, make it more accessible, or document what all the complicated coding around setup of stuff is, would help make it easier to push development forward (I don't have time to cross ref all the labels to register values, which is what it seems to take to really dig into trying new things for the module now). I'm just not seeing how worth it things are to get the OEM cards working, which is all I have, when it seems like just a simple tuner issue but so much code now to wade through just to get some video to show up as a first step (and trust me, I've went exactly every path possible of how to do things, type 47 for NTSC, new tuner.ko etc...). Thanks, Chris On Thu, Mar 17, 2005 at 12:45:43PM -0500, Sergey Alexandrov wrote: > On Thu, 2005-03-17 at 12:33 -0500, Tyler Trafford wrote: > > > Sergey Alexandrov <[EMAIL PROTECTED]> wrote: > > > Looks like to make scaling work it's necessary to setup HACTIVE and > > > VACTIVE > > > to new width/height. I've tried to set it up, but HACTIVE resets to > > > 720 when I've tried to > > > capture something .. Have no idea where it got defaulted from :( > > > > I'm pretty sure that VACTIVE and HACTIVE (and VBLANK and HBLANK) are > > used primarily to set the region the encoder looks at. (it is possible > > to scale using them, but only in a way that maintains the WxH ratio). > > > I meant to scale image properly, you have to setup HSCALE, VSACLE AND!!! > HACTIVE, VACTIVE. > In case of simple scaling it's not ness. to change BLANK values. Take a > look on older conexant's > driver code, they ALWAYS define HACTIVE and VACTIVE in scaling > procedures. We don't. As I can see > in 3.2 and earlier, there is only (H/V)SCALE setup, but not (H/V)ACTIVE. > Look, if we setup scaler to, > for example, 480x480, HACTIVE should be 480, in 3.2 case it's still 720, > so we have "crop" instead > of scale ... > > > Thanks, Serg -- --- Chris Kennedy / [EMAIL PROTECTED] Engineer KMOS-TV/KTBG-FM Broadcasting Services Department Central Missouri State University ------------------------------------------------------- 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=6595&alloc_id=14396&op=click _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
