Hi, this is David Wu from Shanghai, China.
We are a printing company, we can print color box, corrugated box,
label, hang tag etc.
Please let me know if you need these.
I will send you the website then.
Best regards,
David Wu
--
To unsubscribe from this list: send the line "unsubscribe linux-medi
Added Sveon STV21 device based on Realtek RTL2832U and FC0013 tuner
Signed-off-by: Sebastian Kemper
---
diff --git a/drivers/media/dvb-core/dvb-usb-ids.h
b/drivers/media/dvb-core/dvb-usb-ids.h
index 11d2bea..b518ada 100644
--- a/drivers/media/dvb-core/dvb-usb-ids.h
+++ b/drivers/media/dvb-core/
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: Thu Jun 12 04:00:29 CEST 2014
git branch: test
git hash: 5ea878796f0a1d9649fe43a6a09df53d3915c0ef
gcc versi
Dear David,
From our test, Linux kernel 3.14 + v3.6.0.0 firmware have good RF performance
on single and dual tuners.
BRs,
Jason
-Original Message-
From: linux-media-ow...@vger.kernel.org
[mailto:linux-media-ow...@vger.kernel.org] On Behalf Of David Shirley
Sent: Wednesday, June 11, 201
On 06/11/2014 04:21 AM, Philipp Zabel wrote:
> Hi Steve,
>
> Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
>> Hi all,
>>
>> This patch set adds video capture support for the Freescale i.MX6 SOC.
>>
>> It is a from-scratch standardized driver that works with community
>> v4l2 ut
I just ran blind scan using w_scan and it interrupted scanning, with
following error (ioctl DMX_SET_FILTER failed: 27 File too large).
602000: (time: 00:58.973)
(0.308sec): SCL (0x1F)
(0.308sec) signal
(0.308sec) lock
signal ok: QAM_AUTO f = 602000 kHz I999B8C999D
Do you have any idea about that bug?
kernel: submit of urb 0 failed (error=-27)
https://bugzilla.kernel.org/show_bug.cgi?id=72891
I have seen it recently very often when I try start streaming DVB. When
it happens, device is unusable. I have feeling that it could be coming
from recent 28xx big
Reviewed-by: Antti Palosaari
Acked-by: Antti Palosaari
On 06/03/2014 08:19 PM, CrazyCat wrote:
TS clock inversion in config.
Signed-off-by: Evgeny Plehov
---
drivers/media/dvb-frontends/cxd2820r.h| 6 ++
drivers/media/dvb-frontends/cxd2820r_c.c | 1 +
drivers/media/dvb-frontend
On 06/11/2014 01:33 PM, Hans Verkuil wrote:
> On 06/11/2014 09:43 PM, Scott Doty wrote:
>> On 06/11/2014 01:24 AM, Hans Verkuil wrote:
>>> On 06/03/14 03:23, Scott Doty wrote:
Hello Mr. Hans and mailing list,
In a nutshell, I'm having some hdpvr trouble:
I'm using vlc to vi
On 06/11/2014 09:43 PM, Scott Doty wrote:
> On 06/11/2014 01:24 AM, Hans Verkuil wrote:
>> On 06/03/14 03:23, Scott Doty wrote:
>>> Hello Mr. Hans and mailing list,
>>>
>>> In a nutshell, I'm having some hdpvr trouble:
>>>
>>> I'm using vlc to view the stream. Kernel 3.9.11 works pretty well,
>>>
On 06/11/2014 01:24 AM, Hans Verkuil wrote:
> On 06/03/14 03:23, Scott Doty wrote:
>> Hello Mr. Hans and mailing list,
>>
>> In a nutshell, I'm having some hdpvr trouble:
>>
>> I'm using vlc to view the stream. Kernel 3.9.11 works pretty well,
>> including giving me AC3 5.1 audio from the optical
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> This is a V4L2 camera interface driver for i.MX6. See
> Documentation/video4linux/mx6_camera.txt.
The CSI and ICs part are not i.MX6 specific. The only difference between
i.MX5 and i.MX6DL (besides register offsets and some minor
* Arnd Bergmann [140611 07:51]:
> On Wednesday 11 June 2014 09:42:04 Nishanth Menon wrote:
> > On 06/11/2014 09:35 AM, Arnd Bergmann wrote:
> > > The OMAP4 camera support depends on I2C and VIDEO_V4L2, both
> > > of which can be loadable modules. This causes build failures
> > > if we want the cam
On 06/11/2014 09:49 AM, Arnd Bergmann wrote:
> On Wednesday 11 June 2014 09:42:04 Nishanth Menon wrote:
>> On 06/11/2014 09:35 AM, Arnd Bergmann wrote:
>>> The OMAP4 camera support depends on I2C and VIDEO_V4L2, both
>>> of which can be loadable modules. This causes build failures
>>> if we want th
On Wednesday 11 June 2014 09:42:04 Nishanth Menon wrote:
> On 06/11/2014 09:35 AM, Arnd Bergmann wrote:
> > The OMAP4 camera support depends on I2C and VIDEO_V4L2, both
> > of which can be loadable modules. This causes build failures
> > if we want the camera driver to be built-in.
> >
> > This ca
* Arnd Bergmann [140611 07:37]:
> The OMAP4 camera support depends on I2C and VIDEO_V4L2, both
> of which can be loadable modules. This causes build failures
> if we want the camera driver to be built-in.
That's good news, but let's not fix it this way.
> This can be solved by turning the optio
On 06/11/2014 09:35 AM, Arnd Bergmann wrote:
> The OMAP4 camera support depends on I2C and VIDEO_V4L2, both
> of which can be loadable modules. This causes build failures
> if we want the camera driver to be built-in.
>
> This can be solved by turning the option into "tristate",
> which unfortunat
The OMAP4 camera support depends on I2C and VIDEO_V4L2, both
of which can be loadable modules. This causes build failures
if we want the camera driver to be built-in.
This can be solved by turning the option into "tristate",
which unfortunately causes another problem, because the
driver incorrectl
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> Adds the following new IPU units:
>
> - Camera Sensor Interface (csi)
> - Sensor Multi FIFO Controller (smfc)
> - Image Converter (ic)
> - Image Rotator (irt)
>
> Signed-off-by: Steve Longerbeam
> ---
> drivers/staging/imx-drm/
Hey Jason,
We have access to the following firmwares for it913x:
http://palosaari.fi/linux/v4l-dvb/firmware/IT9135/12.10.04.1/IT9135v2_3.40.1.0_3.17.1.0/
http://palosaari.fi/linux/v4l-dvb/firmware/IT9135/12.10.04.1/IT9135v2_3.42.3.3_3.29.3.3/
and of course the one the kernel uses:
http://www.i
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> Map the IOMUXC registers, which will be needed by ipu-csi for mux
> control.
>
> Signed-off-by: Steve Longerbeam
> ---
> drivers/staging/imx-drm/ipu-v3/ipu-common.c |8
> drivers/staging/imx-drm/ipu-v3/ipu-prv.h
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> +static const struct i2c_device_id ov5640_id[] = {
> + {"ov5640_mipi", 0},
Is there really a different ov5640_mipi chip as opposed to ov5640?
I suspect this could be well configured in the OF graph endpoint.
regards
Philipp
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
[...]
> static int pca953x_read_single(struct pca953x_chip *chip, int reg, u32 *val,
> @@ -735,6 +741,26 @@ static int pca953x_probe(struct i2c_client *client,
> /* If I2C node has no interrupts property, disable GPIO
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
[...]
> +&ipu1 {
> + status = "okay";
> +
> + v4l2-capture {
> + compatible = "fsl,imx6-v4l2-capture";
I'm not happy with adding the simple-bus compatible to the ipu
device tree node just to instantiate a virtual
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> The IPU can have child devices now, so add "simple-bus" to
> compatible list to ensure creation of the children.
>
> Signed-off-by: Steve Longerbeam
> ---
> .../bindings/staging/imx-drm/fsl-imx-drm.txt |6 --
> arc
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> Signed-off-by: Jiada Wang
> ---
> drivers/staging/imx-drm/ipu-v3/ipu-common.c | 18 ++
> include/linux/platform_data/imx-ipu-v3.h|1 +
> 2 files changed, 19 insertions(+)
>
> diff --git a/drivers/stagin
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> Add mode device info to the MIPI CSI2 receiver node: compatible string,
> interrupt sources, clocks.
>
> Signed-off-by: Steve Longerbeam
> ---
> arch/arm/boot/dts/imx6qdl.dtsi |7 ++-
> 1 file changed, 6 insertions(+), 1
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> Move channel parameter memory setup functions and macros into a new
> submodule ipu-cpmem. In the process, cleanup arguments to the functions
> to take a channel pointer instead of a pointer into cpmem for that
> channel. That allo
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> Rename the ENC/VF/PP rotation channel names, to be more consistent
> with the convention that *_MEM is write-to-memory channels and
> MEM_* is read-from-memory channels. Also add the channels who's
> source and destination is the I
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> Adds of-alias id to ipu_soc and retrieve with ipu_get_num().
It would be nice to have a comment here what this will be needed for.
I see that later ipu-csi uses this to find the correct input mux and
mx6-encode selects the DMA ch
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> Add ipu_idmac_current_buffer(), returns the currently active
> buffer number in the given channel.
This is already implemented in drm-next ...
> Checks for third buffer ready in case triple-buffer support is
> added later.
... b
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> Adds two new functions, ipu_set_csi_src_mux() and ipu_set_ic_src_mux(),
> that select the inputs to the CSI and IC respectively. Both muxes are
> programmed in the IPU_CONF register.
>
> Signed-off-by: Steve Longerbeam
Acked-by:
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> Add simple conversion from pixelformat to total bits-per-pixel.
[...]
> +/*
> + * Standard bpp from pixel format.
> + */
> +int ipu_bits_per_pixel(u32 pixelformat)
> +{
> + switch (pixelformat) {
> + case V4L2_PIX_FMT_YUV42
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> In subsequent patches, the video capture units will be added (csi, smfc,
> ic, irt). So the IPU prototypes are no longer needed only by imx-drm,
> so we need to export them to a common include path.
>
> Signed-off-by: Steve Longer
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> Add ipu0 (and ipu1 for quad) aliases to ipu1/ipu2 nodes respectively.
>
> Signed-off-by: Steve Longerbeam
> ---
> arch/arm/boot/dts/imx6q.dtsi |1 +
> arch/arm/boot/dts/imx6qdl.dtsi |1 +
> 2 files changed, 2 insertion
Hi Steve,
Am Samstag, den 07.06.2014, 14:56 -0700 schrieb Steve Longerbeam:
> Hi all,
>
> This patch set adds video capture support for the Freescale i.MX6 SOC.
>
> It is a from-scratch standardized driver that works with community
> v4l2 utilities, such as v4l2-ctl, v4l2-cap, and the v4l2src gst
--
Váženie E-mail užívateľa;
Prekročili ste limit úložisko poštovej schránky set 23432
Webmaster Služby / a môžu byť použité na odosielanie problém
a bude, kým si nechajte potvrdiť svoju e-mailovú adresu znova. postupy
by mali byť
sa konala počas zobrazenia, kliknite na kontrolu
odkaz a zadaj
Hi Dan,
Thanks for the patch.
On Wed, Jun 11, 2014 at 8:31 AM, Dan Carpenter wrote:
> We recently changed some locking around so we need some new unlocks on
> the error paths.
>
> Signed-off-by: Dan Carpenter
> ---
> Please review this one carefully. I don't know if the unlock should go
> befo
On 06/03/14 03:23, Scott Doty wrote:
> Hello Mr. Hans and mailing list,
>
> In a nutshell, I'm having some hdpvr trouble:
>
> I'm using vlc to view the stream. Kernel 3.9.11 works pretty well,
> including giving me AC3 5.1 audio from the optical input to the
> Hauppauge device. The only problem
Dear David,
The RF performance of ITE9137 BX + IE9133 dongle is a little worse than single
tuner.
As our test resolut, the RF performances should be -80db and -82db for dual
tuners and single tuner.
There is an issue in hardware design if the reception capability is too worse.
We don’t need to
I have not received any response on this email... so I hope to bump this
thread back to the more active region in most people's in-boxes.
On 2014-05-31 10:37, Niels Laukens wrote:
> Hi,
>
> I believe I've found a bug in the NEC decoder for InfraRed remote
> controls. The problem manifests itself
On Wed, Jun 11, 2014 at 05:31:47AM +, jason.d...@ite.com.tw wrote:
> Dear Sebastian,
>
> There is a RF performance issue in the af9033 driver of kernel 3.15.
> It is no problem in the it913x driver of kernel 3.14. There were some
> initial sequences not correct after the it913x driver was int
On Wed, Jun 11, 2014 at 7:36 AM, Sakari Ailus
wrote:
> Add numeric definitions for menu items used in the smiapp driver's test
> pattern menu.
>
> Signed-off-by: Sakari Ailus
> Acked-by: Laurent Pinchart
Acked-by: Lad, Prabhakar
Regards,
--Prabhakar Lad
> ---
> since v3:
> - Add Kbuild entry
We recently changed some locking around so we need some new unlocks on
the error paths.
Signed-off-by: Dan Carpenter
---
Please review this one carefully. I don't know if the unlock should go
before or after the list_for_each_entry_safe() loop.
diff --git a/drivers/media/platform/davinci/vpif_c
On 06/11/2014 02:54 AM, Steve Longerbeam wrote:
> On 06/10/2014 08:11 AM, Hans Verkuil wrote:
>> On 06/09/2014 06:42 PM, Steve Longerbeam wrote:
>>> On 06/08/2014 01:36 AM, Hans Verkuil wrote:
Hi Steve!
On 06/07/2014 11:56 PM, Steve Longerbeam wrote:
> Hi all,
>
> This pa
Hey Jason,
Do we know if that RF problem exists in 3.14.5? Using the IT913X driver?
I have a Leadtek Winfast Dual Dongle (0413:6a05 - dual usb - ITE9137
BX + IE9133) which is being extremely painful (random signal locks,
tzap reports ok signal strength for one tuner but poor for the other,
random
46 matches
Mail list logo
