I have to agree. This could end up being a real a problem...for me or
anyone else. The syslog will group some log messages if they are similar
enough, but since I had the messages coming on the 8 tuners, it was rare to
get consecutive messages for the same tuner, and hence, no grouping of
RFC MPEG encoding and decoding V4L2/DVB API additions
Version 0.2
(The latest version of this RFC can be found here as well:
http://ivtvdriver.org/viewcvs/ivtv/trunk/doc/)
This RFC adds new functionality to the V4L2/DVB API in order to properly
support MPEG hardware encoders and decoders. This
Em Dom, 2007-02-18 às 14:03 +0100, Hans Verkuil escreveu:
RFC MPEG encoding and decoding V4L2/DVB API additions
Version 0.2
(The latest version of this RFC can be found here as well:
http://ivtvdriver.org/viewcvs/ivtv/trunk/doc/)
This RFC adds new functionality to the V4L2/DVB API in
RFC MPEG encoding and decoding V4L2/DVB API additions
Version 0.3
(This third revision incorporates the comments and suggestions that
resulted from discussing this RFC with Ralph Metzler. This should be
pretty much the final version. I hope.)
This RFC adds new functionality to the V4L2/DVB API
6) Scaling and positioning of the video
The cx23415 can take the MPEG stream and scale it to an arbitrary width
and height and position it at anywhere in the TV-out screen. So you can
get effects like having the MPEG output to the top left corner and an
OSD in the lower right corner.
On Sunday 18 February 2007 17:54, Mauro Carvalho Chehab wrote:
6) Scaling and positioning of the video
The cx23415 can take the MPEG stream and scale it to an arbitrary
width and height and position it at anywhere in the TV-out screen.
So you can get effects like having the MPEG output
Hi all,
First the good news: we've received official permission to redistribute
the firmwares from Hauppauge. Thank you, Hauppauge!
Now the bad news: I've updated all the firmware archives on
ivtvdriver.org by adding the new license files. This means that they
all changed size and I promptly
Hi all,
As you may have noticed there has been a lot of activity lately. It
looks like there is a good chance that ivtv can go in the 2.6.21
kernel. If some last API changes are accepted, then there is nothing
that stands in the way.
So I've branched off the ivtv-0.10 series in subversion.
On Sun, Feb 18, 2007 at 09:03:31PM +0100, Hans Verkuil wrote:
Now the bad news: I've updated all the firmware archives on
ivtvdriver.org by adding the new license files. This means that they
all changed size and I promptly got a report that gentoo didn't like
that one bit!
I'm not sure
RFC V4L2 additions required for full cx23415 OSD and YUV support
Version 0.1
(Really, it's the last RFC. I promise. :-)
The Conexant cx23415 MPEG encoder/decoder features an On-Screen Display
framebuffer. It is able to overlay the image of the framebuffer on top
of the MPEG or YUV decoder
Hans Verkuil writes:
Hi all,
First the good news: we've received official permission to redistribute
the firmwares from Hauppauge. Thank you, Hauppauge!
Thank _you_ for making that happen.
Hopefully this is just the first of the many good news to come; and the spec
sheets for the new
Hans Verkuil wrote:
Hi all,
As you may have noticed there has been a lot of activity lately. It
looks like there is a good chance that ivtv can go in the 2.6.21
kernel. If some last API changes are accepted, then there is nothing
that stands in the way.
So I've branched off the
Thank you for all the help.
After playing around with the tuning so more I found I need to use the
cable HRC frequencies.
There was nothing wrong with the driver or the install.
So for anyone else out there. I hope this helps them.
Thanks Again,
Drew
On 2/12/07, Hans Verkuil [EMAIL PROTECTED]
13 matches
Mail list logo
