Re: [PATCH v2 2/2] x86/mm/pat, drivers/media/ivtv: move pat warn and replace WARN() with pr_warn()
* Luis R. Rodriguez wrote: > On Mon, Jul 6, 2015 at 5:44 PM, Luis R. Rodriguez wrote: > > If we really wanted to we could consider arch_phys_wc_add() > > I mean adding a __arch_phys_wc_add() which does not check for pat_enabled(). > > > and > > deal with that this will not check for pat_enabled() and forces MTRR... > > I think Andy Luto won't like that very much though ? I at least don't > > like it since we did all this work to finally leave only 1 piece of > > code with direct MTRR access... Seems a bit sad. Since ipath will > > be removed we'd have only ivtv driver using this API, I am not sure if > > its worth it. > > Since ipath is going away soon we'd just have one driver with the icky > #ifdef code. I'd rather see that and then require semantics / grammer > rules to require ioremap_wc() when used with arch_phys_wc_add(). I don't > think > ivtv is worth to consider breaking the semantics and requirements. Ok, let's keep your original approach with the warning then. Thanks, Ingo -- 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: [PATCH v2 1/2] create SMAF module
A nit only, I'm afraid: a license mismatch.
On ma, 2015-07-06 at 13:40 +0200, Benjamin Gaignard wrote:
> --- /dev/null
> +++ b/drivers/smaf/smaf-core.c
> + * License terms: GNU General Public License (GPL), version 2
> +MODULE_LICENSE("GPL");
The comment at the top of this file states, succinctly, that the license
is GPL v2. And, according to include/linux/module.h, the
MODULE_LICENSE() macro here states that the license is GPL v2 or later.
So I think that either that comment or the ident used in that macro
needs to change.
Ditto for 2/2.
Thanks,
Paul Bolle
--
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
cron job: media_tree daily build: ERRORS
This message is generated daily by a cron job that builds media_tree for the kernels and architectures in the list below. Results of the daily build of media_tree: date: Tue 7 Jul 09:13:31 CEST 2015 git branch: test git hash: 8783b9c50400c6279d7c3b716637b98e83d3c933 gcc version:i686-linux-gcc (GCC) 5.1.0 sparse version: v0.5.0-44-g40791b9 smatch version: 0.4.1-3153-g7d56ab3 host hardware: x86_64 host os:4.0.0-3.slh.1-amd64 linux-git-arm-at91: OK linux-git-arm-davinci: OK linux-git-arm-exynos: OK linux-git-arm-mx: OK linux-git-arm-omap: OK linux-git-arm-omap1: OK linux-git-arm-pxa: OK linux-git-blackfin-bf561: OK linux-git-i686: OK linux-git-m32r: OK linux-git-mips: OK linux-git-powerpc64: OK linux-git-sh: OK linux-git-x86_64: OK linux-2.6.32.27-i686: OK linux-2.6.33.7-i686: OK linux-2.6.34.7-i686: OK linux-2.6.35.9-i686: OK linux-2.6.36.4-i686: OK linux-2.6.37.6-i686: OK linux-2.6.38.8-i686: OK linux-2.6.39.4-i686: OK linux-3.0.60-i686: OK linux-3.1.10-i686: OK linux-3.2.37-i686: OK linux-3.3.8-i686: OK linux-3.4.27-i686: OK linux-3.5.7-i686: OK linux-3.6.11-i686: OK linux-3.7.4-i686: OK linux-3.8-i686: OK linux-3.9.2-i686: OK linux-3.10.1-i686: OK linux-3.11.1-i686: OK linux-3.12.23-i686: OK linux-3.13.11-i686: OK linux-3.14.9-i686: OK linux-3.15.2-i686: OK linux-3.16.7-i686: OK linux-3.17.8-i686: OK linux-3.18.7-i686: OK linux-3.19-i686: OK linux-4.0-i686: OK linux-4.1.1-i686: OK linux-4.2-rc1-i686: OK linux-2.6.32.27-x86_64: OK linux-2.6.33.7-x86_64: OK linux-2.6.34.7-x86_64: OK linux-2.6.35.9-x86_64: OK linux-2.6.36.4-x86_64: OK linux-2.6.37.6-x86_64: OK linux-2.6.38.8-x86_64: OK linux-2.6.39.4-x86_64: OK linux-3.0.60-x86_64: OK linux-3.1.10-x86_64: OK linux-3.2.37-x86_64: OK linux-3.3.8-x86_64: OK linux-3.4.27-x86_64: OK linux-3.5.7-x86_64: OK linux-3.6.11-x86_64: OK linux-3.7.4-x86_64: OK linux-3.8-x86_64: OK linux-3.9.2-x86_64: OK linux-3.10.1-x86_64: OK linux-3.11.1-x86_64: ERRORS linux-3.12.23-x86_64: ERRORS linux-3.13.11-x86_64: ERRORS linux-3.14.9-x86_64: ERRORS linux-3.15.2-x86_64: ERRORS linux-3.16.7-x86_64: ERRORS linux-3.17.8-x86_64: ERRORS linux-3.18.7-x86_64: ERRORS linux-3.19-x86_64: ERRORS linux-4.0-x86_64: ERRORS linux-4.1.1-x86_64: ERRORS linux-4.2-rc1-x86_64: OK apps: OK spec-git: OK sparse: WARNINGS smatch: ERRORS Detailed results are available here: http://www.xs4all.nl/~hverkuil/logs/Tuesday.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Tuesday.tar.bz2 The Media Infrastructure API from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/media.html -- 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_usb_af9015: command failed=1 _ kernel >= 4.1.x
On 06.07.2015 22:17, Jose Alberto Reguero wrote: > I made the patch for the af9035. I have not a af9015 whith mxl5007 and dual > channel. Revert it, if it cause regresions. > > Jose Alberto > Thanks. >From e19560ea038e54dc57be717db55f19d449df63f0 Mon Sep 17 00:00:00 2001 From: poma Date: Tue, 7 Jul 2015 10:26:13 +0200 Subject: [PATCH] Fix for AF9015 DVB-T USB2.0 stick This reverts commitas: - 02f9cf96df57575acea2e6eb4041e9f3ecd32548 "[media] [PATH,2/2] mxl5007 move loop_thru to attach" - fe4860af002a4516dd878f7297b61e186c475b35 "[media] [PATH,1/2] mxl5007 move reset to attach" This is the conclusion after extensive testing, these two commitas produce: mxl5007t_soft_reset: 521: failed! mxl5007t_attach: error -121 on line 907 causing AF9015 DVB-T USB2.0 stick completely unusable. Tested-by: poma --- drivers/media/tuners/mxl5007t.c | 30 +- 1 file changed, 5 insertions(+), 25 deletions(-) diff --git a/drivers/media/tuners/mxl5007t.c b/drivers/media/tuners/mxl5007t.c index f4ae04c..f8c4ba2 100644 --- a/drivers/media/tuners/mxl5007t.c +++ b/drivers/media/tuners/mxl5007t.c @@ -374,6 +374,7 @@ static struct reg_pair_t *mxl5007t_calc_init_regs(struct mxl5007t_state *state, mxl5007t_set_if_freq_bits(state, cfg->if_freq_hz, cfg->invert_if); mxl5007t_set_xtal_freq_bits(state, cfg->xtal_freq_hz); + set_reg_bits(state->tab_init, 0x04, 0x01, cfg->loop_thru_enable); set_reg_bits(state->tab_init, 0x03, 0x08, cfg->clk_out_enable << 3); set_reg_bits(state->tab_init, 0x03, 0x07, cfg->clk_out_amp); @@ -530,6 +531,10 @@ static int mxl5007t_tuner_init(struct mxl5007t_state *state, struct reg_pair_t *init_regs; int ret; + ret = mxl5007t_soft_reset(state); + if (mxl_fail(ret)) + goto fail; + /* calculate initialization reg array */ init_regs = mxl5007t_calc_init_regs(state, mode); @@ -895,32 +900,7 @@ struct dvb_frontend *mxl5007t_attach(struct dvb_frontend *fe, /* existing tuner instance */ break; } - - if (fe->ops.i2c_gate_ctrl) - fe->ops.i2c_gate_ctrl(fe, 1); - - ret = mxl5007t_soft_reset(state); - - if (fe->ops.i2c_gate_ctrl) - fe->ops.i2c_gate_ctrl(fe, 0); - - if (mxl_fail(ret)) - goto fail; - - if (fe->ops.i2c_gate_ctrl) - fe->ops.i2c_gate_ctrl(fe, 1); - - ret = mxl5007t_write_reg(state, 0x04, - state->config->loop_thru_enable); - - if (fe->ops.i2c_gate_ctrl) - fe->ops.i2c_gate_ctrl(fe, 0); - - if (mxl_fail(ret)) - goto fail; - fe->tuner_priv = state; - mutex_unlock(&mxl5007t_list_mutex); memcpy(&fe->ops.tuner_ops, &mxl5007t_tuner_ops, -- 2.4.3 -- 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: [Patch v3 1/1] media: am437x-vpfe: Fix a race condition during release
On Mon, Jun 29, 2015 at 10:18 PM, Benoit Parrot wrote:
> There was a race condition where during cleanup/release operation
> on-going streaming would cause a kernel panic because the hardware
> module was disabled prematurely with IRQ still pending.
>
> Fixes: 417d2e507edc ("[media] media: platform: add VPFE capture driver
> support for AM437X")
> Cc: # v4.0+
> Signed-off-by: Benoit Parrot
Acked-by: Lad, Prabhakar
Cheers,
--Prabhakar Lad
> ---
> Changes since v2:
> - fix the stable commit reference syntax
>
> drivers/media/platform/am437x/am437x-vpfe.c | 11 +--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/platform/am437x/am437x-vpfe.c
> b/drivers/media/platform/am437x/am437x-vpfe.c
> index a30cc2f7e4f1..eb25c43da126 100644
> --- a/drivers/media/platform/am437x/am437x-vpfe.c
> +++ b/drivers/media/platform/am437x/am437x-vpfe.c
> @@ -1185,14 +1185,21 @@ static int vpfe_initialize_device(struct vpfe_device
> *vpfe)
> static int vpfe_release(struct file *file)
> {
> struct vpfe_device *vpfe = video_drvdata(file);
> + bool fh_singular = v4l2_fh_is_singular_file(file);
> int ret;
>
> mutex_lock(&vpfe->lock);
>
> - if (v4l2_fh_is_singular_file(file))
> - vpfe_ccdc_close(&vpfe->ccdc, vpfe->pdev);
> + /* the release helper will cleanup any on-going streaming */
> ret = _vb2_fop_release(file, NULL);
>
> + /*
> +* If this was the last open file.
> +* Then de-initialize hw module.
> +*/
> + if (fh_singular)
> + vpfe_ccdc_close(&vpfe->ccdc, vpfe->pdev);
> +
> mutex_unlock(&vpfe->lock);
>
> return ret;
> --
> 1.8.5.1
>
--
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: [Patch v3 1/1] media: am437x-vpfe: Requested frame size and fmt overwritten by current sensor setting
On Mon, Jun 29, 2015 at 10:19 PM, Benoit Parrot wrote:
> Upon a S_FMT the input/requested frame size and pixel format is
> overwritten by the current sub-device settings.
> Fix this so application can actually set the frame size and format.
>
> Fixes: 417d2e507edc ("[media] media: platform: add VPFE capture driver
> support for AM437X")
> Cc: # v4.0+
> Signed-off-by: Benoit Parrot
Acked-by: Lad, Prabhakar
Cheers,
--Prabhakar Lad
> ---
> Changes since v2:
> - fix the stable commit reference syntax
>
> drivers/media/platform/am437x/am437x-vpfe.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/am437x/am437x-vpfe.c
> b/drivers/media/platform/am437x/am437x-vpfe.c
> index eb25c43da126..0fa62c50f62d 100644
> --- a/drivers/media/platform/am437x/am437x-vpfe.c
> +++ b/drivers/media/platform/am437x/am437x-vpfe.c
> @@ -1584,7 +1584,7 @@ static int vpfe_s_fmt(struct file *file, void *priv,
> return -EBUSY;
> }
>
> - ret = vpfe_try_fmt(file, priv, fmt);
> + ret = vpfe_try_fmt(file, priv, &format);
> if (ret)
> return ret;
>
> --
> 1.8.5.1
>
--
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: PCTV Triplestick and Raspberry Pi B+
On Sun, 5 Jul 2015, Patrick Boettcher wrote: Your Intel platform is 64bit. I don't know the TripleStick nor the SI or the EM28xx-driver but _maybe_ there is a problem with it on 32-bit platforms. A long shot, I know, but you'll never know. That was a very good point. I installed the 32-bit version of the same OS (Debian 8, kernel 3.16.0, i386) and the result was a bit suprising. In 32-bit I couldn't even scan a DVT-T transponder! dvbv5-scan did Lock, but it didn't find any PSI PIDs. So there is for sure a problem with 32-bit platforms. And the DVT-T2 transponders didn't work either. Maybe the Raspberry problem can be a Endianess problem? On Mon, 6 Jul 2015, Andy Furniss wrote: Clutching at straws now, but maybe it's possible that the Pi is electrically more noisy then the intel. The USB lead on the 292e doesn't have a ferrite core - maybe if you have an extension lead that does you could try adding that. That was actually also a good point. I installed a 50 cm extension but no difference. :( Can anyone suggest a DVB-T2 USB stick that works on the Raspberry Pi B+? // Peter -- 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: PCTV Triplestick and Raspberry Pi B+
On Tue, 7 Jul 2015, Patrick Boettcher wrote: I installed the 32-bit version of the same OS (Debian 8, kernel 3.16.0, i386) and the result was a bit suprising. In 32-bit I couldn't even scan a DVT-T transponder! dvbv5-scan did Lock, but it didn't find any PSI PIDs. So there is for sure a problem with 32-bit platforms. And the DVT-T2 transponders didn't work either. Maybe the Raspberry problem can be a Endianess problem? No, rpi (arm) is little-endian as Intel. Which drivers is your device using again? [7.245815] em28xx: New device PCTV PCTV 292e @ 480 Mbps (2013:025f, interface 0, class 0) [7.256731] em28xx: DVB interface 0 found: isoc [7.262712] em28xx: chip ID is em28178 [9.258341] em28178 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x5110ff04 [9.267163] em28178 #0: EEPROM info: [9.272644] em28178 #0: microcode start address = 0x0004, boot configuration = 0x01 [9.291418] em28178 #0: AC97 audio (5 sample rates) [9.298231] em28178 #0: 500mA max power [9.303993] em28178 #0: Table at offset 0x27, strings=0x146a, 0x1888, 0x0a7e [9.313288] em28178 #0: Identified as PCTV tripleStick (292e) (card=94) [9.321852] em28178 #0: dvb set to isoc mode. [9.328536] usbcore: registered new interface driver em28xx [9.357476] em28178 #0: Binding DVB extension [9.380909] i2c i2c-1: Added multiplexed i2c bus 2 [9.389469] si2168 1-0064: Silicon Labs Si2168 successfully attached [9.410263] si2157 2-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached [9.422419] DVB: registering new adapter (em28178 #0) [9.428929] usb 1-1.4: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)... [9.442954] em28178 #0: DVB extension successfully initialized [9.450692] em28xx: Registered (Em28xx dvb Extension) extension [9.482115] em28178 #0: Registering input extension [9.563907] em28178 #0: Input extension successfully initalized [9.571364] em28xx: Registered (Em28xx Input Extension) extension [ 297.703612] si2168 1-0064: found a 'Silicon Labs Si2168-B40' [ 300.998391] si2168 1-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw' [ 301.275434] si2168 1-0064: firmware version: 4.0.4 [ 301.284625] si2157 2-0060: found a 'Silicon Labs Si2157-A30' [ 301.340643] si2157 2-0060: firmware version: 3.0.5 // Peter -- 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: PCTV Triplestick and Raspberry Pi B+
On Tue, 7 Jul 2015 17:33:01 +0200 (SST) Peter Fassberg wrote: > On Sun, 5 Jul 2015, Patrick Boettcher wrote: > > > Your Intel platform is 64bit. I don't know the TripleStick nor the SI or > > the EM28xx-driver but _maybe_ there is a problem with it on 32-bit > > platforms. A long shot, I know, but you'll never know. > > That was a very good point. > > I installed the 32-bit version of the same OS (Debian 8, kernel 3.16.0, i386) > and the result was a bit suprising. > > In 32-bit I couldn't even scan a DVT-T transponder! dvbv5-scan did Lock, but > it didn't find any PSI PIDs. So there is for sure a problem with 32-bit > platforms. And the DVT-T2 transponders didn't work either. > > Maybe the Raspberry problem can be a Endianess problem? No, rpi (arm) is little-endian as Intel. Which drivers is your device using again? regards, -- Patrick. -- 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: PCTV Triplestick and Raspberry Pi B+
On Tue, 7 Jul 2015 17:38:25 +0200 (SST) Peter Fassberg wrote: > On Tue, 7 Jul 2015, Patrick Boettcher wrote: > > >> I installed the 32-bit version of the same OS (Debian 8, kernel 3.16.0, > >> i386) and the result was a bit suprising. > >> > >> In 32-bit I couldn't even scan a DVT-T transponder! dvbv5-scan did Lock, > >> but it didn't find any PSI PIDs. So there is for sure a problem with > >> 32-bit platforms. And the DVT-T2 transponders didn't work either. > >> > >> Maybe the Raspberry problem can be a Endianess problem? > > > > No, rpi (arm) is little-endian as Intel. > > > > Which drivers is your device using again? > > [7.245815] em28xx: New device PCTV PCTV 292e @ 480 Mbps (2013:025f, > interface 0, class 0) > [7.256731] em28xx: DVB interface 0 found: isoc > [7.262712] em28xx: chip ID is em28178 > [9.258341] em28178 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x5110ff04 > [9.267163] em28178 #0: EEPROM info: > [9.272644] em28178 #0: microcode start address = 0x0004, boot > configuration = 0x01 > [9.291418] em28178 #0: AC97 audio (5 sample rates) > [9.298231] em28178 #0: 500mA max power > [9.303993] em28178 #0: Table at offset 0x27, strings=0x146a, 0x1888, > 0x0a7e > [9.313288] em28178 #0: Identified as PCTV tripleStick (292e) (card=94) > [9.321852] em28178 #0: dvb set to isoc mode. > [9.328536] usbcore: registered new interface driver em28xx > [9.357476] em28178 #0: Binding DVB extension > [9.380909] i2c i2c-1: Added multiplexed i2c bus 2 > [9.389469] si2168 1-0064: Silicon Labs Si2168 successfully attached > [9.410263] si2157 2-0060: Silicon Labs Si2147/2148/2157/2158 successfully > attached > [9.422419] DVB: registering new adapter (em28178 #0) > [9.428929] usb 1-1.4: DVB: registering adapter 0 frontend 0 (Silicon Labs > Si2168)... > [9.442954] em28178 #0: DVB extension successfully initialized > [9.450692] em28xx: Registered (Em28xx dvb Extension) extension > [9.482115] em28178 #0: Registering input extension > [9.563907] em28178 #0: Input extension successfully initalized > [9.571364] em28xx: Registered (Em28xx Input Extension) extension > [ 297.703612] si2168 1-0064: found a 'Silicon Labs Si2168-B40' > [ 300.998391] si2168 1-0064: downloading firmware from file > 'dvb-demod-si2168-b40-01.fw' > [ 301.275434] si2168 1-0064: firmware version: 4.0.4 [ 301.284625] si2157 > 2-0060: found a 'Silicon Labs Si2157-A30' > [ 301.340643] si2157 2-0060: firmware version: 3.0.5 Just reading quickly the changes made to the si2157 and si2168 driver since 3.16 up to 4.1 makes me think that it is worth a try. Plenty of things have changed regarding buffers and memcpy. Though I haven't found (yet) a 64bit and 32bit mix up yet in the 3.16 version. Might be the RF frequency that is truncated on 32bit platforms somewhere. That could explain that there is no crash but simply not tuning. Can you easily try more recent kernels or media_trees? -- Patrick. -- 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: PCTV Triplestick and Raspberry Pi B+
On Tue, 7 Jul 2015 18:25:41 +0200 Patrick Boettcher wrote: > > [ 301.275434] si2168 1-0064: firmware version: 4.0.4 [ 301.284625] si2157 > > 2-0060: found a 'Silicon Labs Si2157-A30' > > [ 301.340643] si2157 2-0060: firmware version: 3.0.5 > Can you easily try more recent kernels or media_trees? It seems you are already using a more recent version of the si21xx-drivers than provided with 3.16. (in 3.16.0 there is no firmware version-print in si2157) -- Patrick. -- 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: PCTV Triplestick and Raspberry Pi B+
On Tue, 7 Jul 2015, Patrick Boettcher wrote: Might be the RF frequency that is truncated on 32bit platforms somewhere. That could explain that there is no crash but simply not tuning. This is the current status: ARM 32-bit, kernel 4.0.6, updated media_tree: Works with DVB-T, no lock on DVB-T2. Intel 32-bit, kernel 3.16.0, standard media_tree: Locks, but no PSIs detected. Intel 64-bit, kernel 3.16.0, standard media_tree: Works like a charm. So I don't think that en RF freq is truncated. -- Peter -- 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: PCTV Triplestick and Raspberry Pi B+
Patrick Boettcher wrote: [ 301.275434] si2168 1-0064: firmware version: 4.0.4 [ 301.284625] si2157 2-0060: found a 'Silicon Labs Si2157-A30' [ 301.340643] si2157 2-0060: firmware version: 3.0.5 Can you easily try more recent kernels or media_trees? It seems you are already using a more recent version of the si21xx-drivers than provided with 3.16. (in 3.16.0 there is no firmware version-print in si2157) Yes, I did an upgrade to the latest I could find before I gave up. This is in use: root@raspberrypi:~# uname -a Linux raspberrypi 4.0.6-v7+ #798 SMP PREEMPT Tue Jun 23 18:06:01 BST 2015 armv7l GNU/Linux root@raspberrypi:~# modinfo si2157 filename: /lib/modules/4.0.6-v7+/kernel/drivers/media/tuners/si2157.ko firmware: dvb-tuner-si2158-a20-01.fw author: Antti Palosaari description:Silicon Labs Si2146/2147/2148/2157/2158 silicon tuner driver srcversion: 397E31D773FD172EA0CE7F6 root@raspberrypi:~# modinfo si2168 filename: /lib/modules/4.0.6-v7+/kernel/drivers/media/dvb-frontends/si2168.ko firmware: dvb-demod-si2168-b40-01.fw firmware: dvb-demod-si2168-a30-01.fw firmware: dvb-demod-si2168-a20-01.fw description:Silicon Labs Si2168 DVB-T/T2/C demodulator driver author: Antti Palosaari srcversion: 12127041CAEFE39931DE3A1 root@raspberrypi:~# modinfo em28xx filename: /lib/modules/4.0.6-v7+/kernel/drivers/media/usb/em28xx/em28xx.ko version:0.2.1 description:Empia em28xx device driver author: Ludovico Cavedon , Markus Rechberger , Mauro Carvalho Chehab , Sascha Sommer srcversion: 1E6C5892B8BEB1E429BECC7 vermagic: 4.0.6-v7 SMP preempt mod_unload modversions ARMv7 parm: tuner:tuner type (int) parm: disable_ir:disable infrared remote support (int) parm: disable_usb_speed_check:override min bandwidth requirement of 480M bps (int) parm: card:card type (array of int) parm: usb_xfer_mode:USB transfer mode for frame data (-1 = auto, 0 = prefer isoc, 1 = prefer bulk) (int) parm: i2c_scan:scan i2c bus at insmod time (int) parm: i2c_debug:i2c debug message level (1: normal debug, 2: show I2C transfers) (int) parm: core_debug:enable debug messages [core] (int) parm: reg_debug:enable debug messages [URB reg] (int) root@raspberrypi:~# modinfo em28xx_dvb filename: /lib/modules/4.0.6-v7+/kernel/drivers/media/usb/em28xx/em28xx-dvb.ko version:0.2.1 description:Empia em28xx device driver - digital TV interface author: Mauro Carvalho Chehab srcversion: 60267D5DE16B950E37CD3FF vermagic: 4.0.6-v7 SMP preempt mod_unload modversions ARMv7 parm: debug:enable debug messages [dvb] (int) parm: adapter_nr:DVB adapter numbers (array of short) root@raspberrypi:~# modinfo em28xx_rc filename: /lib/modules/4.0.6-v7+/kernel/drivers/media/usb/em28xx/em28xx-rc.ko version:0.2.1 description:Empia em28xx device driver - input interface author: Mauro Carvalho Chehab srcversion: C0534469E29D3F7AEB3353A depends:em28xx,rc-core vermagic: 4.0.6-v7 SMP preempt mod_unload modversions ARMv7 parm: ir_debug:enable debug messages [IR] (int) -- 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
cron job: media_tree daily build: OK
This message is generated daily by a cron job that builds media_tree for the kernels and architectures in the list below. Results of the daily build of media_tree: date: Wed Jul 8 04:00:18 CEST 2015 git branch: test git hash: 8783b9c50400c6279d7c3b716637b98e83d3c933 gcc version:i686-linux-gcc (GCC) 5.1.0 sparse version: v0.5.0-44-g40791b9 smatch version: 0.4.1-3153-g7d56ab3 host hardware: x86_64 host os:4.0.0-3.slh.1-amd64 linux-git-arm-at91: OK linux-git-arm-davinci: OK linux-git-arm-exynos: OK linux-git-arm-mx: OK linux-git-arm-omap: OK linux-git-arm-omap1: OK linux-git-arm-pxa: OK linux-git-blackfin-bf561: OK linux-git-i686: OK linux-git-m32r: OK linux-git-mips: OK linux-git-powerpc64: OK linux-git-sh: OK linux-git-x86_64: OK linux-2.6.32.27-i686: OK linux-2.6.33.7-i686: OK linux-2.6.34.7-i686: OK linux-2.6.35.9-i686: OK linux-2.6.36.4-i686: OK linux-2.6.37.6-i686: OK linux-2.6.38.8-i686: OK linux-2.6.39.4-i686: OK linux-3.0.60-i686: OK linux-3.1.10-i686: OK linux-3.2.37-i686: OK linux-3.3.8-i686: OK linux-3.4.27-i686: OK linux-3.5.7-i686: OK linux-3.6.11-i686: OK linux-3.7.4-i686: OK linux-3.8-i686: OK linux-3.9.2-i686: OK linux-3.10.1-i686: OK linux-3.11.1-i686: OK linux-3.12.23-i686: OK linux-3.13.11-i686: OK linux-3.14.9-i686: OK linux-3.15.2-i686: OK linux-3.16.7-i686: OK linux-3.17.8-i686: OK linux-3.18.7-i686: OK linux-3.19-i686: OK linux-4.0-i686: OK linux-4.1.1-i686: OK linux-4.2-rc1-i686: OK linux-2.6.32.27-x86_64: OK linux-2.6.33.7-x86_64: OK linux-2.6.34.7-x86_64: OK linux-2.6.35.9-x86_64: OK linux-2.6.36.4-x86_64: OK linux-2.6.37.6-x86_64: OK linux-2.6.38.8-x86_64: OK linux-2.6.39.4-x86_64: OK linux-3.0.60-x86_64: OK linux-3.1.10-x86_64: OK linux-3.2.37-x86_64: OK linux-3.3.8-x86_64: OK linux-3.4.27-x86_64: OK linux-3.5.7-x86_64: OK linux-3.6.11-x86_64: OK linux-3.7.4-x86_64: OK linux-3.8-x86_64: OK linux-3.9.2-x86_64: OK linux-3.10.1-x86_64: OK linux-3.11.1-x86_64: OK linux-3.12.23-x86_64: OK linux-3.13.11-x86_64: OK linux-3.14.9-x86_64: OK linux-3.15.2-x86_64: OK linux-3.16.7-x86_64: OK linux-3.17.8-x86_64: OK linux-3.18.7-x86_64: OK linux-3.19-x86_64: OK linux-4.0-x86_64: OK linux-4.1.1-x86_64: OK linux-4.2-rc1-x86_64: OK apps: OK spec-git: OK sparse: WARNINGS smatch: ERRORS Detailed results are available here: http://www.xs4all.nl/~hverkuil/logs/Wednesday.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Wednesday.tar.bz2 The Media Infrastructure API from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/media.html -- 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
