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: Sun Apr 16 05:00:15 CEST 2017
media-tree git hash:f2fe89061d79706eca5c47e4efdc09bbc171e74a
media_build gi
Several channels used at Bamberg and Hesselberg have been changed at the
start of 2017 to avoid potential interference with the new DVB-T2 service
started at the end of March. EinsPlus has been replaced with One in
October 2016.
Full details are available (in german) at http://dvb-t-bayern.de/ .
Hi Mauro,
I've two devices using this driver, and whenever I have them both in
use I eventually (between 10K and 100K secs uptime) i2c write errors
such as in the log below. If only have one of the devices in use, the
machine is stable.
The machine never recovers from the error.
All help aprecia
Thanks for the information Milan.
On 15/04/17 06:10 AM, Milan Broz wrote:
> I think your patch is ok (if it is just plain conversion), if it is
> really needed, we can switch to ahash later in follow-up patch.
Sounds good to me.
> p.s.
> there is a lot of lists on cc, but for this patch is missi
Hi all,
I've managed to build OpenVizsla USB tool.
So, here is how the things look like from hardware USB sniffer point of view:
[] 7.219456 d= 0.000997 [181.0 + 3.667] [ 3] IN : 4.5
[T ] 7.219459 d= 0.03 [181.0 + 7.083] [800] DATA0: 53 da
50 f9 c1 a5 4a d5 14 2c 55
Em Mon, 10 Apr 2017 20:06:03 +0200
Frank Schäfer escreveu:
> Am 26.03.2017 um 16:24 schrieb Frank Schäfer:
> >
> >
> > Am 24.03.2017 um 20:16 schrieb Mauro Carvalho Chehab:
> >> Em Thu, 23 Mar 2017 19:03:20 +0100
> >> Frank Schäfer escreveu:
> >>
> >>> Am 23.03.2017 um 13:56 schrieb Mauro Ca
On 04/14/2017 06:03 PM, Logan Gunthorpe wrote:
>
>
> On 14/04/17 02:39 AM, Christoph Hellwig wrote:
>> On Thu, Apr 13, 2017 at 04:05:22PM -0600, Logan Gunthorpe wrote:
>>> Very straightforward conversion to the new function in all four spots.
>>
>> I think the right fix here is to switch dm-crypt
With MEDIA_SUBDRV_AUTOSELECT enabled in the kernel config, the em28xx
driver currently does't select some used subdrivers.
Fix this by adding the missing auto-selections to the Kconfig file.
Signed-off-by: Frank Schäfer
---
drivers/media/usb/em28xx/Kconfig | 7 ++-
1 file changed, 6 insertio
The v4l2 dummy clock has been added with commit fc5d0f8a8878
("V4L2: em28xx: register a V4L2 clock source") to be able to use the ov2640
soc_camera driver.
Since commit 46796cfcd346 ("ov2640: use standard clk and enable it") it is
no longer required.
Signed-off-by: Frank Schäfer
---
drivers/medi
With an unknown sensor, norm_maxw() and norm_maxh() return 0 as max.
height and width values, which causes a devide by zero in size_to_scale().
Of course we could use speculative default values for unknown sensors,
but the chance that the device works at this resolution without any
driver/setup is
Signed-off-by: Frank Schäfer
---
drivers/media/usb/em28xx/em28xx-video.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/media/usb/em28xx/em28xx-video.c
b/drivers/media/usb/em28xx/em28xx-video.c
index aaa83f9e5c1a..8d253a5df0a9 100644
--- a/drivers/media/usb/em28xx/em28xx-video.
CbYCrY has been identified by looking into the tvp5150 driver and the
saa7115 datasheet.
YUV formats have been verified with em2765 + ov2640 (VAD Laplace webcam).
RGB8 formats have been verified with em2710/em2820 + mt9v011 (Silvercrest
webcam 1.3mpix).
I also did some cross-checking with these two
Hi!
> Worse than that, patch 2/2 gives the false sensation that both
> controls are equal.
>
> Ok, I understand that they need to be identical on the existing
> driver, in order to keep backward compatibility, but I'm afraid
> that, without a clear distinction between them at the documentation,
>
13 matches
Mail list logo
