On Thu March 14 2013 00:08:57 Benjamin Schindler wrote:
Hi
I recently upgraded from 3.2 to 3.7 and noticed, that I don't get any
sound anymore from my TV-card. tvtime still works fine, just with no
sound. As you can see from the snippet below, I have a hauppage WinTV
card which uses
Hi Hans
Thank you for the prompt response. I will try this once I'm home again.
Which patch is responsible for fixing it? Just so I can track it once it
lands upstream.
I have one more question - the wiki states the the WinTV-HVR-5500 is not
yet supported (as of June 2011) - is there an update
of a much longer patch series, so there may be other
patches involved in this particular problem, but I don't think so.
If you can perhaps test just that single patch then that would be useful
information. If that fixes the problem then that's a candidate for 'stable'
kernels.
I have one more
Hi Laurent, Guennadi,
On 11 March 2013 21:51, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Hi Javier,
[2.706939] omap3isp omap3isp: Revision 15.0 found
[2.712402] omap_iommu_attach: 1
[2.715942] omap_iommu_attach: 2
[2.719329] omap_iommu_attach: 3
[2.722778]
Hi Javier,
On Tuesday 12 March 2013 08:52:39 javier Martin wrote:
On 11 March 2013 21:51, Laurent Pinchart wrote:
Hi Javier,
[2.706939] omap3isp omap3isp: Revision 15.0 found
[2.712402] omap_iommu_attach: 1
[2.715942] omap_iommu_attach: 2
[2.719329]
Hi,
I'm trying to make omap3isp work with our DM3730 based board.
When I try to boot the kernel I get the following message:
[2.064239] omap3isp omap3isp: Revision 15.0 found
[2.070220] omap_iommu_attach: 1
[2.073669] omap_iommu_attach: 2
[2.077056] omap_iommu_attach: 3
[
I've just found the following thread where te problem is explained:
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-February/086364.html
The problem is related with the order iommu and omap3isp are probed
when both are built-in. If I load omap3isp as a module the problem is
gone
Hi Javier,
On Monday 11 March 2013 13:18:12 javier Martin wrote:
I've just found the following thread where te problem is explained:
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-February/086364.h
tml
The problem is related with the order iommu and omap3isp are probed
when
Hi Laurent,
thank you for your answer.
On 11 March 2013 16:01, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Hi Javier,
On Monday 11 March 2013 13:18:12 javier Martin wrote:
I've just found the following thread where te problem is explained:
http://lists.infradead.org/pipermail
Hi Javier,
On Monday 11 March 2013 16:28:58 javier Martin wrote:
On 11 March 2013 16:01, Laurent Pinchart wrote:
On Monday 11 March 2013 13:18:12 javier Martin wrote:
I've just found the following thread where te problem is explained:
http://lists.infradead.org/pipermail/linux-arm-kernel
if it will work well nowadays.
I experimented with my Kworld usb radio that uses the same driver
(radio-si470x). I use sox to redirect sound from radio:
sox --endian little -c 2 -S -r 96000 -t alsa hw:1 -t alsa -r 96000 hw:0
(i have problem with alsa: under-run because of sound card and radio
are connected
Hi, I'm going to unsubscribe this mailing list (cause of flooding my mailbox ;))
Please send a mail to me if there's any progress.
Sorry for any annoyance :(
Sincerely,
Henry Lin pika1...@gmail.com
2013/1/2 林博仁 pika1...@gmail.com:
Hi,
I tried to make a DVB-T reciever which uses ID
Hello,
I'm a Ubuntu and DMB-TH digital TV USB dongle user. The USB
dongle working flawlessly in Ubuntu 10.XX, but it failed after migrate
to latest Ubuntu 12.10. Then I using google to find out the problem and
suspect the problem come from DVBv3 migrate to DVBv5. Because
On Mon, Jan 14, 2013 at 1:01 PM, nise.design nise.des...@gmail.com wrote:
After google search I think the problem may be come from connection between
DMB-TH drivers and dvb_frontend.c broken. I wanted to know any example code
or instruction about DVBv3 driver connect to dvb_frontend.c. Thank
it is quite easy to comment
out / tweak with driver in order to find problem. With the experience
and luck it is only few hours to fix, but without a experience you
will likely need to learn a lot of stuff first.
I have not experience with the linux media drivers coding, so it probably
would take me
with driver in order to find problem. With the experience
and luck it is only few hours to fix, but without a experience you
will likely need to learn a lot of stuff first.
I have not experience with the linux media drivers coding, so it probably
would take me much more than a few hours or require lots
Hi,
I have a 'NOT Only TV DVB-T USB Deluxe' tuner device:
Model name: LV5TDLX DVB-T USB
P/N: STLV5TDLXT702
S/N: LV5TDLX120700116
USB ID: 1f4d:c803
This is based on the RTL2838UHIDIR chip with e4000 tuner (at least, that
is detected by various drivers).
I had some minor success with it with
it is quite easy to comment out / tweak
with driver in order to find problem. With the experience and luck it is
only few hours to fix, but without a experience you will likely need to
learn a lot of stuff first.
Of course those sniffs needed to take from working case, which just
makes
Hi,
I tried to make a DVB-T reciever which uses ID 187f:0202(Siano Mobile
Silicon Nice) work on my linux machine(Ubuntu 12.10 x86 32bit 3.5.x
kernel) and eventually found that only manually load 'smsdvb' module
make the dvb device create (it won't create if just plug-in the
hardware)
Dec 31
Hi guy's,
I have some problem with my new Gigabyte U8000-RH hybrid DVB-T and Analogue USB
device.
My idea is to use this dvb-t tuner together with my Raspberry Pi, XBMC and
tvheadend.
But now I try to use tuner in my notebook with Fedora 17 and kernel
3.6.10-2.fc17.x86_64
The device I
Hi Adam,
On Monday 05 November 2012 16:02:08 Adam Wozniak wrote:
I'm working with a custom board based on an Overo WaterStorm com. The
processor is a DM3730. The kernel is 2.6.32 based.
2.6.32 very probably means you're using the old TI driver. Please don't.
That's buggy and totally
understanding the
driver:
1.) MINOR PROBLEM: The card is not auto-recognized. The module needs to be
loaded with the option card=32 to get it recognized.
2.) MINOR PROBLEM: With PAL camera, there is a black left border of
about 20-30 pixel. No border on the right side.
3.) MAJOR PROBLEM: The image
On Tue, Nov 13, 2012 at 9:10 AM, Neuer User auslands...@gmx.de wrote:
Hello
First of all, I don't know, if this is the right mailing list. I haven't
found any other. The video4linux list seems to be abandoned.
I am testing a Commell MPX-885 mini-pcie card, which is based on a
cx23885 chip.
confirm that the biggest problem, the color problem, is fixed at
least with kernel 3.5.7 (maybe earlier).
The minor ones (card not autodetected, and black border on the left
side) can probably be dealt with, e.g. in postprocessing. Or is there a
chance to fix these in the driver?
Michael
Am 13.11.2012
by the cx23885.
I can confirm that the biggest problem, the color problem, is fixed at
least with kernel 3.5.7 (maybe earlier).
Ok, good.
The minor ones (card not autodetected, and black border on the left
side) can probably be dealt with, e.g. in postprocessing. Or is there a
chance to fix
the original MPX support as a consulting project.
Devin
Hi Devin
Thanks for the help.
The HSYNC problem is bigger than I thought. I compared the captured
image with an image from another (USB) video digitizer and it is obvious
that the image has lost about 10-20% on the right side
On Tue, Nov 13, 2012 at 1:02 PM, Neuer User auslands...@gmx.de wrote:
The HSYNC problem is bigger than I thought. I compared the captured
image with an image from another (USB) video digitizer and it is obvious
that the image has lost about 10-20% on the right side and on the bottom.
Can
Am 13.11.2012 19:54, schrieb Devin Heitmueller:
Almost certainly just changes needed for the cx25840 driver. These
are all basic issues with the video decoder core. Google around - the
cx25840 datasheet is readily available. You have to watch out though
because there are some subtle
On Tue, Nov 13, 2012 at 2:03 PM, Neuer User auslands...@gmx.de wrote:
Thanks, you probably hinted me into the right direction. I use mplayer
to play the video stream and mplayer does indeed recognize a 640x480
video stream.
I am not using any crop settings for these tests. But maybe it is
.
Absolutely, you found the problem. Thanks a lot. Indeed as soon as I
define a resolution (even the 640x480) I get the full picture. Only if
NO resolution is specified, I get 640x480 as a croped version.
Funny bug. For me I can live with the current solution. I can define the
resolution with mplayer
On Sun, Oct 14, 2012 at 11:39 AM, Yuriy Davygora
davyg...@googlemail.com wrote:
Hello,
I have trouble compiling the 3.4.9 kernel with genkernel (gentoo)
having enabled the Ali Corp webcam (m5602) driver.
Here's the output of the ver_linux script:
=
---
* Video For Linux (NEW)
[*] Video capture adapters (NEW) ---
[*] V4L USB devices (NEW) ---
* GSPCA based webcams (NEW) ---
* Ali USB m5602 Camera Driver
The problem is not the compilation, but the linking step.
$ make
make[1]: Nothing to be done
On Mon, Oct 15, 2012 at 10:21 AM, Yuriy Davygora
davyg...@googlemail.com wrote:
Hi Ezequiel,
thank you very very much! This was indeed the problem. I wonder, why
menuconfig did not warn me that USB is marked to be compiled as
module, when I chose to build in the gspca support
(Adding media list in Cc)
On Sun, Oct 14, 2012 at 11:39 AM, Yuriy Davygora
davyg...@googlemail.com wrote:
Hello,
I have trouble compiling the 3.4.9 kernel with genkernel (gentoo)
having enabled the Ali Corp webcam (m5602) driver.
Here's the output of the ver_linux script:
the problem is that IR edges aren't being reported until
triggered by more IR edges.
Can you reproduce the issue on a more contemporary kernel?
Yes. The buggy behavior is present in Ubuntu 12.04 (IIRC, kernel
v3.2.*). I also know that the buggy behavior is present at v3.4.x of
the kernel
properly. The major problem is that every
keystroke is registered after the next keystroke. So, if I press the
sequence 123 on the remote, it actually comes up with only 12. If
I then if I wait for 5 seconds, the 3 gets lost.
Now I tried to bisect the kernel and it lead to the following commit
Hi Sean,
I am not an expert on the kernel. So please excuse me if I give the
wrong answer somewhere.
On Fri, Aug 10, 2012 at 3:47 PM, Sean Young s...@mess.org wrote:
Are you runnning the lircd user space process for input or relying on
the in-kernel decoders?
For my testing, I booted the
I added Kernel GPIO interface for cxd2820r driver. What I understand I
should select GPIOLIB in order to compile cxd2820r now. I am not sure if
that problem comes from recent Media Kconfig re-arrangement or not, but
for some reason I didn't saw it earlier.
What I should put for Kconfig
Hi,
I have a saa7134 analog tv card (Avermedia PCI pure m135a) with an IR
remote. The IR remote is recognized by a standard keyboard and lirc
used to work fine with this. However, from kernel v2.6.35, the IR
remote does not work properly. The major problem is that every
keystroke is registered
Hi,
I have a saa7134 analog tv card (Avermedia PCI pure m135a) with an IR
remote. The IR remote is recognized by a standard keyboard and lirc
used to work fine with this. However, from kernel v2.6.35, the IR
remote does not work properly. The major problem is that every
keystroke is registered
a stk7700d_frontend_attach. This tries to set
GPIOs 6,9,4 and 7 to 1, then it tries to set GPIO10 to 0 before resetting it to
1 and then finally tries to set GPIO 0 to 1. The driver reports no problem
doing this but when you drill deeper you find that it does not seem to be doing
what it is supposed
I have tuning problem for some analog channels with the Terratec Cinergy
XS 0ccd:0042. This card is unable to tune into some channels.
I have another version of this hardware with the ID's 0ccd:005e.
Interestingly, this Hardware-Version tunes without any problems all
available channels
On Mon, Jul 23, 2012 at 3:40 AM, Radek Mašín ra...@masin.eu wrote:
Hello,
may be one more problem. I use Zoneminder software for capturing pictures
from card and occasionally
I get corrupted picture. Please take a look for attached files.
Looks like the IRQ handler wasn't servicing fast
, if it is enought.
Regards
Radek Masin
Dne Po, 07/23/2012 02:20 odp., Devin Heitmueller dheitmuel...@kernellabs.com
napsal(a):
On Mon, Jul 23, 2012 at 3:40 AM, Radek Mašín ra...@masin.eu wrote:
Hello,
may be one more problem. I use Zoneminder software for capturing pictures
from card
Hi,
I have tuning problem for some analog channels with the Terratec Cinergy
XS 0ccd:0042. This card is unable to tune into some channels.
I have another version of this hardware with the ID's 0ccd:005e.
Interestingly, this Hardware-Version tunes without any problems all
available channels
Hello,
I have upgraded my testing system with cx25821 based video capture card to
system (OpenSuSE 12.1)
with kernel 3.4.4 and driver for cx25821 doesn't work. Previous system was with
kernel 2.6.37 (OpenSuSE 11.4)
with this patch http://patchwork.linuxtv.org/patch/10056/ and manualy compiled
Hi Radek,
On Wed, Jul 18, 2012 at 9:52 AM, Radek Mašín ra...@masin.eu wrote:
Hello,
I have upgraded my testing system with cx25821 based video capture card to
system (OpenSuSE 12.1)
with kernel 3.4.4 and driver for cx25821 doesn't work. Previous system was
with kernel 2.6.37 (OpenSuSE
Radek,
On Wed, Jul 18, 2012 at 10:14 AM, Ezequiel Garcia elezegar...@gmail.com wrote:
Hi Radek,
I think the attached patch will solve this issue.
Please test and tell me if it did,
Ezequiel.
0001-cx25821-Remove-bad-strcpy-to-read-only-char.patch
Description: Binary data
Hello,
I can test it without problems. Please send me a patch.
Regards
Radek Masin
ra...@masin.eu
Dne St, 07/18/2012 03:14 odp., Ezequiel Garcia elezegar...@gmail.com
napsal(a):
Hi Radek,
On Wed, Jul 18, 2012 at 9:52 AM, Radek Mašín ra...@masin.eu wrote:
Hello,
I have upgraded my
On Wed, Jul 18, 2012 at 10:45 AM, Radek Mašín ra...@masin.eu wrote:
Hello,
I can test it without problems. Please send me a patch.
I already did :-) Please checkout my previous mail.
Thanks,
Ezequiel.
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a
Hello,
with your patch driver is working properly. I see devices in /dev directory and
in dmesg
is attached output:
[5.124858] cx25821: driver version 0.0.106 loaded
[5.124890] cx25821: Athena pci enable !
[5.124891] cx25821:
[5.124892] ***
[
On Wed, Jul 18, 2012 at 11:38 AM, Radek Mašín ra...@masin.eu wrote:
Hello,
with your patch driver is working properly. I see devices in /dev directory
and in dmesg
is attached output:
Great! That's good news. I'll send the patch to the list later.
If you encounter any other problems, please
i have two cards both of them are for dmb-th (mainly used in china and
hong kong). however, these two cards stop working after upgraded the
kernel to 3.3. sadly the drivers were writen by a person David Wong
who has been passed away. i traced the code and found a function
set_delivery_system which
Dear v4l-dvb experts,
I'm stuck trying to get a hybrid tv card that seems to be well supported
working. The box is labeled simply pctv hd card 800i; Newegg sells it as
Hauppauge pctv pci 800i; Linuxtv has a setup page for it as a Pinnacle
card
software, in the google search I found the
same problem on fedora on link
https://bugzilla.redhat.com/show_bug.cgi?id=739448
If I downgrade the kernel to 2.6.38.12 the webcam work fine !!
I think that the problem is on the UVC driver on the kernel after 2.6.38.12 to
latest kernel
Thanks
Tiziano
Hi,
BGR3, RGB3, YU12 and YV12 are provided through libv4l, the original
unconverted stream format provided through uvcvideo driver is YUYV, if
this is fine then this is probably an issue with libv4l.
Regards,
Paulo
2012/4/5 Chris Rankin ranki...@googlemail.com:
Hi,
I have a UVC video device,
Hi,
From what you describe I would say that during conversion a YUYV (2
bytes per pixel) size (be it a buffer or loop iterations) is being
used for RGB3 (3 bytes per pixel), so you only get 2/3 of the picture.
Does this happen in any resolution ?
Regards,
Paulo
2012/4/5 Paulo Assis
Does this happen in any resolution ?
All resolutions except 960x720: in this resolution I only get a tiny strip of
image across the top of the window.
Cheers,
Chris
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
Hi,
I have a UVC video device, which lsusb describes as:
046d:0992 Logitech, Inc. QuickCam Communicate Deluxe
With the 3.3.1 kernel, the bottom 3rd of the video window displayed by
guvcview is completely black. This happens whenever I select either
BGR3 or RGB3 as the video output format.
V4L2 device Pinnacle Dazzle DVC 90/100/101/ using driver: em28xx
(version: 0.1.2)
Fedora 14
VLC 1.1.12
I know about the issue with changing video standards in this VLC UI
version. That's not the problem, and I've confirmed it with a slightly
more up to date Ubuntu equivalent. I get the same
On Mon, Apr 2, 2012 at 5:02 PM, Colin Eby colin...@isallthat.com wrote:
There's clear evidence I can get some kind of tool chain to work in
Windows. But I wondered if there wasn't some fine tuning to the driver
that would get Linux rig to work. And I wondered if there were known
issues around
the NTSC_443 norm. Forgive me if I've missed any, but I
haven't found any so far.
It's probably also worth mentioning that if you want to try to debug
this yourself, the problem is probably in the saa711x driver (the
video decoder chip in the Dazzle), not the em28xx driver.
Devin
--
Devin J
VO5630 VTR using BNC to RCA video out
V4L2 device Pinnacle Dazzle DVC 90/100/101/ using driver: em28xx
(version: 0.1.2)
Fedora 14
VLC 1.1.12
I know about the issue with changing video standards in this VLC UI
version. That's not the problem, and I've confirmed it with a slightly
more up to date
Hello,
I'm running into an issue when compiling the last version of media_build :
/usr/src/linux-headers-2.6.32-5-common/include/linux/kernel.h:366:1: warning:
this is the location of the previous definition
CC [M] /home/toto/sources/media_build/v4l/hdpvr-control.o
CC [M]
one less argument that
in the older kernel version you are using.
You will need to fix the drivers/media/video/ivtv/ source files to fix the
problem. If you develop a patch for the backport, you can submit it and
hopefully get it included as a backward compatibilty patch for the media_build
I'm running kernel-ml-2.6.35-14.1.el5.elrepo
I'm following the info on:
http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
First I run:
git clone git://linuxtv.org/media_build.git
cd media_build
Then when I run ./build, it stops with the following error:
from a cable feed, both free HD
and SD.
This problem happens regardless of how the drivers are installed.
I noticed this:
[ 763.341895] s5h1409_readreg: readreg error (ret == -6)
And was wondering if this is related to the card appearing to be less
well known?
I will enable debug and poke
.
Is this a known problem, or do I need to change my configuration in some
way, to accommodate the 3.3 kernel changes?
Thanks..
Robert Gadsdon.
--
.
Robert Gadsdon
email: rhgadsdonatgmail.com
.
--
To unsubscribe from this list: send the line
Hello,
there must be made some changes to the V4L2 IOCTLs, also the V4L2 API
since 2.6.39.
Upon starting xawtv, i get following errors:
ioctl: VIDIOC_S_CTRL(id=9963785;value=0): Unpassender IOCTL
(I/O-Control) für das Gerät ioctl: VIDIOC_S_CTRL(id=9963785;value=1):
Unpassender IOCTL
Hello,
there must be made some changes to the V4L2 IOCTLs, also the V4L2 API
since 2.6.39.
Upon starting xawtv, i get following errors:
ioctl: VIDIOC_S_CTRL(id=9963785;value=0): Unpassender IOCTL
(I/O-Control) für das Gerät ioctl: VIDIOC_S_CTRL(id=9963785;value=1):
Unpassender IOCTL
no one ?
Zitat von Thor myt...@x-defense.de:
hi all,
checked out git on january 8th.
have the cam working,but it stops working every two or 3 days (system
is running 24 hours)
sometimes it recovers on its own:
Jan 21 20:59:45 zotac kernel: [81316.229519] dvb_ca adapter 0: CAM
tried to
hi all,
checked out git on january 8th.
have the cam working,but it stops working every two or 3 days (system
is running 24 hours)
sometimes it recovers on its own:
Jan 21 20:59:45 zotac kernel: [81316.229519] dvb_ca adapter 0: CAM
tried to send a buffer larger than the ecount size!
Jan 21
Hi,
I have a MythTV backend with a Hauppauge HVR-2250 (dual tuner,
ATSC?QAM, PCIe) and a Ceton InfiniTV4 (quad tuner, QAM/cable card,
PCIe). Over the weekend, I started intermittently seeing corrupt
recordings that were painful to watch.
I eventually narrowed the problem down to when both
.
I eventually narrowed the problem down to when both tuners on the 2250
are active at the same time. In this case, both recordings have
corruption (CRC errors, etc.). The InfiniTV4 does not appear to be
affected by anything going on on the 2250. Likewise, the 2250 does
not appear
intermittently seeing corrupt
recordings that were painful to watch.
I eventually narrowed the problem down to when both tuners on the 2250
are active at the same time. In this case, both recordings have
corruption (CRC errors, etc.). The InfiniTV4 does not appear to be
affected
Daniel,
Didn't work for me either - had to use repository. Same kernel base
version, but on gentoo though.
// Fredrik
On Thu, Jan 12, 2012 at 19:02, Daniel Rindt daniel.ri...@googlemail.com wrote:
Hello,
i am running Fedora 16 64bit and have no luck to get working the WinTV
HVR-930C.
Hello,
i am running Fedora 16 64bit and have no luck to get working the WinTV
HVR-930C. Invoked command lsusb told me: Bus 001 Device 002: ID
2040:1605 Hauppauge. Installed from update-testing-repository is the
most recent kernel version kernel-3.1.8-2.fc16.x86_64.
Loaded the em28xx by hand and
Hi,
I've got these kind of old usb 2.0 grabbers (GrabBeex) based on some
em28xx chipsets that are not correctly identified under linux. Here is the
dmesg log.
A video device is created but there are no controls in v4l-info and dmesg
seems to see that everything is probably not correctly
device registered as video7
Now I plan to start using a newer version of the Linux kernel 3.2.0-rc4,
but unfortunately faced with the problem. That suggest?
I'm quite surprised. I've just tested 3.2-rc2 here, and got no oops when
loading the omap3-isp driver. I've tried compiling the driver
[mailto:dub...@crans.org]
Sent: mercredi 7 décembre 2011 00:05
To: sraill...@coexsi.fr
Subject: Tr. : Irdeto Cam Problem, any help
C'est pour toi ça.
--
Brice
- Forwarded message -
De : JULIAN GARDNER joo...@btinternet.com
Pour : linux-media@vger.kernel.org linux-media@vger.kernel.org
Hi All,
I have problem in booting the Kernel.
Here the problematic part of the boot message.
As I understand it happens when isp_probe calling and it calls isp-iommu_dev =
omap_find_iommu_device(isp);
[1.976715] Linux media interface: v0.10
[1.981781] Linux video capture interface
Hi Alex,
Alex Gershgorin wrote:
Hi All,
I have problem in booting the Kernel.
Here the problematic part of the boot message.
As I understand it happens when isp_probe calling and it calls isp-iommu_dev =
omap_find_iommu_device(isp);
[1.976715] Linux media interface: v0.10
[1.981781
.
Regards,
Alex Gershgorin
Hi Alex,
Alex Gershgorin wrote:
Hi All,
I have problem in booting the Kernel.
Here the problematic part of the boot message.
As I understand it happens when isp_probe calling and it calls isp-iommu_dev
= omap_find_iommu_device(isp);
[1.976715] Linux media
Alex Gershgorin wrote:
Hi Sakari,
Thank you for your quick response and sorry for stupid question.
Yes CONFIG_OMAP_IOMMU and CONFIG_OMAP_IOVMM enabled,
because OMAP 3 camera controller depends on the CONFIG_OMAP_IOVMM and
CONFIG_OMAP_IOMMU.
Please tell me how I can use dmabuf instead of the
-rc4, but
unfortunately faced with the problem.
That suggest?
Thanks,
Alex Gershgorin --
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.kernel.org/majordomo-info.html
device registered as video7
Now I plan to start using a newer version of the Linux kernel 3.2.0-rc4,
but unfortunately faced with the problem. That suggest?
I'm quite surprised. I've just tested 3.2-rc2 here, and got no oops when
loading the omap3-isp driver. I've tried compiling the driver
device registered as video7
Now I plan to start using a newer version of the Linux kernel 3.2.0-rc4,
but unfortunately faced with the problem. That suggest?
I'm quite surprised. I've just tested 3.2-rc2 here, and got no oops when
loading the omap3-isp driver. I've tried compiling the driver
Hi,
I'm implementing new adapter for DVB, I built a module to register the
adapter and demux/net devices. From the kernel log I see all actions are
performed fine and dvb_register_device (called by dvb_dmxdev_init) is called
successfully for net0/demux0/dvr0, however, demux0/dvr0 devices do not
/dvr0, however, demux0/dvr0 devices do not show
up, ls /sys/class/dvb shows only dvb0.net0 (and nothing appears under
/dev/dvb/ anyhow).
What could cause not having demux0/dvr0 registered? Note that net0 shows up
fine.
It is hard to tell the exact problem without looking into the driver. Are you
On 07-12-2011 13:50, Mauro Carvalho Chehab wrote:
It is hard to tell the exact problem without looking into the driver. Are you
handling the error codes returned by the register functions?
You can follow what's happening inside your driver by enabling tracepoints.
Here is one of the scripts I
Been trying now to get my IrdetoCam and card working, im using mumudvb for this.
Turning on debug i get the folowing in the output
nfo: Autoconf: Channel number : 0, name : ERT World service id 0
Info: Autoconf: Multicast4 ip : 227.25.0.1:1234
Deb0: Autoconf: pids : 5001
Hi Hendrik,
On Sunday 27 November 2011 14:04:02 Hendrik Sattler wrote:
Hi,
I just updated by self-built kernel-from v3.1 to v3.1.3.
With the new version, my built-in webcam[1] does not work anymore but it
did with v3.1.
$ luvcview
luvcview 0.2.6
SDL information:
Video driver: x11
Hi Laurent,
Am Montag, 28. November 2011, 11:37:52 schrieb Laurent Pinchart:
uvcvideo: Failed to submit URB 0 (-28).
Same for using e.g. Google+ Hangouts which worked fine using v3.1.
Any ideas what might be wrong?
I'm tempted to blame
f0cc710a6dec5b808a6f13f1f8853c094fce5f12 on-top of v3.1.3 and
now the webcam is working again.
Should this go to v3.1.4 and 3.2?
The problem has just been reported to the linux-usb mailing list (uvcvideo:
Failed to submit URB 0 (-28) mail thread). Let's see what will happen.
--
Regards,
Laurent Pinchart
--
To unsubscribe
Hi,
I just updated by self-built kernel-from v3.1 to v3.1.3.
With the new version, my built-in webcam[1] does not work anymore but it did
with v3.1.
$ luvcview
luvcview 0.2.6
SDL information:
Video driver: x11
A window manager is available
Device information:
Device path: /dev/video0
the problem. From what I see by now, the HDD behaves flaky too.
--
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.kernel.org/majordomo-info.html
Alan Stern wrote:
This is probably a low-level hardware error. Interference between the
two ports of some kind.
This is quite possible. Have been able to produce a more verbose logfile
snippet.
[25045.734288] af9013_update_ber_unc: err bits:1286 total bits:1632 abort
count:0
On Sat, 26 Nov 2011, Johann Klammer wrote:
Alan Stern wrote:
This is probably a low-level hardware error. Interference between the
two ports of some kind.
This is quite possible. Have been able to produce a more verbose logfile
snippet.
The log shows that your EHCI controller reports
On Fri, 2011-11-25 at 03:21 +0100, Johann Klammer wrote:
When using a DVB-T Dongle and an external HDD simultaneously, EHCI
almost always disconnects.
Ideally HDD, and DVB devices shouldn't share the the same controller.
Most systems have two.
However, it is difficult for users know how
Alan Stern wrote:
This could be the result of an electrical glitch or power fluctuation.
Are these devices bus-powered?
The DVB Stick is. The HDD is not.
Or it could simply be something wrong with your EHCI controller.
Possible. The power supply is old, too and there's a telephone in the
201 - 300 of 754 matches
Mail list logo
