Date: Thu, 15 Feb 2007 02:37:09 +0100 From: Danny Pansters <danny@ricin.com> To: freebsd-multimedia@freebsd.org Cc: freebsd-multimedia@freebsd.org Subject: Re: multimedia/kbtv question Message-ID: <200702150237.09561.danny@ricin.com> In-Reply-To: <20070214185708.49151f5c@vixen42> References: <20070213201515.224e0fa7@vixen42> <200702150049.43245.danny@ricin.com> <20070214185708.49151f5c@vixen42>
next in thread | previous in thread | raw e-mail | index | archive | help
Resent to multimedia@ from private mail, because it may be good to have this info in the archives (hope you don't mind vvelox) ... On Thursday 15 February 2007 01:57, you wrote: > On Thu, 15 Feb 2007 00:49:43 +0100 > > Danny Pansters <danny@ricin.com> wrote: > > On Wednesday 14 February 2007 03:15, Vulpes Velox wrote: > > > I came across this and noticed it supports saa7130 and saa7134 > > > cards. > > > > > > I am a bit lost when reading though there. Any one know if the > > > device interfaces are similar to the bktr one? I was just > > > wondering if > > > > Similar but not the same. The saa driver comes from a 3rd party. > > Kbtv uses the kernel module and its ioctl interface. > > > > > mplayer could be used with it. > > > > Not that I know. Perhaps with raw YUV2 input. > > Cool. Thanks for the info. This will provide me a excuse to being > mucking around more with C when I finish up a few perl projects of > mine in the next month. I will have to look at what it will take to > modify the bktr grab code. :) The saa code: http://download.purpe.com/files/saa-REL_14.tgz That's the one I use in kbtv. Everything under kbtv-1.2.3/saa is still mine, everything under kbtv-1.2.3/saa/saa is from Rohit, the saa driver's author. I employ a few patches too. As far as grabbing frames, it's even easier in saa than in bktr, it already pre-allocates (and fills) buffer. See saa.h, the viewer_init() routine or/and the [f]tvv code that comes with the saa driver. > > You also wrote: > > > The saa module attracted my interesting. I was wondering if you > > > would mind me beginning work to break it out seperate from the > > > python and KDE stuff? > > > > Do as you wish. It already is seperate though. You can use the > > saa.h and saa.c as a library and do the same things from a main.c > > as the python module does, see > > http://freebsd.ricin.com/kbtv/pydoc/saa.html > > > > The KDE stuff is only used at GUI level of course. > > Cool. What I will begin work on breaking the kernel modules out into > a seperate port. :) More people have tried/done so in the past. The fltk stuff is/was b0rken within the ports frame it seems. I gave up on it and rather have a fixed code base imported to kbtv which I only change at my own whim. If used from kbtv, it merely installs the kernel module. Also, the saa driver was not 64 bits clean (think I have solved that now, but not sure at runtime). I suggest you use (mostly) my tuning code, not Rohit's (in the support dir). Mine's better. HTH, Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200702150237.09561.danny>