On Tuesday, October 04, 2011 07:31:27 Mauro Carvalho Chehab wrote:
Em 03-10-2011 19:37, Javier Martinez Canillas escreveu:
Hello,
Reading the last emails I understand that still isn't a consensus on
the way this has to be made.
True.
If it has to be implemented at the video
On Tue, Oct 4, 2011 at 7:31 AM, Mauro Carvalho Chehab
mche...@infradead.org wrote:
For now, I propose you to just add/improve the auto-detection on the
existing callbacks. We need to reach a consensus before working at the pad
level.
Ok, I'll do that using saa7115 driver as a reference as
On 09/30/2011 06:52 PM, Mauro Carvalho Chehab wrote:
Em 29-09-2011 11:22, Tomasz Stanislawski escreveu:
This patch adds a documentation for VIDIOC_{G/S}_SELECTION ioctl. Moreover, the
patch adds the description of modeling of composing, cropping and scaling
features in V4L2. Finally, some
Hi Mauro,
if it's not too late for 3.2 could you please pull from
git://linuxtv.org/pb/media_tree.git staging/for_v3.2
for
[media] dib9090: limit the I2C speed
[media] dib8096P: add the reference board
[media] add the support for DiBcom
[media] dib7090: add the reference board
[media]
Em 04-10-2011 04:03, Hans Verkuil escreveu:
On Tuesday, October 04, 2011 07:31:27 Mauro Carvalho Chehab wrote:
Em 03-10-2011 19:37, Javier Martinez Canillas escreveu:
Hello,
Reading the last emails I understand that still isn't a consensus on
the way this has to be made.
True.
If it has
Hi Paul,
On Monday 03 October 2011 07:51:34 Paul Chiha wrote:
Hi,
I've been having trouble getting the resizer to work, and mainly because
I don't know how to correctly configure it.
I'm using kernel 2.6.37 on arm DM37x board.
I've been able to configure the media links
Hi Ivan,
On Tuesday 04 October 2011 13:46:32 Ivan T. Ivanov wrote:
On Tue, 2011-10-04 at 13:03 +0200, Laurent Pinchart wrote:
On Monday 03 October 2011 07:51:34 Paul Chiha wrote:
Hi,
I've been having trouble getting the resizer to work, and mainly
because I don't know how to
I managed to find a series of values that are working correctly for MCLKI:
MCLKI = 0x5554 - i * 0x0c
In my case I can go down to 0x5338 before having TS errors.
From CXD2099 specs
--
It is a requirement for the frequency of MCLKI to be set higher than the input
data rate. ie 8
times
Hi Ivan,
On Tuesday 04 October 2011 13:54:12 Ivan T. Ivanov wrote:
On Tue, 2011-10-04 at 13:50 +0200, Laurent Pinchart wrote:
On Tuesday 04 October 2011 13:46:32 Ivan T. Ivanov wrote:
On Tue, 2011-10-04 at 13:03 +0200, Laurent Pinchart wrote:
On Monday 03 October 2011 07:51:34 Paul
Hello,
Please find below the DVB-T frequencies for the Ramsbottom,
Lancashire, UK transmitter.
#--
# file automatically generated by w_scan
# (http://wirbel.htpc-forum.de/w_scan/index2.html)
#! w_scan 20110702 1 0 OFDM
On Mon, 3 Oct 2011, Laurent Pinchart wrote:
Hi Guennadi,
On Monday 03 October 2011 17:29:23 Guennadi Liakhovetski wrote:
Hi Laurent
Thanks for the reviews!
You're welcome.
On Mon, 3 Oct 2011, Laurent Pinchart wrote:
On Thursday 29 September 2011 18:18:55 Guennadi Liakhovetski
Hi Laurent,
On Tue, 2011-10-04 at 15:00 +0200, Laurent Pinchart wrote:
Hi Ivan,
On Tuesday 04 October 2011 13:54:12 Ivan T. Ivanov wrote:
On Tue, 2011-10-04 at 13:50 +0200, Laurent Pinchart wrote:
On Tuesday 04 October 2011 13:46:32 Ivan T. Ivanov wrote:
On Tue, 2011-10-04 at 13:03
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date:Tue Oct 4 19:00:22 CEST 2011
git hash:2f4cf2c3a971c4d5154def8ef9ce4811d702852d
gcc version: i686-linux-gcc
2011/9/28 tvboxspy tvbox...@gmail.com:
Frontend bus lock for af9015 devices.
Last week, I aqcuired a dual KWorld PlusTV Dual DVB-T Stick (DVB-T 399U).
The lock is intended for dual frontends that share the same tuner I2C address
to stop either frontend sending data while any gate is open.
There are several bugs at saa7115 standards detection:
After the fix, the driver is returning the proper standards,
as tested with 3 different broadcast sources:
On an invalid channel (without any TV signal):
[ 4394.931630] saa7115 15-0021: Status byte 2 (0x1f)=0xe0
[ 4394.931635] saa7115
Acked-by: Mike Isely is...@pobox.com
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/video/pvrusb2/pvrusb2-hdw.c |7 +++
drivers/media/video/pvrusb2/pvrusb2-hdw.h |3 +++
drivers/media/video/pvrusb2/pvrusb2-v4l2.c |7 +++
3 files changed, 17
Instead of using V4L2_STD_ALL when no standard is detected,
trust that the maximum allowed standards are already filled by
the V4L2 core. It is better this way, as the bridge and/or the audio
decoder may have some extra restrictions to some video standards.
This also allow other devices like
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/video/pvrusb2/pvrusb2-v4l2.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/media/video/pvrusb2/pvrusb2-v4l2.c
b/drivers/media/video/pvrusb2/pvrusb2-v4l2.c
index 0d029da..ce7ac45 100644
Hi Antti,
I would like to made own firmware for Cypress FX2 based DVB device. Is there
any sample to look example?
I've done multiple FX2 firmware projects in the past, including DVB-T.
The technical reference manual for the FX2 explains the GPIF waveform
sampling engine very well. It also
I have had some luck with this patch. I am still getting fouled
recordings with tuner A but it's not consistent. I have yet to
ascertain if the problem occurs depending on the order of tuning to
have both tuners recording different frquencies at the same time, ie
Tuner B then Tuner A or vice
On Tue, Oct 04, 2011 at 03:00:55PM +0200, Laurent Pinchart wrote:
Hi Ivan,
Hi all,
On Tuesday 04 October 2011 13:54:12 Ivan T. Ivanov wrote:
On Tue, 2011-10-04 at 13:50 +0200, Laurent Pinchart wrote:
On Tuesday 04 October 2011 13:46:32 Ivan T. Ivanov wrote:
On Tue, 2011-10-04 at 13:03
I have been looking for correct device name for serial smart card reader
that is integrated to Anysee DVB USB devices. Consider it like old so
called Phoenix reader. Phoenix is de facto protocol used for such
readers and there is whole bunch of different RS232 (/dev/ttyS#) or
USB-serial
On Tue, Oct 04, 2011 at 10:43:59PM +0300, Antti Palosaari wrote:
I would like to made own firmware for Cypress FX2 based DVB device.
Is there any sample to look example?
http://linuxtv.org/cgi-bin/viewvc.cgi/dvb-hw/dvbusb-fx2/termini/
HTH
Johannes
--
To unsubscribe from this list: send the
On Wed, 2011-10-05 at 07:44 +1100, Jason Hecker wrote:
I have had some luck with this patch. I am still getting fouled
recordings with tuner A but it's not consistent. I have yet to
ascertain if the problem occurs depending on the order of tuning to
have both tuners recording different
Which Firmware are your using?
4.95
Yes, because it is also happening with other duo devices on Myth TV
0.24.1
OK, well that is what I am using so I guess I am stuck until it's fixed.
Josu what software and versions are you using?
--
To unsubscribe from this list: send the line unsubscribe
On Tue, Oct 04, 2011 at 03:00:55PM +0200, Laurent Pinchart wrote:
Hi Ivan,
On Tuesday 04 October 2011 13:54:12 Ivan T. Ivanov wrote:
On Tue, 2011-10-04 at 13:50 +0200, Laurent Pinchart wrote:
On Tuesday 04 October 2011 13:46:32 Ivan T. Ivanov wrote:
On Tue, 2011-10-04 at 13:03 +0200,
On Wed, Oct 05, 2011 at 12:22:09AM +0300, Antti Palosaari wrote:
I have been looking for correct device name for serial smart card
reader that is integrated to Anysee DVB USB devices. Consider it
like old so called Phoenix reader. Phoenix is de facto protocol used
for such readers and there is
On 10/05/2011 07:59 AM, Greg KH wrote:
On Wed, Oct 05, 2011 at 12:22:09AM +0300, Antti Palosaari wrote:
I have been looking for correct device name for serial smart card
reader that is integrated to Anysee DVB USB devices. Consider it
like old so called Phoenix reader. Phoenix is de facto
28 matches
Mail list logo
