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 Oct 28 04:00:18 CET 2014
git branch: test
git hash: 1ef24960ab78554fe7e8e77d8fc86524fbd60d3c
gcc
On 2014-10-26 20:33, Tomas Melin wrote:
On Sat, Oct 25, 2014 at 12:03 PM, David Härdeman da...@hardeman.nu
wrote:
Wouldn't something like this be a simpler way of achieving the same
result? (untested):
The idea was to remove the empty change_protocol function that had
been added in the
Hello
As we discussed in the mini-summit I am interested in upstreaming an
API for Dead Pixels.
Since it is not viable to push my camera code, I would like to add it
to an already supported camera.
On the summit somebody mention a board that also has hardware support
for Dead Pixels, but the
Kindly View attachment for loan offer @ the rate of 3.5% interest.
3.5 WONGA LOANS OFFER.pdf
Description: Adobe PDF document
tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f7e87a44ef60ad379e39b45437604141453bf0ec
commit: 3cf0c6bd68915aee3b5827b960e485de201e42c1 Merge remote-tracking branch
'linus/master' into patchwork
date: 5 weeks ago
config: x86_64-randconfig-iv1-10281307
Hi Ricardo,
Ricardo Ribalda Delgado wrote:
Hello
As we discussed in the mini-summit I am interested in upstreaming an
API for Dead Pixels.
Since it is not viable to push my camera code, I would like to add it
to an already supported camera.
On the summit somebody mention a board that
Hello,
On Tuesday 28 October 2014 15:10:22 Sakari Ailus wrote:
Ricardo Ribalda Delgado wrote:
Hello
As we discussed in the mini-summit I am interested in upstreaming an
API for Dead Pixels.
Since it is not viable to push my camera code, I would like to add it
to an already
On Mon, 14 Jul 2014 12:27:57 +0200
Hans de Goede hdego...@redhat.com wrote:
Hi,
On 07/11/2014 02:56 PM, Antonio Ospite wrote:
Signed-off-by: Antonio Ospite a...@ao2.it
Thanks, I've added this to my tree and send a pull-req for it
to Mauro.
Hi Hans, I still don't see the change in
Fixes the following smatch errors:
drivers/media/dvb-frontends/lgdt3306a.c: In function 'lgdt3306a_set_if':
drivers/media/dvb-frontends/lgdt3306a.c:695:6: warning: variable 'ret' set but
not used [-Wunused-but-set-variable]
int ret;
^
drivers/media/dvb-frontends/lgdt3306a.c: In function
The submitted lgdt3306a driver was not in a good shape for merging.
However, as most of the issues are trivial, I solved them.
There are still a few remaining issues:
- As reported by checkpatch.pl:
WARNING: added, moved or deleted file(s), does MAINTAINERS need
updating?
Who will
WARNING: braces {} are not necessary for any arm of this statement
+ if (ret == 0) {
[...]
+ } else {
[...]
Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com
diff --git a/drivers/media/dvb-frontends/lgdt3306a.c
b/drivers/media/dvb-frontends/lgdt3306a.c
Fix this CodingStyle error:
ERROR: Do not include the paragraph about writing to the Free Software
Foundation's mailing address from the sample GPL notice. The FSF has changed
addresses in the past, and may do so ag$
#56: FILE: drivers/media/dvb-frontends/lgdt3306a.c:19:
Fix two smatch warnings:
drivers/media/dvb-frontends/lgdt3306a.h:53:28: error: dubious one-bit
signed bitfield
drivers/media/dvb-frontends/lgdt3306a.h:56:33: error: dubious one-bit
signed bitfield
Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com
diff --git
Ideally, we should be replacing this function by intlog10().
While we don't do that, let's at least constify the tables,
in order to remove its code footfrint, and get rid of nelems.
This also fixes a few 80-cols CodingStyle warnings.
Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com
Simplify the check if CONFIG_DVB_LGDT3306A is enabled, use the
IS_ENABLED() macro, just like the other frontend modules.
Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com
diff --git a/drivers/media/dvb-frontends/lgdt3306a.c
b/drivers/media/dvb-frontends/lgdt3306a.c
index
While this is not a mandatory rule at the CodingStyle, we prefer
hexadecimal values in lowercase. Currently, there's a mix of lowercase
and uppercase ons at lgdt3306a. So, convert all to lowercase with this
small script:
perl -ne 'if (m,0x([\dA-F]+),) { $o=$1; $n=lc $1; s,0x($o),0x$n, }
As warned by smatch:
drivers/media/dvb-frontends/lgdt3306a.c:1354 log10_x1000() error:
buffer overflow 'valx_x10' 14 = 14
drivers/media/dvb-frontends/lgdt3306a.c:1355 log10_x1000() error:
buffer overflow 'log10x_x1000' 14 = 14
There's a potential of returning a value out of the
Fix most of checkpatch warnings like:
WARNING: line over 80 characters
Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com
diff --git a/drivers/media/dvb-frontends/lgdt3306a.c
b/drivers/media/dvb-frontends/lgdt3306a.c
index ad483be1b64e..4e0cf443b9ff 100644
---
Use pr_foo() where there's a direct replacement. For debug, use
custom-made macros, for now, as there are 3 different debug levels.
We should get rid of those some day, specially since several such
macros can be just removed, as Kernel trace would provide about
the same output.
This gets rid of
Get rid of the remaining checkpatch.pl warnings:
WARNING: braces {} are not necessary for any arm of this statement
Signed-off-by: Mauro Carvalho Chehab mche...@osg.samsung.com
diff --git a/drivers/media/dvb-frontends/lgdt3306a.c
b/drivers/media/dvb-frontends/lgdt3306a.c
index
The logic there is too complex and it looks like an inifite
loop.
So, simplify the logic and implement it as a for loop.
This gets rid of the following checkpatch.pl warnings:
WARNING: else is not generally useful after a break or return
+ return LG3306_UNLOCK;
+
Fix a few minor CodingStyle issues at the source code:
- Use proper multi-line comments;
- Align the log tables;
- Remove the .type from dvb_frontend_ops, since this is not
needed anymore (since the drivers conversion to DVBv5);
- Remove emacs format
Em Thu, 23 Oct 2014 12:32:05 +0200
Kamil Debski k.deb...@samsung.com escreveu:
The following changes since commit 1ef24960ab78554fe7e8e77d8fc86524fbd60d3c:
Merge tag 'v3.18-rc1' into patchwork (2014-10-21 08:32:51 -0200)
are available in the git repository at:
Em Fri, 10 Oct 2014 10:04:58 +0200
Hans Verkuil hverk...@xs4all.nl escreveu:
(This patch is from Divneil except for the vivid changes which I added. He had
difficulties posting the patch without the mailer mangling it, so I'm
reposting
it for him)
- vb2 drivers to rely on VB2_MAX_FRAME.
On Tue, Oct 28, 2014 at 10:42 AM, David Härdeman da...@hardeman.nu wrote:
On 2014-10-26 20:33, Tomas Melin wrote:
Please let me know your preferences on which you prefer, and, if
needed, I'll make a new patch version.
I'd prefer the above, minimal, approach. But it's Mauro who decides in
IR receiver using nuvoton-cir and lirc required additional configuration
steps after upgrade from kernel 3.16 to 3.17-rcX.
Bisected regression to commit da6e162d6a4607362f8478c715c797d84d449f8b
([media] rc-core: simplify sysfs code).
The regression comes from adding function change_protocol in
Em Tue, 28 Oct 2014 20:43:14 +0200
Tomas Melin tomas.me...@iki.fi escreveu:
IR receiver using nuvoton-cir and lirc required additional configuration
steps after upgrade from kernel 3.16 to 3.17-rcX.
Bisected regression to commit da6e162d6a4607362f8478c715c797d84d449f8b
([media] rc-core:
Em Sat, 20 Sep 2014 14:41:37 +0200
Hans Verkuil hverk...@xs4all.nl escreveu:
From: Hans Verkuil hans.verk...@cisco.com
This list is used some buffers have a different format, but that can
never happen. Remove it and all associated code.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
On Tue, Oct 28, 2014 at 08:43:14PM +0200, Tomas Melin wrote:
IR receiver using nuvoton-cir and lirc required additional configuration
steps after upgrade from kernel 3.16 to 3.17-rcX.
Bisected regression to commit da6e162d6a4607362f8478c715c797d84d449f8b
([media] rc-core: simplify sysfs code).
On 10/27/2014 06:52 AM, Mauro Carvalho Chehab wrote:
Em Sun, 26 Oct 2014 09:27:40 +0100
Takashi Iwai ti...@suse.de escreveu:
Hmm... this is actually more complex than that. V4L2 driver doesn't
know if ALSA is streaming or not, or even if ALSA device node is opened
while he is touching at
We can use kfifo_initialized() to check if the fifo in lirc_buffer is
initialized or not. There's no need to have a dedicated fifo status
variable in lirc_buffer.
Signed-off-by: Martin Kaiser mar...@kaiser.cx
---
include/media/lirc_dev.h |8 ++--
1 file changed, 2 insertions(+), 6
The webcam is identified as Toshiba webcam although it seems a module
from Chicony Electronics. Not sure about the model so just refering
to it as Toshiba webcam that is in Portege z30 laptop.
Signed-off-by: Arend van Spriel aspr...@gmail.com
---
drivers/media/usb/uvc/uvc_driver.c | 8
Hi Arend,
Thank you for the patch.
On Tuesday 28 October 2014 23:30:18 Arend van Spriel wrote:
The webcam is identified as Toshiba webcam although it seems a module
from Chicony Electronics. Not sure about the model so just refering
to it as Toshiba webcam that is in Portege z30 laptop.
From: Sakari Ailus sakari.ai...@linux.intel.com
The Media controller doesn't tell much to the user in cases such as pipeline
startup failure. The link validation is the most common media graph (or in
V4L2's case, format) related reason for the failure. In more complex
pipelines the reason may not
Hi Sakari,
Thank you for the patch.
On Wednesday 29 October 2014 01:10:04 Sakari Ailus wrote:
From: Sakari Ailus sakari.ai...@linux.intel.com
The Media controller doesn't tell much to the user in cases such as pipeline
startup failure. The link validation is the most common media graph (or
Hi Laurent,
On Wed, Oct 29, 2014 at 01:20:06AM +0200, Laurent Pinchart wrote:
ret = -EPIPE;
+ dev_dbg(entity-parent-dev,
+ \%s\:%u must be connected by an enabled
link, error %d\n,
+ entity-name,
From: Sakari Ailus sakari.ai...@linux.intel.com
The Media controller doesn't tell much to the user in cases such as pipeline
startup failure. The link validation is the most common media graph (or in
V4L2's case, format) related reason for the failure. In more complex
pipelines the reason may not
Hi Shuah,
I'm understanding that you're collecting comments to write a RFC with the
needs by the media token, right?
I'm sending you my contributions to such text. See enclosed.
I suggest to change the subject and submit this on a separate thread, after
we finish the review of such document.
Em Tue, 28 Oct 2014 21:42:50 -0200
Mauro Carvalho Chehab mche...@osg.samsung.com escreveu:
Before starting with the description, this is the simplified diagram of
a media device (without IR, eeprom and other beasts):
As reference, a more complete diagram would be:
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 Oct 29 04:00:26 CET 2014
git branch: test
git hash: 7a7f1ab37dc8f66cf0ef10f3d3f1b79ac4bc67fc
gcc
Hi Kaneko-san, Hi Sergei,
On Tue, Oct 21, 2014 at 08:33:52PM +0900, Yoshihiro Kaneko wrote:
Hello Sergei,
2014-10-21 19:22 GMT+09:00 Sergei Shtylyov
sergei.shtyl...@cogentembedded.com:
Hello.
On 10/21/2014 9:08 AM, Yoshihiro Kaneko wrote:
From: Koji Matsuoka
41 matches
Mail list logo
