Ralph Metzler wrote:
>
> > The docs are wrong: they say the driver defaults to 7 if you don't
> > specify a stream type. A few other problems I found in the readme file:
>
> Nope, the README says the default is VT_KFIR_PROGRAM which is 3.
Sorry, I meant 3. My point is, my board didn't start outputting working
streams until I specifically gave the streamtype parameter. I re-tried
this test, and it seems to give working streams _without_ specifying the
stream type. Now I'm at a loss as to why it failed originally.
> > o "vidrate" isn't adequately explained: it isn't clear whether it's an
> > enum (e.g. 1 = 1 Mbit/s, 2 = 1.5 Mbit/s, 3 = 2 Mbit/s, etc.) or an
> > actual bit rate value, and if the latter, in what units.
>
> Sorry, it's in bits/s.
I know; I mentioned it so the docs would be clarifed for the next driver
release.
> > o "loaded" is also not explained well: Kyler made the same mistaken
> > assumption I did, that "loaded" as a parameter means "don't load the
> > microcode". I had to read the source to find that you need to say
> > "loaded=1".
>
> No, "loaded=1" means that the microcode is already loaded and should
> not be loaded again, just as you assumed.
Again, I know; the docs need to make this clear.
I just discovered another oddity. When you load the driver the first
time after booting the system, you the driver will lock the system up if
you give it any parameters aside from "debug=1". (The system locks
right after the "kfir: Reset Kfir and PLL ..." message.) I verified
this multiple times with the following modprobe command:
# /sbin/modprobe kfir vidinmode=1 vidoutmode=0 vidsize=0x26
vidrate=4000000 vidinput=1 mpeg1mode=0
The defaults are okay for people in areas where PAL is used, but those
of us in the US always have to change the parameters from their
defaults. (I didn't check to find out which of the above parameters
causes the crash.)
This needs to be fixed or mentioned in the docs. Also, my script will
probably also crash the system, since its hard-coded defaults are for
the NTSC system. I probably need to add a command line option (-i for
"initial"?) that loads kfir.o with default options. You could put the
following sequence in your system's rc file:
kfir -i
kfir
This would load the driver with default options, then reload it with the
options in ~/.kfirrc.
--
= Warren -- Video articles: http://www.cyberport.com/~tangent/video/
=
= ICBM Address: 36.8274040 N, 108.0204086 W, alt. 1714m
