Previously, images were relatively darker due to non-optimal
settings for black target level and bias.
Now, use recommended settings for black target level and output bias
as default values. The same default settings apply to all the resolutions.
Given these recommeneded settings do not change dyn
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: Fri Aug 25 05:00:17 CEST 2017
media-tree git hash:0779b8855c746c90b85bfe6e16d5dfa2a6a46655
media_build gi
When RC_CORE is a loadable module, and au0828 is built-in including
the RC support, we get a link error:
drivers/media/usb/au0828/au0828-input.o: In function `au0828_get_key_au8522':
au0828-input.c:(.text+0x474): undefined reference to `ir_raw_event_store'
drivers/media/usb/au0828/au0828-input.o:
Hi Mauro,
Here are the last atomisp cleanups and fixes for 4.14.
Please pull.
The following changes since commit 0779b8855c746c90b85bfe6e16d5dfa2a6a46655:
media: ddbridge: fix semicolon.cocci warnings (2017-08-20 10:25:22 -0400)
are available in the git repository at:
https://linuxtv.org
On Thu, 24 Aug 2017 13:26:28 -0600
Jonathan Corbet wrote:
> > - % To allow adjusting table sizes
> > - \\usepackage{adjustbox}
> > -
> > '''
> > }
>
> So this change doesn't quite match the changelog...what's the story there?
Indeed, with that patch applied, I get this:
! LaTeX Er
On Wed, 23 Aug 2017 05:56:57 -0300
Mauro Carvalho Chehab wrote:
> Now that the PDF building issues with Sphinx 1.6 got fixed,
> update the documentation and scripts accordingly.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> Documentation/conf.py | 3 ---
> Documentation/doc-gui
From: Daniel Scheller
Backport to pci_enable_msi_block for kernels <3.14 (picked from upstream
dddvb package). Also, ddbridge requires the PCI_DEVICE_SUB macro, which
was added in 3.8.
Signed-off-by: Daniel Scheller
Tested-by: Jasmin Jessich
---
This should finally silence all current media_bu
On Sat 19 Aug 01:22 PDT 2017, Bhumika Goyal wrote:
> Make this const as it is only stored in the type field of a device
> structure, which is const.
> Done using Coccinelle.
>
> Signed-off-by: Bhumika Goyal
Applied, thanks.
Regards,
Bjorn
> ---
> drivers/remoteproc/remoteproc_core.c | 2 +-
>
On Sat, 19 Aug 2017, Bhumika Goyal wrote:
> Make this const as it is only stored in the type field of a device
> structure, which is const.
> Done using Coccinelle.
>
> Signed-off-by: Bhumika Goyal
Acked-by: Guennadi Liakhovetski
Thanks
Guennadi
> ---
> drivers/media/i2c/soc_camera/mt9t031.
On Sat, Aug 19, 2017 at 01:52:19PM +0530, Bhumika Goyal wrote:
> Make this const as it is only stored in the type field of a device
> structure, which is const.
> Done using Coccinelle.
>
> Signed-off-by: Bhumika Goyal
Applied to pci/misc for v4.14, thanks!
> ---
> drivers/pci/endpoint/pci-epf
Hi Niklas,
On Mon, Jul 31, 2017 at 12:31:56AM +0200, Niklas Söderlund wrote:
> Instead of trying to cope with the failed memory allocation and still
> leaving the kernel in a semi-broken state (the subdevices will be
> released but never re-probed) simply abort. The kernel have already
> printed a
Hi Hans,
On Thu, Aug 24, 2017 at 09:59:41AM +0200, Hans Verkuil wrote:
> On 08/23/17 21:03, Niklas Söderlund wrote:
> > Hi,
> >
> > On 2017-08-18 15:42:37 +0200, Niklas Söderlund wrote:
> >> Hi Sakari and Laurent,
> >>
> >> Thanks for your feedback.
> >>
> >> On 2017-08-18 14:20:08 +0300, Laurent
Hi Mauro,
Thanks for the update! A few comments below.
(Cc Hans and Laurent.)
On Thu, Aug 24, 2017 at 09:07:35AM -0300, Mauro Carvalho Chehab wrote:
> From: "mche...@s-opensource.com"
>
> When we added support for omap3, back in 2010, we added a new
> type of V4L2 devices that aren't fully con
Hi Mauro,
This patchset includes the AS3645A LED driver as well as contents of the
previous pull request here of which the driver depends on:
https://patchwork.linuxtv.org/patch/43363/>
I've agreed with Jacek that the AS3645A patches in the pull request go
through the media tree. The same applie
On Thu, Aug 24, 2017 at 01:37:35PM +0200, Hans Verkuil wrote:
On 08/24/17 13:14, Brian Starkey wrote:
Hi Hans,
On Mon, Aug 21, 2017 at 06:36:29PM +0200, Hans Verkuil wrote:
On 08/21/2017 06:01 PM, Daniel Vetter wrote:
On Mon, Aug 21, 2017 at 5:52 PM, Brian Starkey wrote:
Hi all,
I couldn't
From: "mche...@s-opensource.com"
When we added support for omap3, back in 2010, we added a new
type of V4L2 devices that aren't fully controlled via the V4L2
device node. Yet, we never made it clear, at the V4L2 spec,
about the differences between both types.
Let's document them with the current
On 08/24/17 13:14, Brian Starkey wrote:
> Hi Hans,
>
> On Mon, Aug 21, 2017 at 06:36:29PM +0200, Hans Verkuil wrote:
>> On 08/21/2017 06:01 PM, Daniel Vetter wrote:
>>> On Mon, Aug 21, 2017 at 5:52 PM, Brian Starkey
>>> wrote:
Hi all,
I couldn't find this topic talked about elsewh
Hi Hans,
On Mon, Aug 21, 2017 at 06:36:29PM +0200, Hans Verkuil wrote:
On 08/21/2017 06:01 PM, Daniel Vetter wrote:
On Mon, Aug 21, 2017 at 5:52 PM, Brian Starkey wrote:
Hi all,
I couldn't find this topic talked about elsewhere, but apologies if
it's a duplicate - I'll be glad to be steered
MHL specification defines Remote Control Protocol(RCP) to
send input events between MHL devices.
The driver now recognizes RCP messages and reacts to them
by reporting key events to input subsystem, allowing
a user to control a device using TV remote control.
Signed-off-by: Maciej Purski
---
Cha
On Thu, Aug 24, 2017 at 08:47:54AM +0200, Hans Verkuil wrote:
> On 08/24/2017 02:07 AM, Jasmin J. wrote:
> > Hi!
> >
> > Just some notes on that patch.
> >
> > I have *not* tested it due to the lack of an ir remote control. So someone
> > needs to test this on an <= 4.9 Kernel, if the ir core is
Hi Laurent,
On Wed, Aug 23, 2017 at 03:59:35PM +0300, Laurent Pinchart wrote:
> Hi Sakari,
>
> On Wednesday, 23 August 2017 12:01:24 EEST Sakari Ailus wrote:
> > On Tue, Aug 22, 2017 at 03:52:33PM +0300, Laurent Pinchart wrote:
> > > On Friday, 18 August 2017 14:23:16 EEST Sakari Ailus wrote:
> >
On 08/23/17 21:03, Niklas Söderlund wrote:
> Hi,
>
> On 2017-08-18 15:42:37 +0200, Niklas Söderlund wrote:
>> Hi Sakari and Laurent,
>>
>> Thanks for your feedback.
>>
>> On 2017-08-18 14:20:08 +0300, Laurent Pinchart wrote:
>>> Hello,
>>>
>>> On Tuesday 15 Aug 2017 19:09:33 Sakari Ailus wrote:
>>
Hello Sean!
> I agree with Jasmin here. I noticed the same errors in the daily build and it
> is really caused by not using the correct functions. I just didn't have the
> time to follow up on it.
I started to fix also gpio-ir-tx.c, but stopped that because it was too late.
So I simply deactivated
Hi Mauro,
Here are two fixes for the smiapp and omap3isp drivers.
Please pull.
The following changes since commit 0779b8855c746c90b85bfe6e16d5dfa2a6a46655:
media: ddbridge: fix semicolon.cocci warnings (2017-08-20 10:25:22 -0400)
are available in the git repository at:
ssh://linuxtv.org/g
24 matches
Mail list logo
