Re: small regression in mediatree/for_v3.7-3 - media_build
--- On Sat, 3/11/12, VDR User user@gmail.com wrote: On Tue, Aug 14, 2012 at 4:51 PM, Antti Palosaari cr...@iki.fi wrote: There seems to be a small regression on mediatree/for_v3.7-3 - dmesg/klog get flooded with these: [201145.140260] dvb_frontend_poll: 15 callbacks suppressed [201145.586405] usb_urb_complete: 88 callbacks suppressed [201150.587308] usb_urb_complete: 3456 callbacks suppressed [201468.630197] usb_urb_complete: 3315 callbacks suppressed [201473.632978] usb_urb_complete: 3529 callbacks suppressed [201478.635400] usb_urb_complete: 3574 callbacks suppressed It seems to be every 5 seconds, but I think that's just klog skipping repeats and collapsing duplicate entries. This does not happen the last time I tried playing with the TV stick :-). That's because you has dynamic debugs enabled! modprobe dvb_core; echo -n 'module dvb_core +p' /sys/kernel/debug/dynamic_debug/control modprobe dvb_usbv2; echo -n 'module dvb_usbv2 +p' /sys/kernel/debug/dynamic_debug/control If you don't add dvb_core and dvb_usbv2 modules to /sys/kernel/debug/dynamic_debug/control you will not see those. I'm getting massive amounts of dvb_frontend_poll: 20 callbacks suppressed messages in dmesg also and I definitely did not put dvb_core or anything else in /sys/kernel/debug/dynamic_debug/control. For that matter I don't even have a /sys/kernel/debug/dynamic_debug/control file. I have added ratelimited version for those few debugs that are flooded normally. This suppressed is coming from ratelimit - it does not print all those similar debugs. I'm using kernel 3.6.3 with media_build from Oct. 21, 2012. How I can disable those messages? I'd rather not see hundreds, possibly thousands or millions of those messages. :) okay, if you had followed the threads further down, you would probably see that I patched the host side copy of device.h, i.e: /lib/modules/`uname -r `/build/include/linux/device.h to get around this, since media_build does not use a full dev kernel tree, but uses the host-side copy of the kernel headers. So you need to apply the patch (attached) to that. i.e. cd /lib/modules/`uname -r `/build/include/linux/ patch -p3 /tmp/patch Mind you this messes up your kernel-dev headers. In my case, because that file is part of the fedora distro kernel-devel package, and as soon as I get a new kernel the whole thing is thrown away, so I don't care. But if you compile your own kernel (and hence have your own kernel-devel headers which you want to keep in clean state), you might want to take note about this. Hope this helps. patch Description: Binary data
Re: [v3 1/1] driver-core: Shut up dev_dbg_reatelimited() without DEBUG
--- On Fri, 24/8/12, Hiroshi Doyu hd...@nvidia.com wrote:
From: Hiroshi Doyu hd...@nvidia.com
Subject: [v3 1/1] driver-core: Shut up dev_dbg_reatelimited() without DEBUG
To: gre...@linuxfoundation.org gre...@linuxfoundation.org
Cc: linux-ker...@vger.kernel.org linux-ker...@vger.kernel.org,
ht...@users.sourceforge.net ht...@users.sourceforge.net,
linux-media@vger.kernel.org linux-media@vger.kernel.org,
j...@perches.com j...@perches.com, linux-te...@vger.kernel.org
linux-te...@vger.kernel.org, cr...@iki.fi cr...@iki.fi
Date: Friday, 24 August, 2012, 5:35
dev_dbg_reatelimited() without DEBUG
printed 217078 callbacks
suppressed. This shouldn't print anything without DEBUG.
With CONFIG_DYNAMIC_DEBUG, the print should be configured as
expected.
Signed-off-by: Hiroshi Doyu hd...@nvidia.com
Reported-by: Hin-Tak Leung ht...@users.sourceforge.net
Tested-by: Antti Palosaari cr...@iki.fi
Acked-by: Hin-Tak Leung ht...@users.sourceforge.net
Tested-by: Hin-Tak Leung ht...@users.sourceforge.net
Went ahead and patched my 2.5.x distro kernel-devel package header, and it
works as expected. Apologies about the red-herring with media_build (for those
who are not familar with it, = back-port wrapper package for building new DVB
modules against older kernels).
The distro kernel-devel headers is per installed distro kernel so will be
replaced in a week or two... no permanent demage done :-).
---
include/linux/device.h | 62
+--
1 files changed, 38 insertions(+), 24 deletions(-)
diff --git a/include/linux/device.h
b/include/linux/device.h
index 9648331..bb6ffcb 100644
--- a/include/linux/device.h
+++ b/include/linux/device.h
@@ -932,6 +932,32 @@ int _dev_info(const struct device *dev,
const char *fmt, ...)
#endif
+/*
+ * Stupid hackaround for existing uses of non-printk uses
dev_info
+ *
+ * Note that the definition of dev_info below is actually
_dev_info
+ * and a macro is used to avoid redefining dev_info
+ */
+
+#define dev_info(dev, fmt, arg...) _dev_info(dev, fmt,
##arg)
+
+#if defined(CONFIG_DYNAMIC_DEBUG)
+#define dev_dbg(dev, format, ...)
\
+do {
\
+ dynamic_dev_dbg(dev, format,
##__VA_ARGS__); \
+} while (0)
+#elif defined(DEBUG)
+#define dev_dbg(dev, format, arg...)
\
+ dev_printk(KERN_DEBUG, dev, format,
##arg)
+#else
+#define dev_dbg(dev, format, arg...)
\
+({
\
+ if (0)
\
+
dev_printk(KERN_DEBUG, dev, format,
##arg); \
+ 0;
\
+})
+#endif
+
#define dev_level_ratelimited(dev_level, dev, fmt,
...)
\
do {
\
static
DEFINE_RATELIMIT_STATE(_rs,
\
@@ -955,33 +981,21 @@ do {
\
dev_level_ratelimited(dev_notice, dev,
fmt, ##__VA_ARGS__)
#define dev_info_ratelimited(dev, fmt,
...)
\
dev_level_ratelimited(dev_info, dev,
fmt, ##__VA_ARGS__)
+#if defined(CONFIG_DYNAMIC_DEBUG) || defined(DEBUG)
#define dev_dbg_ratelimited(dev, fmt,
...)
\
- dev_level_ratelimited(dev_dbg, dev, fmt,
##__VA_ARGS__)
-
-/*
- * Stupid hackaround for existing uses of non-printk uses
dev_info
- *
- * Note that the definition of dev_info below is actually
_dev_info
- * and a macro is used to avoid redefining dev_info
- */
-
-#define dev_info(dev, fmt, arg...) _dev_info(dev, fmt,
##arg)
-
-#if defined(CONFIG_DYNAMIC_DEBUG)
-#define dev_dbg(dev, format, ...)
\
-do {
\
- dynamic_dev_dbg(dev, format,
##__VA_ARGS__); \
+do {
\
+ static
DEFINE_RATELIMIT_STATE(_rs,
\
+
DEFAULT_RATELIMIT_INTERVAL, \
+
DEFAULT_RATELIMIT_BURST);
\
+
DEFINE_DYNAMIC_DEBUG_METADATA(descriptor,
fmt);
\
+ if (unlikely(descriptor.flags
_DPRINTK_FLAGS_PRINT) \
+
__ratelimit(_rs))
\
+
__dynamic_pr_debug(descriptor,
pr_fmt(fmt), \
+
##__VA_ARGS__);
\
} while (0)
-#elif defined(DEBUG)
-#define dev_dbg(dev, format, arg...)
\
- dev_printk(KERN_DEBUG, dev, format,
##arg)
#else
-#define dev_dbg(dev, format, arg...)
\
-({
\
- if (0)
\
-
dev_printk(KERN_DEBUG, dev, format,
##arg); \
- 0;
\
-})
+#define dev_dbg_ratelimited(dev, fmt,
...)
\
+ no_printk(KERN_DEBUG pr_fmt(fmt),
##__VA_ARGS__)
#endif
#ifdef VERBOSE_DEBUG
--
1.7.5.4
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord
Re: [PATCH 1/1] driver-core: Shut up dev_dbg_reatelimited() without DEBUG
--- On Wed, 22/8/12, Antti Palosaari cr...@iki.fi wrote:
On 08/22/2012 04:57 PM, Hin-Tak Leung
wrote:
Antti Palosaari wrote:
Hello Hiroshi,
On 08/21/2012 10:02 AM, Hiroshi Doyu wrote:
Antti Palosaari cr...@iki.fi
wrote @ Mon, 20 Aug 2012 23:29:34 +0200:
On 08/20/2012 02:14 PM, Hiroshi Doyu
wrote:
Hi Antti,
Antti Palosaari cr...@iki.fi
wrote @ Sat, 18 Aug 2012 02:11:56
+0200:
On 08/17/2012 09:04 AM, Hiroshi
Doyu wrote:
dev_dbg_reatelimited() without
DEBUG printed 217078 callbacks
suppressed. This shouldn't
print anything without DEBUG.
Signed-off-by: Hiroshi Doyu
hd...@nvidia.com
Reported-by: Antti Palosaari
cr...@iki.fi
---
include/linux/device.h | 6
+-
1 files
changed, 5 insertions(+), 1 deletions(-)
diff --git
a/include/linux/device.h b/include/linux/device.h
index eb945e1..d4dc26e 100644
--- a/include/linux/device.h
+++ b/include/linux/device.h
@@ -962,9 +962,13 @@ do {
\
dev_level_ratelimited(dev_notice, dev,
fmt, ##__VA_ARGS__)
#define
dev_info_ratelimited(dev, fmt, ...)
\
dev_level_ratelimited(dev_info, dev, fmt,
##__VA_ARGS__)
+#if defined(DEBUG)
#define
dev_dbg_ratelimited(dev, fmt, ...)
\
dev_level_ratelimited(dev_dbg, dev, fmt,
##__VA_ARGS__)
-
+#else
+#define
dev_dbg_ratelimited(dev, fmt, ...)
\
+
no_printk(KERN_DEBUG pr_fmt(fmt), ##__VA_ARGS__)
+#endif
/*
* Stupid
hackaround for existing uses of non-printk uses
dev_info
*
NACK. I don't think that's correct
behavior. After that patch it
kills
all output of
dev_dbg_ratelimited(). If I use dynamic debugs and
order
debugs, I expect to see debugs as
earlier.
You are right. I attached the update
patch, just moving *_ratelimited
functions after dev_dbg() definitions.
With DEBUG defined/undefined in your
test.ko, it works fine. With
CONFIG_DYNAMIC_DEBUG, it works with
+p, but with -p, still
..callbacks suppressed is printed.
I am using dynamic debugs and behavior is
now just same as it was when
reported that bug. OK, likely for static
debug it is now correct.
The following patch can also refrain
..callbacks suppressed with
-p. I think that it's ok for all cases.
From
b4c6aa9160f03b61ed17975c73db36c983a48927 Mon Sep 17 00:00:00
2001
From: Hiroshi Doyu hd...@nvidia.com
Date: Mon, 20 Aug 2012 13:49:19 +0300
Subject: [v3 1/1] driver-core: Shut up
dev_dbg_reatelimited() without
DEBUG
dev_dbg_reatelimited() without DEBUG printed
217078 callbacks
suppressed. This shouldn't print anything
without DEBUG.
With CONFIG_DYNAMIC_DEBUG, the print should be
configured as expected.
Signed-off-by: Hiroshi Doyu hd...@nvidia.com
Reported-by: Antti Palosaari cr...@iki.fi
---
include/linux/device.h
| 62
+--
1 files changed, 38
insertions(+), 24 deletions(-)
diff --git a/include/linux/device.h
b/include/linux/device.h
index 9648331..bb6ffcb 100644
--- a/include/linux/device.h
+++ b/include/linux/device.h
@@ -932,6 +932,32 @@ int _dev_info(const struct
device *dev, const
char *fmt,
...)
#endif
+/*
+ * Stupid hackaround for existing uses of
non-printk uses dev_info
+ *
+ * Note that the definition of dev_info below
is actually _dev_info
+ * and a macro is used to avoid redefining
dev_info
+ */
+
+#define dev_info(dev, fmt, arg...)
_dev_info(dev, fmt, ##arg)
+
+#if defined(CONFIG_DYNAMIC_DEBUG)
+#define dev_dbg(dev, format, ...)
\
+do {
\
+ dynamic_dev_dbg(dev, format,
##__VA_ARGS__); \
+} while (0)
+#elif defined(DEBUG)
+#define dev_dbg(dev, format, arg...)
\
+ dev_printk(KERN_DEBUG, dev,
format, ##arg)
+#else
+#define dev_dbg(dev, format, arg...)
\
+({
\
+ if (0)
\
+
dev_printk(KERN_DEBUG, dev, format, ##arg); \
+ 0;
\
+})
+#endif
+
#define
dev_level_ratelimited(dev_level, dev, fmt, ...)
\
do {
\
static
DEFINE_RATELIMIT_STATE(_rs,
\
@@ -955,33 +981,21 @@ do {
\
dev_level_ratelimited(dev_notice, dev,
fmt, ##__VA_ARGS__)
#define
dev_info_ratelimited(dev, fmt, ...)
\
dev_level_ratelimited(dev_info, dev, fmt,
##__VA_ARGS__)
+#if defined(CONFIG_DYNAMIC_DEBUG) ||
defined(DEBUG)
#define
dev_dbg_ratelimited(dev, fmt, ...)
\
- dev_level_ratelimited(dev_dbg,
dev, fmt, ##__VA_ARGS__)
-
-/*
- * Stupid hackaround for existing uses of
non-printk uses dev_info
- *
- * Note that the definition of dev_info below
is actually _dev_info
Re: [PATCH 1/1] driver-core: Shut up dev_dbg_reatelimited() without DEBUG
,\
+ DEFAULT_RATELIMIT_INTERVAL,\
+ DEFAULT_RATELIMIT_BURST);\
+DEFINE_DYNAMIC_DEBUG_METADATA(descriptor, fmt);\
+if (unlikely(descriptor.flags _DPRINTK_FLAGS_PRINT) \
+__ratelimit(_rs))\
+__dynamic_pr_debug(descriptor, pr_fmt(fmt),\
+ ##__VA_ARGS__);\
} while (0)
-#elif defined(DEBUG)
-#define dev_dbg(dev, format, arg...)\
-dev_printk(KERN_DEBUG, dev, format, ##arg)
#else
-#define dev_dbg(dev, format, arg...)\
-({\
-if (0)\
-dev_printk(KERN_DEBUG, dev, format, ##arg);\
-0;\
-})
+#define dev_dbg_ratelimited(dev, fmt, ...)\
+no_printk(KERN_DEBUG pr_fmt(fmt), ##__VA_ARGS__)
#endif
#ifdef VERBOSE_DEBUG
That seems to work correctly now. I tested it using dynamic debugs. It was
Hin-Tak who originally reported that bug for me after I added few ratelimited
debugs for DVB stack. Thank you!
Reported-by: Hin-Tak Leung ht...@users.sourceforge.net
Tested-by: Antti Palosaari cr...@iki.fi
regards
Antti
This is with mediatree/for_v3.7-8 , playing DVB-T video with mplayer.
echo 'file ...media_build/v4l/usb_urb.c +p'
/sys/kernel/debug/dynamic_debug/control
With +p
[137749.698202] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137749.699449] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137749.700825] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137754.690862] usb_urb_complete: 3570 callbacks suppressed
[137754.690888] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137754.692489] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137754.693745] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137754.694882] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137754.696240] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137754.697483] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137754.699002] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137754.700884] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137754.701613] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137754.702986] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137759.695906] usb_urb_complete: 3595 callbacks suppressed
[137759.695934] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137759.697788] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
[137759.698772] usb 1-3: usb_urb_complete: bulk urb completed status=0
length=4096/4096 pack_num=0 errors=0
with -p
[137814.730303] usb_urb_complete: 3555 callbacks suppressed
[137819.740698] usb_urb_complete: 3519 callbacks suppressed
[137824.744857] usb_urb_complete: 3443 callbacks suppressed
[137829.746023] usb_urb_complete: 3345 callbacks suppressed
[137834.749931] usb_urb_complete: 3558 callbacks suppressed
[137839.753102] usb_urb_complete: 3465 callbacks suppressed
[137844.755521] usb_urb_complete: 3438 callbacks suppressed
--
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
Re: noisy dev_dbg_ratelimited()
--- On Thu, 16/8/12, Antti Palosaari cr...@iki.fi wrote:
Hello Hiroshi
On 08/16/2012 10:12 AM, Hiroshi Doyu wrote:
Hi Antti,
Antti Palosaari cr...@iki.fi
wrote @ Thu, 16 Aug 2012 03:11:56 +0200:
Hello Hiroshi,
I see you have added dev_dbg_ratelimited()
recently, commit
6ca045930338485a8cdef117e74372aa1678009d .
However it seems to be noisy as expected similar
behavior than normal
dev_dbg() without a ratelimit.
I looked ratelimit.c and there is:
printk(KERN_WARNING %s: %d callbacks
suppressed\n, func, rs-missed);
What it looks my eyes it will print those
callbacks suppressed always
because KERN_WARNING.
Right. Can the following fix the problem?
No. That silences dev_dbg_reatelimited() totally.
dev_dbg() works as expected printing all the debugs. But
when I change
it to dev_dbg_reatelimited() all printings are silenced.
That's probably correct - the patch looks a bit strange... I did not try the
patch, but had a quick look at the file and noted that in
include/linux/device.h, info (and possibly another level) are treated
specially... just thought I should mention this.
From 905b1dedb6c64bc46a70f6d203ef98c23fccb107 Mon
Sep 17 00:00:00 2001
From: Hiroshi Doyu hd...@nvidia.com
Date: Thu, 16 Aug 2012 10:02:11 +0300
Subject: [PATCH 1/1] driver-core: Shut up
dev_dbg_reatelimited() without
DEBUG
dev_dbg_reatelimited() without DEBUG printed 217078
callbacks
suppressed. This shouldn't print anything without
DEBUG.
Signed-off-by: Hiroshi Doyu hd...@nvidia.com
Reported-by: Antti Palosaari cr...@iki.fi
---
include/linux/device.h |
6 +-
1 files changed, 5 insertions(+), 1
deletions(-)
diff --git a/include/linux/device.h
b/include/linux/device.h
index eb945e1..d4dc26e 100644
--- a/include/linux/device.h
+++ b/include/linux/device.h
@@ -962,9 +962,13 @@ do {
\
dev_level_ratelimited(dev_notice, dev, fmt, ##__VA_ARGS__)
#define dev_info_ratelimited(dev, fmt,
...)
\
dev_level_ratelimited(dev_info, dev, fmt, ##__VA_ARGS__)
+#if defined(DEBUG)
#define dev_dbg_ratelimited(dev, fmt,
...)
\
dev_level_ratelimited(dev_dbg, dev, fmt, ##__VA_ARGS__)
-
+#else
+#define dev_dbg_ratelimited(dev, fmt,
...)
\
+ no_printk(KERN_DEBUG pr_fmt(fmt),
##__VA_ARGS__)
+#endif
/*
* Stupid hackaround for existing uses of
non-printk uses dev_info
*
regards
Antti
--
http://palosaari.fi/
--
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
small regression in mediatree/for_v3.7-3 - media_build
There seems to be a small regression on mediatree/for_v3.7-3 - dmesg/klog get flooded with these: [201145.140260] dvb_frontend_poll: 15 callbacks suppressed [201145.586405] usb_urb_complete: 88 callbacks suppressed [201150.587308] usb_urb_complete: 3456 callbacks suppressed [201468.630197] usb_urb_complete: 3315 callbacks suppressed [201473.632978] usb_urb_complete: 3529 callbacks suppressed [201478.635400] usb_urb_complete: 3574 callbacks suppressed It seems to be every 5 seconds, but I think that's just klog skipping repeats and collapsing duplicate entries. This does not happen the last time I tried playing with the TV stick :-). -- 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
Re: small regression in mediatree/for_v3.7-3 - media_build
--- On Wed, 15/8/12, Antti Palosaari cr...@iki.fi wrote: On 08/15/2012 02:39 AM, Hin-Tak Leung wrote: There seems to be a small regression on mediatree/for_v3.7-3 - dmesg/klog get flooded with these: [201145.140260] dvb_frontend_poll: 15 callbacks suppressed [201145.586405] usb_urb_complete: 88 callbacks suppressed [201150.587308] usb_urb_complete: 3456 callbacks suppressed [201468.630197] usb_urb_complete: 3315 callbacks suppressed [201473.632978] usb_urb_complete: 3529 callbacks suppressed [201478.635400] usb_urb_complete: 3574 callbacks suppressed It seems to be every 5 seconds, but I think that's just klog skipping repeats and collapsing duplicate entries. This does not happen the last time I tried playing with the TV stick :-). That's because you has dynamic debugs enabled! modprobe dvb_core; echo -n 'module dvb_core +p' /sys/kernel/debug/dynamic_debug/control modprobe dvb_usbv2; echo -n 'module dvb_usbv2 +p' /sys/kernel/debug/dynamic_debug/control If you don't add dvb_core and dvb_usbv2 modules to /sys/kernel/debug/dynamic_debug/control you will not see those. I have added ratelimited version for those few debugs that are flooded normally. This suppressed is coming from ratelimit - it does not print all those similar debugs. I did not enable it - it is as shipped :-). # grep 'CONFIG_DYNAMIC' /boot/config* /boot/config-3.4.6-2.fc17.x86_64:CONFIG_DYNAMIC_FTRACE=y /boot/config-3.4.6-2.fc17.x86_64:CONFIG_DYNAMIC_DEBUG=y /boot/config-3.5.0-2.fc17.x86_64:CONFIG_DYNAMIC_FTRACE=y /boot/config-3.5.0-2.fc17.x86_64:CONFIG_DYNAMIC_DEBUG=y /boot/config-3.5.1-1.fc17.x86_64:CONFIG_DYNAMIC_FTRACE=y /boot/config-3.5.1-1.fc17.x86_64:CONFIG_DYNAMIC_DEBUG=y Now I wonder why I didn't have those usb_urb_complete messages before? The last time I played with mediatree was with 3.4.4-5.fc17.x86_64, and with the mediatree2/dvb_core branch - and I did not have these then. -- 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
Re: patches to media_build, and a few other things
--- On Tue, 17/7/12, Antti Palosaari cr...@iki.fi wrote: snipped The last one, something for Antti to figure out: - I found that that part of backports/api_version.patch, which changes LINUX_VERSION_CODE to V4L2_VERSION in drivers/media/video/v4l2-ioctl.c, is relocated from line 930-ish in http://linux/linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2 to line 590-ish in Antti's dvb_core branch. So there are commits which are in linux-media-LATEST.tar.bz2 and not in Antti's branch or vice versa. (so that's any reason who one wants to know how linux-media-LATEST.tar.bz2 is made). I used Linus 3.5 development tree as a base and rebased it continuously to latest rc. Current media_build.git seems to download some older files. I could guess it is tar'ed from Kernel 3.4 /drivers/media/ Patch which likely breaks backports/api_version.patch is that: http://www.mail-archive.com/linuxtv-commits@linuxtv.org/msg13388.html No, it is not that. the diff should look like it deletes a chunk of lines around 930 and adds a similar chunk around line 590, spanning a few lines which includes LINUX_VERSION_CODE/V4L2_VERSION . There shouldn't be any need for guess work - the regular tar ball snapshot is set up by some person, so there should be an authoritative answer... By the way, I was doing a bit of travelling in the last few days - and got fairly good reception with just the small 5-in aerial in two places; on the 5th floor of a hotel in Brighton (a coastal city in south UK) and the 4th floor by a correct-facing window (same building one floor below interior was crap) local. So it seems that the high you go in UK (or in SE UK), the better. That probably explains why it is so bad in my place - mid-way between two transmitters, and also on the ground floor just outside floodable distance from the local river (i.e. as low in altitude as one can get...). -- 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
patches to media_build, and a few other things
I have a couple of patches to my local media_build repo, which do these: - a new option --as-is to the build script. It basically suppresses any git pull/rebase to both media_build and the ./media subdirectory (if used in combination with --main-git). In combination to --main-git, you are left on your own and be wholy responsible about what is inside ./media - I use that to check Antti's work (which is on a branch), and also since I have some interrim patches to media_build itself, I would prefer I can tell it not to pull/merge . - a small change to v4l/Makefile , to install under /lib/modules/$(KERNELRELEASE)/updates/... - recent fedora seems to have a modprobe preference to load from ../updates/... (or at least, that's the case of having installed compat-wireless at some stage - one might want to steal some code from that?), when more than one kernel module of the same name exists. This is so as not to trash distro-shipped modules (and also if one cleans out .../updates/... and runs depmod -a, one is back to distro as shipped behavior). Also trashing distro-shipped modules have the side-effect of making drpm not to work and whole kernel packages are downloaded in the next yum upgrade. I also have a suggestion to make: - How http://linux/linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2 is generated, probably should be documented. Over the weekend I was playing with one with timestamp Jul 7, and it is quite broken with firstly header files not in the right place (linux/v4l2-common.h instead of media/v4l2-common.h), and also the following: media_build/v4l/../linux/include/media/v4l2-dev.h:127:2: error: unknown type name 'v4l2_std_id' media_build/v4l/../linux/include/media/v4l2-dev.h:128:2: error: unknown type name 'v4l2_std_id' media_build/v4l/../linux/include/media/v4l2-dev.h:135:32: error: 'BASE_VIDIOC_PRIVATE' undeclared here (not in a function) I see that the Jul 16 version has both of these issues fixed... but I am not against having a look myself if it is urgent enough for me (considered that it was broken for 9 days). - a few of the firmware files are newer/different than distro-shipped... I am less bothered by it trashing distro-shipped packaged files as the linux-firmware package is rarely upgraded. But maybe one can try pushing some of that upstream? The last one, something for Antti to figure out: - I found that that part of backports/api_version.patch, which changes LINUX_VERSION_CODE to V4L2_VERSION in drivers/media/video/v4l2-ioctl.c, is relocated from line 930-ish in http://linux/linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2 to line 590-ish in Antti's dvb_core branch. So there are commits which are in linux-media-LATEST.tar.bz2 and not in Antti's branch or vice versa. (so that's any reason who one wants to know how linux-media-LATEST.tar.bz2 is made). -- 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
Re: unload/unplugging (Re: success! (Re: media_build and Terratec Cinergy T Black.))
--- On Sat, 7/7/12, Antti Palosaari cr...@iki.fi wrote: snipped I also have quite a few : [224773.229293] DVB: adapter 0 frontend 0 frequency 2 out of range (17400..86200) This seems to come from running w_scan. yes, those warnings are coming when application request illegal frequency. Setting frequency as a 2 Hz is something totally wrong, wild guess, it is some other value set accidentally as frequency. I am thinking either w_scan is doing something it should not, in which case we should inform its author to have this looked at, or the message does not need to be there? The kernel seems happy while having the device physically pulled out. But the kernel module does not like to be unloaded (modprobe -r) while mplayer is running, so we need to fix that. Yep, seems to refuse unload. I suspect it is refused since there is ongoing USB transmission as it streams video. But should we allow that? And is removing open device nodes OK as applications holds those? I am thinking about suspend/resume, the poorman's way, which is to unload/reload. One interesting thing to try would be to pause but not quit the application - either just press pause, or say, 'gdb mplayerbinary pid', and see if 'modprobe -r' can be made to work under that sort of condition, if it isn't already. -- 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
channel scanning (Re: success! (Re: media_build and Terratec Cinergy T Black.))
--- On Sat, 7/7/12, Antti Palosaari cr...@iki.fi wrote:
snipped
scandvb still does not work at all, nor those sample
config files under
/usr/share/doc/dvb-apps-1.1.2/channels-conf/dvb-t/* , or use
those (tried about 6 different transmitter config various
distance away). It is also true that I have poor reception:
all the BBC* channels seems to work okay - about 18 channels
- but none of the non-BBC stations. Also they are not there
on a 2nd scan, so I guess they are weaker.
UK is a little bit special case as it uses different channel
raster. I
just looked and there seems to be auto-With167kHzOffsets
which could
be used. It scans all the possible channels using auto
parameter detection.
Those files (dvb-t/uk-{regions}) are not in the dvb-apps hg repo, so I don't
know where they came from, but considered that they don't work for me at all
(and w_scan does find some), their contents are either wrong or outdated.
The fedora package changelog possibly says tuning files are kept elsewhere and
were last updated over 2 years ago - I know it is probably cliche to assume
every *.fi person knows every other *.fi person, but do you? :-)
* Sat Jun 05 2010 Ville Skyttä ville.sky...@iki.fi - 1.1.1-22
- Patch to fix dvbnet -h crash (#597604).
- Update tuning files to 20100605.
So obviously there are a lot of rough edges. I also
think it is a bit stupid for w_scan not to offer writing
*all* the formats, since all the information should be there
after a scan. It takes about 8 minutes to do a full scan. It
would be more logical to generate all the channels.conf
formats on one scan, and let the user throw away the ones he
does not need, if it takes that long to do a full scan.
Yes there is. There is no many desktop applications
supporting DVB and
even less applications having own channels scanner.
With a full scan taking 8 minutes (and quick assisted scan based on presets
not working at all), channel-scanning can't really be modularized and built
into an application. Actually even w_scan needs assistance about which
*country*.
Also a typical user might like to try a few different applications. I use
mplayer-derivatives - mplayer, gmplayer, gnome-mplayer, dragonplayer - mostly
because of its widest/earliest codec support, but I am not against using
another if it offers more DVB-centric user-interface. I really think w_scan
should by default write all variants of channels.conf formats, or a master-form
convertable to others, just to save the 8 minutes of re-scan. (being able to
convert quickly, or for application to standardize would be nice, but seeing as
the formats have different info, that idea does not seem likely).
--
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
Re: unload/unplugging (Re: success! (Re: media_build and Terratec Cinergy T Black.))
--- On Sat, 7/7/12, Antti Palosaari cr...@iki.fi wrote: snipped I am thinking either w_scan is doing something it should not, in which case we should inform its author to have this looked at, or the message does not need to be there? As scandvb and all the other applications are able to set desired parameters without that error it must be w_scan issue. But scandvb does not work at all in my case (or rather, the bundled tuning files were wrong/out-dated). And personally I don't care whole warning, returning some error code (which is likely -EINVAL) should be enough. It is not error situation in the mean of Kernel or device error - it is just user error as user tries to set unsupported frequency. It is possibly just too much information in klog/dmesg . The kernel seems happy while having the device physically pulled out. But the kernel module does not like to be unloaded (modprobe -r) while mplayer is running, so we need to fix that. Yep, seems to refuse unload. I suspect it is refused since there is ongoing USB transmission as it streams video. But should we allow that? And is removing open device nodes OK as applications holds those? I am thinking about suspend/resume, the poorman's way, which is to unload/reload. One interesting thing to try would be to pause but not quit the application - either just press pause, or say, 'gdb mplayerbinary pid', and see if 'modprobe -r' can be made to work under that sort of condition, if it isn't already. hmm, what is that kind of suspend/resume? Is that different what is now implemented? In the good old days, for drivers which does not suspend/hibernate well, one can add a file /etc/pm/config.d/myfile containing SUSPEND_MODULES=modname to get them unloaded on suspend. Does it work with mplayer/vlc running or pausing? -- 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
media_build and Terratec Cinergy T Black.
Firstly, the downloaded linux-media.tar.bz2 has some simple typos, missing 3
brackets:
(please feel free to add my signed-off though this is trivial).
-
--- linux/drivers/media/video/v4l2-compat-ioctl32.c~2012-07-06
04:45:17.0 +0100
+++ linux/drivers/media/video/v4l2-compat-ioctl32.c 2012-07-06
07:35:54.166512279 +0100
@@ -387,7 +387,7 @@
get_user(kp-index, up-index) ||
get_user(kp-type, up-type) ||
get_user(kp-flags, up-flags) ||
- get_user(kp-memory, up-memory)
+ get_user(kp-memory, up-memory))
return -EFAULT;
if (V4L2_TYPE_IS_OUTPUT(kp-type))
@@ -471,7 +471,7 @@
put_user(kp-index, up-index) ||
put_user(kp-type, up-type) ||
put_user(kp-flags, up-flags) ||
- put_user(kp-memory, up-memory)
+ put_user(kp-memory, up-memory))
return -EFAULT;
if (put_user(kp-bytesused, up-bytesused) ||
@@ -481,7 +481,7 @@
copy_to_user(up-timecode, kp-timecode, sizeof(struct
v4l2_timecode)) ||
put_user(kp-sequence, up-sequence) ||
put_user(kp-reserved2, up-reserved2) ||
- put_user(kp-reserved, up-reserved)
+ put_user(kp-reserved, up-reserved))
return -EFAULT;
if (V4L2_TYPE_IS_MULTIPLANAR(kp-type)) {
A few comments issues:
- don't realy like the build script trying to clone media_tree, etc had
hard-coded remotes - if(0) out'ed the whole git-on-the-fly block inside to make
it use an existing symlink'ed checkout - consider offering something similar?
- $ lsdvb seems to be doing garbage:(fedora 17's)
usb (-1975381336:62 64848224:32767) on PCI Domain:-1965359032 Bus:62
Device:64848416 Function:32767
DEVICE:0 ADAPTER:0 FRONTEND:0 (Realtek RTL2832 (DVB-T))
FE_OFDM Fmin=174MHz Fmax=862MHz
lsdvb on mercury is only marginally better with the PCI zero's, but the other
numbers swapped:
usb (62:-1975379912 32767:-348245472) on PCI Domain:0 Bus:0 Device:0 Function:0
DEVICE:0 ADAPTER:0 FRONTEND:0 (Realtek RTL2832 (DVB-T))
FE_OFDM Fmin=174MHz Fmax=862MHz
- 'scandvb' segfault at the end on its own.
- scandvb /usr/share/dvb/dvb-t/uk-SandyHeath (supposedly where I am) got a
few WARNING: tuning failed!!! and no list.
- 'w_scan -G -c GB'
have a few curious
WARNING: received garbage data: crc = 0xcc93876c; expected crc = 0xb81bb6c4
return a list of 26, with entries like (which seems to be vaguely correct):
BBC
ONE;(null):522000:B8C23D0G32M64T8Y0:T:27500:101=2:102,106=eng:0:0:4173:9018:4173:0:100
So I just put it in ~/.mplayer:channels.conf
Took me a while to figure out that mplayer wants:
mplayer 'dvb://BBC ONE;(null)'
rather than anything else - curious about the ';(null)' part.
Playing dvb://BBC ONE;(null).
dvb_tune Freq: 522000
ERROR IN SETTING DMX_FILTER 9018 for fd 4: ERRNO: 22ERROR, COULDN'T SET CHANNEL
8: Failed to open dvb://BBC ONE;(null).
--
At this point I am lost :-).
--
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
Re: media_build and Terratec Cinergy T Black.
One more comment: blowing away /lib/modules/`uname -r`/kernel/drivers/ seems
drastic?
The compat-wireless people uses some clever tricks to get modprobe to
preferentially load /lib/modules/`uname -r`/updates first. This way you can
just remove that, run 'depmod -a' and go back to stock distro kernel behavior.
Also it might be useful/quicker not to build the whole 500+ kernel modules...
--- On Fri, 6/7/12, Hin-Tak Leung ht...@users.sourceforge.net wrote:
From: Hin-Tak Leung ht...@users.sourceforge.net
Subject: media_build and Terratec Cinergy T Black.
To: Antti Palosaari cr...@iki.fi, mche...@redhat.com
Cc: linux-media@vger.kernel.org
Date: Friday, 6 July, 2012, 11:54
Firstly, the downloaded
linux-media.tar.bz2 has some simple typos, missing 3
brackets:
(please feel free to add my signed-off though this is
trivial).
-
---
linux/drivers/media/video/v4l2-compat-ioctl32.c~
2012-07-06 04:45:17.0 +0100
+++
linux/drivers/media/video/v4l2-compat-ioctl32.c
2012-07-06 07:35:54.166512279 +0100
@@ -387,7 +387,7 @@
get_user(kp-index, up-index) ||
get_user(kp-type,
up-type) ||
get_user(kp-flags, up-flags) ||
-
get_user(kp-memory, up-memory)
+
get_user(kp-memory, up-memory))
return -EFAULT;
if (V4L2_TYPE_IS_OUTPUT(kp-type))
@@ -471,7 +471,7 @@
put_user(kp-index, up-index) ||
put_user(kp-type,
up-type) ||
put_user(kp-flags, up-flags) ||
-
put_user(kp-memory, up-memory)
+
put_user(kp-memory, up-memory))
return -EFAULT;
if (put_user(kp-bytesused,
up-bytesused) ||
@@ -481,7 +481,7 @@
copy_to_user(up-timecode, kp-timecode,
sizeof(struct v4l2_timecode)) ||
put_user(kp-sequence, up-sequence) ||
put_user(kp-reserved2, up-reserved2) ||
-
put_user(kp-reserved, up-reserved)
+
put_user(kp-reserved, up-reserved))
return -EFAULT;
if
(V4L2_TYPE_IS_MULTIPLANAR(kp-type)) {
A few comments issues:
- don't realy like the build script trying to clone
media_tree, etc had hard-coded remotes - if(0) out'ed the
whole git-on-the-fly block inside to make it use an existing
symlink'ed checkout - consider offering something similar?
- $ lsdvb seems to be doing garbage:(fedora 17's)
usb (-1975381336:62 64848224:32767) on PCI
Domain:-1965359032 Bus:62 Device:64848416 Function:32767
DEVICE:0 ADAPTER:0 FRONTEND:0 (Realtek
RTL2832 (DVB-T))
FE_OFDM
Fmin=174MHz Fmax=862MHz
lsdvb on mercury is only marginally better with the PCI
zero's, but the other numbers swapped:
usb (62:-1975379912 32767:-348245472) on PCI Domain:0 Bus:0
Device:0 Function:0
DEVICE:0 ADAPTER:0 FRONTEND:0 (Realtek
RTL2832 (DVB-T))
FE_OFDM
Fmin=174MHz Fmax=862MHz
- 'scandvb' segfault at the end on its own.
- scandvb /usr/share/dvb/dvb-t/uk-SandyHeath (supposedly
where I am) got a few WARNING: tuning
failed!!! and no list.
- 'w_scan -G -c GB'
have a few curious
WARNING: received garbage data: crc = 0xcc93876c; expected
crc = 0xb81bb6c4
return a list of 26, with entries like (which seems to be
vaguely correct):
BBC
ONE;(null):522000:B8C23D0G32M64T8Y0:T:27500:101=2:102,106=eng:0:0:4173:9018:4173:0:100
So I just put it in ~/.mplayer:channels.conf
Took me a while to figure out that mplayer wants:
mplayer 'dvb://BBC ONE;(null)'
rather than anything else - curious about the ';(null)'
part.
Playing dvb://BBC ONE;(null).
dvb_tune Freq: 522000
ERROR IN SETTING DMX_FILTER 9018 for fd 4: ERRNO: 22ERROR,
COULDN'T SET CHANNEL 8: Failed to open dvb://BBC
ONE;(null).
--
At this point I am lost :-).
--
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
Re: media_build and Terratec Cinergy T Black.
--- On Fri, 6/7/12, Antti Palosaari cr...@iki.fi wrote: On 07/06/2012 01:54 PM, Hin-Tak Leung wrote: - $ lsdvb seems to be doing garbage:(fedora 17's) usb (-1975381336:62 64848224:32767) on PCI Domain:-1965359032 Bus:62 Device:64848416 Function:32767 DEVICE:0 ADAPTER:0 FRONTEND:0 (Realtek RTL2832 (DVB-T)) FE_OFDM Fmin=174MHz Fmax=862MHz lsdvb on mercury is only marginally better with the PCI zero's, but the other numbers swapped: usb (62:-1975379912 32767:-348245472) on PCI Domain:0 Bus:0 Device:0 Function:0 DEVICE:0 ADAPTER:0 FRONTEND:0 (Realtek RTL2832 (DVB-T)) FE_OFDM Fmin=174MHz Fmax=862MHz I was aware of that tool but didn't know it lists USB devices too. Someone should fix it working properly for USB devices. The mercury repository is on linuxtv, so presumably one of you can do it :-). It is wierd that (1) those numbers are swapped between fc17's vs upstream, (2) the numbers also change between runs - 'scandvb' segfault at the end on its own. I didn't see that. This is fc17's - it does so in a string function (v*printf) - probably easy to fix if/when I get the debuginfo package, if it isn't fixed upstream already. - scandvb /usr/share/dvb/dvb-t/uk-SandyHeath (supposedly where I am) got a few WARNING: tuning failed!!! and no list. This is where it gets confusing - /usr/share/dvb/dvb-t/* and /usr/share/doc/dvb-apps-1.1.2/channels-conf/dvb-t/* have similiar names, but different content, and no explanation which is which. The latter seems to be in the correct format you wrote below, but does not work. One thing would be nice to do would be write up a description of those formats, and say which is which. - 'w_scan -G -c GB' have a few curious WARNING: received garbage data: crc = 0xcc93876c; expected crc = 0xb81bb6c4 return a list of 26, with entries like (which seems to be vaguely correct): BBC ONE;(null):522000:B8C23D0G32M64T8Y0:T:27500:101=2:102,106=eng:0:0:4173:9018:4173:0:100 w_scan is the only one which seems to be able to scan, but its output format isn't correct. Any ideas about the garbage data message? Both scandvb and w_scan works here, same device used. I suspect your signal is just simply too weak for reception. Small antenna coming with those DVB sticks is not suitable unless you are living very near transmitter. Try to connect it roof antenna. One thing that helps a lot is to attach small bundled antenna to outside window. I was using my satellite dish as antenna, BTW. Nothing with the small antenna. There is both dvbscan and scandvb in Fedora dvb-apps. It is not clear for me why two similar looking tools. Anyhow it is just scandvb which I found working one. I just found a dvbv5-scan on my harddisk (fc17) also, and dvbscan is in locate.db but gone. Apparently one might be 'scan' but too confusing and got its name changed during packaging. So I just put it in ~/.mplayer:channels.conf Took me a while to figure out that mplayer wants: mplayer 'dvb://BBC ONE;(null)' rather than anything else - curious about the ';(null)' part. Playing dvb://BBC ONE;(null). dvb_tune Freq: 522000 ERROR IN SETTING DMX_FILTER 9018 for fd 4: ERRNO: 22ERROR, COULDN'T SET CHANNEL 8: Failed to open dvb://BBC ONE;(null). -- Typical channels.conf entry looks like that: MTV3:71400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:305:561:49 And tuning to that channel using mplayer: mplayer dvb://MTV3 Well that at least clear up something - I tried this form (from /usr/share/doc/dvb-apps-1.1.2/channels-conf/dvb-t/* ) but did not get anything either - the error message seemed worse so I didn't go further. I guess I should try getting w_scan to do this form. However, I prefer VLC. Just open channels.conf to VLC and should show playlist. Totem does not work anymore. at least stream used here in Finland. It went broken when they changed from playbin to playbin2 which is really shame as it is default video player for Gnome desktop. At this point I am lost :-). Not big surprise unfortunately :/ Unfortunately desktop integration is currently poor and most users are coming from the HTPC. There seems to be at least two channels.conf formats (one for mplayer/vlc/gstreamer, one for vdr?), and unfortunately both seems to have the same name conventionally, but different content. I can't find documentation about either, or even examples :-). I am also surprised by the checksum failed message with w_scan, and that it does not change output format with adding options, etc. -- 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
success! (Re: media_build and Terratec Cinergy T Black.)
--- On Fri, 6/7/12, Hin-Tak Leung ht...@users.sourceforge.net wrote: snipped Typical channels.conf entry looks like that: MTV3:71400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:305:561:49 And tuning to that channel using mplayer: mplayer dvb://MTV3 Well that at least clear up something - I tried this form (from /usr/share/doc/dvb-apps-1.1.2/channels-conf/dvb-t/* ) but did not get anything either - the error message seemed worse so I didn't go further. I guess I should try getting w_scan to do this form. snipped There seems to be at least two channels.conf formats (one for mplayer/vlc/gstreamer, one for vdr?), and unfortunately both seems to have the same name conventionally, but different content. I can't find documentation about either, or even examples :-). Apparently it was just me not reading the manual/options properly. There are 3 formats - gstreamer, vdr and mplayer's! I thought it was just vdr vs everything else. It was also confusing that mplayer did not complain about it. scandvb still does not work at all, nor those sample config files under /usr/share/doc/dvb-apps-1.1.2/channels-conf/dvb-t/* , or use those (tried about 6 different transmitter config various distance away). It is also true that I have poor reception: all the BBC* channels seems to work okay - about 18 channels - but none of the non-BBC stations. Also they are not there on a 2nd scan, so I guess they are weaker. So obviously there are a lot of rough edges. I also think it is a bit stupid for w_scan not to offer writing *all* the formats, since all the information should be there after a scan. It takes about 8 minutes to do a full scan. It would be more logical to generate all the channels.conf formats on one scan, and let the user throw away the ones he does not need, if it takes that long to do a full scan. -- 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
unload/unplugging (Re: success! (Re: media_build and Terratec Cinergy T Black.))
BTW, I tried just pulling the USB stick out while mplayer is running. Strangely enough mplayer did not notice it gone and kept going for some 5 to 10 seconds. Probably buffering? The only sign about it is two lines in dmesg (other than the usual usb messages about device being unplug). [227690.953311] rtl2832: i2c rd failed=-19 reg=01 len=1 [227710.818089] usb 1-2: dvb_usbv2: streaming_ctrl() failed=-19 I also have quite a few : [224773.229293] DVB: adapter 0 frontend 0 frequency 2 out of range (17400..86200) This seems to come from running w_scan. The kernel seems happy while having the device physically pulled out. But the kernel module does not like to be unloaded (modprobe -r) while mplayer is running, so we need to fix that. -- 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
Re: DVB core enhancements - comments please?
--- On Tue, 3/7/12, Mauro Carvalho Chehab mche...@redhat.com wrote: snipped That is USB radio based si470x chipset. Well, I don't have any si470x device here. It should be noticed that radio applications in general don't open the alsa devices to get audio, as old devices used to have a cable to wire at the audio adapter. I bet that this device uses snd-usb-audio module for audio. So, you may need to use aplayer/arecord in order to listen, with a syntax similar to: arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | aplay - The -r 32000 is for 32 kHz. Quite possibly - shouldn't /proc/bus/usb/devices (or one of the /proc...usb...devices ) gives some clues about what kind of interface/device-class it is? lsusb probably also... Jul 3 00:12:18 localhost kernel: [27988.288783] usb 5-2: New USB device found, idVendor=10c5, idProduct=819a Jul 3 00:12:18 localhost kernel: [27988.288787] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jul 3 00:12:18 localhost kernel: [27988.288789] usb 5-2: Manufacturer: www.rding.cn The vendor's web site has some sort of linux driver for something else. They might be willing to talk. Jul 3 00:12:18 localhost udevd[409]: specified group 'plugdev' unknown Jul 3 00:12:18 localhost kernel: [27988.310751] radio-si470x 5-2:1.2: DeviceID=0x1242 ChipID=0x060c Jul 3 00:12:18 localhost kernel: [27988.310754] radio-si470x 5-2:1.2: This driver is known to work with firmware version 15, Jul 3 00:12:18 localhost kernel: [27988.310756] radio-si470x 5-2:1.2: but the device has firmware version 12. Jul 3 00:12:18 localhost kernel: [27988.312750] radio-si470x 5-2:1.2: software version 1, hardware version 7 Jul 3 00:12:18 localhost kernel: [27988.312753] radio-si470x 5-2:1.2: This driver is known to work with software version 7, Jul 3 00:12:18 localhost kernel: [27988.312755] radio-si470x 5-2:1.2: but the device has software version 1. The two-stage (I assume) firmware message is a bit confusing... can this be improved? -- 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
Re: GSoC 2012 Linux-Media!
Hi Antti, I promised to put you in touch with some more knowledgeable people, so here they are. Will made a few comments during our discussions (inserted verbatim below - may or may not be relevant)... Please feel free to respond to Mr Cooke and/or write to him and Greg. Hin-Tak Will Cooke wrote: The hacks with USB stick are entirely reliant on the chips inside the stick. In this case, the demod (Realtek RTL2832U)has the ability to pass through to the USB bus raw 8-bit sampled RF called I/Q (http://zone.ni.com/devzone/cda/tut/p/id/4805). Once you have this raw I/Q data you can demodulate the signals and process them in software. So it's possible to build an FM radio, an AM radio, a DAB radio, Ham radio, Packet radio, slow scan TV, basically anything which modulates a sine wave within the frequency range of the tuner inside the DVB stick. Not all DVB tuners are created equal. Some will be limited to n hundred MHz, some have a range as low as 50 or 60 MHz up to a few GHz. Chips that have this functionality AND are built in to DVB USB sticks AND cost less than 20 Dollars are few and far between. So it's pretty rare to find a compatible USB stick, and not every USB stick can pull off this neat trick. There is probably scope to run a project around a single targeted DVB USB stick, but hardware support would be limited. GNU Radio is a good tool to build the remodulators. As an example real world application, how about building one of these sticks in to a laptop and integrating it with the audio stack. Now my laptop comes with a TV tuner, an FM tuner, a DAB tuner, and so on. I hope that helps set the scene a little bit more. Let me know if you need any more help. Cheers, Will Will Cooke wrote: Hi Till! I am familiar with what a USB-DVB stick is, how it works, the inside of a DVB transport stream, and so on, but... I'm in no way an expert, and I'm in no way a developer! Depending on what sort of mentoring you had in mind, I would be happy to get involved. Can you let me know a little more about the project and what kind of input you need from me. Cheers, Will Antti Palosaari wrote: Moikka! As I have mentioned many people already, I have got Google Summer of Code project for the Linux-Media! It means I can do three months full time work starting from the week 21 (21.05.2012). Originally I applied Open firmware for ath9k_htc -project as that was listed but I added own topic for Linux-Media related stuff and it was accepted. It is rather much time I can spend and fix all those problems I have seen during recent years. Schedule is first to fix all DVB USB problems and then move to enhancing DVB CORE / frontend. I planned only general digital television stuff since it is what I know best. But if there is some time I can likely do some other general fixes. Here is short description. http://www.google-melange.com/gsoc/project/google/gsoc2012/crope/10001 I will open another thread just discussing what are the most important things and how those should be fixed correctly. And there is no blog yet, but sometime ago I created LinuxTV page for Google+. Lets use it: https://plus.google.com/u/0/11135056277089175/posts And my mentor is Hin-Tak Leung. regards Antti -- 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
