I tried to compile media-build on Ubuntu 18.04. (gcc 7.3.0) with Kernel
4.15 and get this error:
/home/martin/media_build/v4l/video-i2c.c: In function 'video_i2c_probe':
/home/martin/media_build/v4l/video-i2c.c:456:16: error: implicit
declaration of function 'device_get_match_data'; did you me
To find the responsible patch for a regression, I need to test older drivers.
(1, 3 or 6 months ago) How can I do this with media_build?
I don't really understand how the build script works. It seems that it doesn't
use the current media_tree.git, but loads instead a driver snapshot
(http://l
> > I suggest to increase the ivtv driver version number when implementing
> > the changes. The application (which must be backward compatible) should
> > be able to determine which ioctl it has to use.
>
> These days the version number of all drivers is the same as the kernel
> version number, s
Hi Hans,
I am not sure if I understand this right. You wrote:
"Comments are added on how to convert the legacy ioctls to standard V4L2 API
in applications. Perhaps these legacy ioctls in ivtv can even be removed in a
few years time."
But the patch looks for me as if the currently used ioctls s
My PVR350 (ivtv) and my PVRUSB2 Model 29034 (pvrusb2) have a much lower volume
when switching to radio.
On the HVR1300 (cx88-blackbird, Philips FMD1216ME tuner) this is no problem;
radio has same volume level.
The saa7134-based KNC One TV Station DVR (similar tuner: FMD1216MEX) has a
very low
The following cards have a Multi Standard tuner with radio:
KNC One TV-Station DVR (saa7134) FMD1216MEX
HVR1300 (cx88-blackbird) Philips FMD1216ME
/dev/radio0 is present and working.
Both drivers do not report the radio when using VIDIOC_QUERYCAP.
Is this a bug, or is there no clear specification
I tried two things:
1.)
compile media_build.git for my 2.6.32 Ubuntu Kernel. It compiles, driver loads
without errors.
[ 8.500109] DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C)...
[ 8.981263] DVB: registering adapter 1 frontend 0 (Philips TDA10021 DVB-C)...
But when I start vdr
I tried to compile git://linuxtv.org/mchehab/new_build.git on a 2.6.32
As alread reported by somebody earlier, there is a problem with hdpvr-i2c.c :
/home/martin/linuxtv_new_build/new_build/v4l/hdpvr-i2c.c: In function
'hdpvr_new_i2c_ir':
/home/martin/linuxtv_new_build/new_build/v4l/hdpvr-i2c.c:
Since some months I didn't test any new drivers, because I don't want to run
an unstable kernel. The v4l-dvb hg is obviously dead, although I never read a
formally announcement. Requests remain unanswered
(http://article.gmane.org/gmane.linux.drivers.video-input-
infrastructure/27069/)
In the
Hi Douglas,
you backported a few ivtv patches from June 2010 to v4l-dvb hg:
http://linuxtv.org/hg/v4l-
dvb/log/abd3aac6644e/linux/drivers/media/video/ivtv/ivtv-streams.c
Unfortunately one patch is missing, which is important for proper function:
http://git.linuxtv.org/media_tree.git?a=commit;h=f0
The HVR1300 driver has several bugs:
1.
When executing VIDIOC_S_EXT_CTRLS or VIDIOC_S_FREQUENCY on the mpeg device
while the mpeg device is active (capturing), the driver calls
blackbird_stop_codec(). This stops the encoder (API call
CX2341X_ENC_STOP_CAPTURE).
Unfortunately, the encoder gets ne
I can confirm that the patch from Waling works. IR works, and vdr detects the
Alphacrypt inside the CAM. So I think descrambling would also work, but I have
no Pay-TV card to test it.
The patch should be merged!
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body
Am Dienstag, 15. Juni 2010, um 03:39:24 schrieb Dmitri Belimov:
> Hi Martin
>
> > This is not only a problem with saa7134, but also with other drivers
> > like budget-ci. The bug was also present in 2.6.35-rc1
>
> I see this bug with 2.6.33 and fresh hg.
>
> > There have been several reports her
This is not only a problem with saa7134, but also with other drivers like
budget-ci.
The bug was also present in 2.6.35-rc1
There have been several reports here in the list since a few weeks:
http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/20198
http://article.gmane.org/gm
It's sad that this bug has gone into 2.6.35-rc1.
I already reported it on 24.05.2010:
http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/19564/
Unfortunately it didn't get any attention, which makes me a little bit
depressive...
What is the right way to report bugs if code
I guess it is a similar problem like the one that was solved a few months ago
with this patch:
http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/14232
I compiled the current v4l-dvb hg against the 2.6.32 Ubuntu 10.04 kernel
May 24 13:30:22 ubuntuvdr1 kernel: [5.629408]
Hi Guy,
great news! Does it also work with QAM256?
Hope the patch becomes accepted. And maybe anybody can add support for the CI
later.
Greets,
Martin
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo i
Am Donnerstag, 31. Dezember 2009 20:40:15 schrieb Andy Walls:
> On Thu, 2009-12-31 at 14:26 -0500, Andy Walls wrote:
> > On Thu, 2009-12-31 at 18:15 +0100, Martin Dauskardt wrote:
>
> Some corrections to errors:
> > My preferences in summary, is that not matter what the di
Hi everybody,
first test results from me:
As expected, the double "ivtv_msleep_timeout(300, 1);" in ivtv-streams.c
increases the time for stopping/starting a stream. I removed the first call
and it still works fine.
@ Mike:
Previously I suggested to add a msleep(300) in state_eval_decoder_run
fine without patch.)
I am also using 2.6.32 and have two DVB and two v4l2 cards in my machine.
Greets,
Martin Dauskardt
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.
Hi everybody and Merry Christmas,
Andy Walls wrote:
> I have a version of the change for the ivtv/PVR-150 tinny audio fix at
>
> http://linuxtv.org/hg/~awalls/v4l-dvb-bugfix
> http://linuxtv.org/hg/~awalls/v4l-dvb-bugfix/rev/7753cdcebd28
>
>
> It separates out the enable/disable of
Am Samstag, 6. Juni 2009 03:59:41 schrieb Andy Walls:
> Hi,
>
> This is version 2 of the patch that:
>
> 1. adds explicit support for the FQ1216LME MK3
>
> 2. points the tveeprom module to the FQ1216LME MK3 entry for EEPROMs
> claiming FQ1216LME MK3 and MK5.
>
> 3. refactors some code in simple
I should add that the picture quality is with all tested tuner types worse
than with my PVR250/350. I don't know if a PVR150 is in generally worse than
a PVR250. I can't call it really noisy, but in german I would say the picture
is a little bit "grobkörnig". It really needs a temporal filter se
Am Montag, 25. Mai 2009 21:34:43 schrieb Martin Dauskardt:
> #define TUNER_PHILIPS_FM1216MK5 79
> result: picture o.k. , but audio disappears every few seconds (for about 1-2
> seconds, then comes back)
correction: This is not a problem of tuner type 79. It happens also w
> #define TUNER_PHILIPS_FQ1216ME 24 /* you must actively select
B/G/D/K, I, L, L` */
> #define TUNER_PHILIPS_FQ1216AME_MK4 56 /* Hauppauge PVR-150 PAL */
>
> #define TUNER_PHILIPS_FM1216ME_MK3 38
>
> #define TUNER_PHILIPS_FMD1216ME_MK3 63
> #define TUNER_PHILIPS_F
Hi Andy,
> Martin,
>
> I don't see tuner type 81 in the list in tuners.h. I do see:
>
>
> #define TUNER_PHILIPS_FQ1216ME 24 /* you must actively select
B/G/D/K, I, L, L` */
> #define TUNER_PHILIPS_FQ1216AME_MK4 56 /* Hauppauge PVR-150 PAL */
>
> #define TUNER_PHILIPS_F
26 matches
Mail list logo