On Mon, 2005-11-21 at 23:00 +0100, Hans Verkuil wrote:
The first drawback can be countered by the fact that ivtv is still an
unofficial driver with a 0.x version number. People using it should
expect some changes every now and then. (So I hope to get this change
accepted before ivtv is
On Tue, 2005-11-22 at 10:20 +0100, Hans Verkuil wrote:
The second drawback is just an extra motivation for people to update
their kernel, so I wouldn't take it too serious.
If people have no big objections I will implement a patch that does
these changes and post it here.
Sure!
I think that it is possible to add the teletext data stream to the mpeg
output. But I'm wondering just how.
I see from the wiki page http://www.ivtvdriver.org/index.php/Ivtvctl
that the following options are available to the ivtvctl command:
--get-vbi
--set-vbi=
--get-vbi-passthrough
I think that it is possible to add the teletext data stream to the mpeg
output. But I'm wondering just how.
I see from the wiki page http://www.ivtvdriver.org/index.php/Ivtvctl
that the following options are available to the ivtvctl command:
--get-vbi
--set-vbi=
--get-vbi-passthrough
So maybe I should just disable the use of the X driver
and use the fbdriver only?
Current=
Section Device
Identifier Hauppauge PVR 350 iTVC15
Framebuffer
Driver ivtvdev
### change fb1 to whatever your card grabbed
Option fbdev /dev/fb1
Option
It's not a problem as such, it's just the way it
works.
Sollutions are to use window managers that allow you
to choose a smaller virtual desktop.
Or if you are running mythtv then you can set it's
overscan settings to work round this.
We are however working on implementing something that
will
