I'm getting these errors:
cx22702_writereg: error (reg == 0x0c, val == 0x40, ret == -6)
cx22702_writereg: error (reg == 0x00, val == 0x01, ret == -6)
cx22702_writereg: error (reg == 0x0d, val == 0x00, ret == -6)
cx22702_writereg: error (reg == 0x0d, val == 0x01, ret == -6)
cx22702_readreg: readreg
On Friday 23 October 2009 06:13:30 Jean Delvare wrote:
> Hi folks,
>
> I am looking for details regarding the DVB frontend API. I've read
> linux-dvb-api-1.0.0.pdf, it roughly explains what the FE_READ_BER,
> FE_READ_SNR, FE_READ_SIGNAL_STRENGTH and FE_READ_UNCORRECTED_BLOCKS
> commands return, how
> We did discuss this briefly during the v4l-dvb mini-summit and I know Mike
> Krufky knew what to do about this, but for the life of me I can't remember
> what it was. I should have made a note of it...
>
> Mike, can you refresh my memory?
You are correct Hans. Mike has some patches that begin to
On Fri, Oct 23, 2009 at 4:12 AM, Markus Rechberger
wrote:
> On Thu, Oct 22, 2009 at 10:29 PM, Manu Abraham wrote:
>> On Fri, Oct 23, 2009 at 12:10 AM, Mauro Carvalho Chehab
>> wrote:
>>> Em Thu, 22 Oct 2009 21:13:30 +0200
>>> Jean Delvare escreveu:
>>>
Hi folks,
I am looking for
On Thu, Oct 22, 2009 at 10:29 PM, Manu Abraham wrote:
> On Fri, Oct 23, 2009 at 12:10 AM, Mauro Carvalho Chehab
> wrote:
>> Em Thu, 22 Oct 2009 21:13:30 +0200
>> Jean Delvare escreveu:
>>
>>> Hi folks,
>>>
>>> I am looking for details regarding the DVB frontend API. I've read
>>> linux-dvb-api-1
> Em Thu, 22 Oct 2009 21:13:30 +0200
> Jean Delvare escreveu:
>
>> Hi folks,
>>
>> I am looking for details regarding the DVB frontend API. I've read
>> linux-dvb-api-1.0.0.pdf, it roughly explains what the FE_READ_BER,
>> FE_READ_SNR, FE_READ_SIGNAL_STRENGTH and FE_READ_UNCORRECTED_BLOCKS
>> com
> The attach patch modifies v4l2-ctl -I to also output signal status as
> detected by the driver/hardware. This info is available in the status
> field of the data returned by VIDIOC_ENUMINPUT which v4l2-ctl -I
> already calls. The strings are copied from the v4l2 api specification
> and could per
> Attached patch adds support for running the VIDIOC_QUERYSTD ioctl from
> v4l2-ctl.
>
> Best regards
>
> Sigmund Augdal
>
Thanks! This looks good to me.
Signed-off-by: Hans Verkuil
--
Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom
--
To unsubscribe from this list: send
On Fri, Oct 23, 2009 at 12:10 AM, Mauro Carvalho Chehab
wrote:
> Em Thu, 22 Oct 2009 21:13:30 +0200
> Jean Delvare escreveu:
>
>> Hi folks,
>>
>> I am looking for details regarding the DVB frontend API. I've read
>> linux-dvb-api-1.0.0.pdf, it roughly explains what the FE_READ_BER,
>> FE_READ_SNR
Em Thu, 22 Oct 2009 21:13:30 +0200
Jean Delvare escreveu:
> Hi folks,
>
> I am looking for details regarding the DVB frontend API. I've read
> linux-dvb-api-1.0.0.pdf, it roughly explains what the FE_READ_BER,
> FE_READ_SNR, FE_READ_SIGNAL_STRENGTH and FE_READ_UNCORRECTED_BLOCKS
> commands retur
On Thu, 22 Oct 2009, [UTF-8] Ozan ÃaÄlayan wrote:
> Alan Stern wrote:
> > On Thu, 22 Oct 2009, [UTF-8] Ozan Ãâ¡aßlayan wrote:
> >
> >
> >> Here's the outputs from /sys/kernel/debug/usb/ehci:
> >>
> >> periodic:
> >>
> >> size = 1024
> >>1: qh1024-0001/f6ffe280 (h2 e
On Thu, Oct 22, 2009 at 12:27 PM, Devin Heitmueller
wrote:
> I could have had this problem solved six months ago for 98% of the
> community, and instead we are right where we have been since the
> beginning of the project.
This is really a shame too considering the enormous amount of people,
both
On Thu, Oct 22, 2009 at 3:13 PM, Jean Delvare wrote:
> Hi folks,
>
> I am looking for details regarding the DVB frontend API. I've read
> linux-dvb-api-1.0.0.pdf, it roughly explains what the FE_READ_BER,
> FE_READ_SNR, FE_READ_SIGNAL_STRENGTH and FE_READ_UNCORRECTED_BLOCKS
> commands return, howe
Hi folks,
I am looking for details regarding the DVB frontend API. I've read
linux-dvb-api-1.0.0.pdf, it roughly explains what the FE_READ_BER,
FE_READ_SNR, FE_READ_SIGNAL_STRENGTH and FE_READ_UNCORRECTED_BLOCKS
commands return, however it does not give any information about how the
returned value
This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.
Results of the daily build of v4l-dvb:
date:Thu Oct 22 19:00:04 CEST 2009
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 13156:f6680fa8e7ec
gcc version: gcc
Alan Stern wrote:
> On Thu, 22 Oct 2009, [UTF-8] Ozan Çağlayan wrote:
>
>
>> Here's the outputs from /sys/kernel/debug/usb/ehci:
>>
>> periodic:
>>
>> size = 1024
>>1: qh1024-0001/f6ffe280 (h2 ep2 [1/0] q0 p8)
>>
>
> There's something odd about this. I'd like to see
Attached is a patch that contains driver side changes to implement the
features that were added to v4l2-ctl by my two previous patches. It is
based on an old kernel and is only tested for one single capture card,
so this patch is provided for reference only, not for inclusion into
the drivers as is
The attach patch modifies v4l2-ctl -I to also output signal status as
detected by the driver/hardware. This info is available in the status
field of the data returned by VIDIOC_ENUMINPUT which v4l2-ctl -I
already calls. The strings are copied from the v4l2 api specification
and could perhaps be mod
Attached patch adds support for running the VIDIOC_QUERYSTD ioctl from v4l2-ctl.
Best regards
Sigmund Augdal
v4l2-ctl-querystd.patch
Description: Binary data
On Thu, 2009-10-22 at 15:52 +0200, Jiri Pirko wrote:
> This helpers should be used by network drivers to access to netdev
> multicast lists.
[...]
> +static inline void netdev_mc_walk(struct net_device *dev,
> + void (*func)(void *, unsigned char *),
> +
Thu, Oct 22, 2009 at 04:18:32PM CEST, bhutchi...@solarflare.com wrote:
>On Thu, 2009-10-22 at 15:52 +0200, Jiri Pirko wrote:
>> This helpers should be used by network drivers to access to netdev
>> multicast lists.
>[...]
>> +static inline void netdev_mc_walk(struct net_device *dev,
>> +
On Thu, 22 Oct 2009, [UTF-8] Ozan ÃaÄlayan wrote:
> Here's the outputs from /sys/kernel/debug/usb/ehci:
>
> periodic:
>
> size = 1024
>1: qh1024-0001/f6ffe280 (h2 ep2 [1/0] q0 p8)
There's something odd about this. I'd like to see this file again,
after the patch below h
Signed-off-by: Jiri Pirko
---
drivers/media/dvb/dvb-core/dvb_net.c | 22 +++---
1 files changed, 7 insertions(+), 15 deletions(-)
diff --git a/drivers/media/dvb/dvb-core/dvb_net.c
b/drivers/media/dvb/dvb-core/dvb_net.c
index 8c9ae0a..eb50fb0 100644
--- a/drivers/media/dvb/dvb-
wrong subject... reposting...
Thu, Oct 22, 2009 at 03:54:47PM CEST, jpi...@redhat.com wrote:
>Signed-off-by: Jiri Pirko
>---
> drivers/media/dvb/dvb-core/dvb_net.c | 22 +++---
> 1 files changed, 7 insertions(+), 15 deletions(-)
>
>diff --git a/drivers/media/dvb/dvb-core/dvb_net.
Signed-off-by: Jiri Pirko
---
drivers/media/dvb/dvb-core/dvb_net.c | 22 +++---
1 files changed, 7 insertions(+), 15 deletions(-)
diff --git a/drivers/media/dvb/dvb-core/dvb_net.c
b/drivers/media/dvb/dvb-core/dvb_net.c
index 8c9ae0a..eb50fb0 100644
--- a/drivers/media/dvb/dvb-
Signed-off-by: Jiri Pirko
---
drivers/net/e1000e/netdev.c | 34 +++---
1 files changed, 19 insertions(+), 15 deletions(-)
diff --git a/drivers/net/e1000e/netdev.c b/drivers/net/e1000e/netdev.c
index 3769248..97cd106 100644
--- a/drivers/net/e1000e/netdev.c
+++ b/dri
Signed-off-by: Jiri Pirko
---
drivers/net/8139too.c | 24 ++--
1 files changed, 14 insertions(+), 10 deletions(-)
diff --git a/drivers/net/8139too.c b/drivers/net/8139too.c
index 7e333f7..f0c3670 100644
--- a/drivers/net/8139too.c
+++ b/drivers/net/8139too.c
@@ -2501,6 +250
This helpers should be used by network drivers to access to netdev
multicast lists.
Signed-off-by: Jiri Pirko
---
include/linux/netdevice.h | 22 ++
1 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
index 8
In a struct net_device, multicast addresses are stored using a self-made linked
list. To convert this to list_head list there would be needed to do the change
in all (literally all) network device drivers at once.
To solve this situation and also to make device drivers' code prettier I'm
introduci
Hello!
I've got a WinTV NOVA T Stick, working flawlessly on buth windows and
linux but as soon as I connect an external HDD, I start getting a
corrupted image on linux but not on windows. What could be done to fix
this issue?
I use xine to watch the channels on linux and ProgDVB on windows.
cya!
Alan Stern wrote On 22-10-2009 04:36:
> On Thu, 22 Oct 2009, Laurent Pinchart wrote:
>
Here's the outputs from /sys/kernel/debug/usb/ehci:
periodic:
size = 1024
1: qh1024-0001/f6ffe280 (h2 ep2 [1/0] q0 p8)
registers:
bus pci, device :00:1d.7
EHCI Host
31 matches
Mail list logo