On Tuesday, December 14, 2010 08:14:32 Marek Szyprowski wrote:
> Hello,
>
> On Saturday, December 11, 2010 5:55 PM Hans Verkuil wrote:
>
> Big thanks for the review! I will fix all these minor issues and resend
> the patches soon. I hope we will manage to get videobuf2 merged soon! :)
>
> > Hi M
Hello,
On Saturday, December 11, 2010 5:55 PM Hans Verkuil wrote:
Big thanks for the review! I will fix all these minor issues and resend
the patches soon. I hope we will manage to get videobuf2 merged soon! :)
> Hi Marek,
>
> Here is my review. I wish I could ack it, but I found a few bugs tha
Hi
What about my last patch?? This is OK or bad?
Our customers kick me every day with IR remotes.
With my best regards, Dmitry.
--
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.kerne
Em 13-12-2010 16:31, Jarod Wilson escreveu:
> On Mon, Dec 13, 2010 at 01:06:00AM -0800, Dmitry Torokhov wrote:
>> On Thu, Dec 09, 2010 at 11:16:47AM -0800, Dmitry Torokhov wrote:
>>> On Thu, Dec 09, 2010 at 08:04:36PM +0100, Henrik Rydberg wrote:
On 12/09/2010 10:39 AM, Dmitry Torokhov wrote:
Hi Strakh:
Thanks for your patch.
But I prefer to remove the mutex_unlock() in the pd_vidioc_s_fmt(),
since the pd_vidioc_s_fmt() is also called in restore_v4l2_context().
would you please change the patch?
I will ack it.
Best Regards
Huang Shijie
2010/12/13 Alexander Strakh :
> KERNEL
On Mon, 13 Dec 2010 12:26:49 +0100
Michal Nazarewicz wrote:
> The Contiguous Memory Allocator is a set of functions that lets
> one initialise a region of memory which then can be used to perform
> allocations of contiguous memory chunks from. The implementation
> uses MIGRATE_CMA migration type
On Mon, 13 Dec 2010 12:26:47 +0100
Michal Nazarewicz wrote:
> The MIGRATE_CMA migration type has two main characteristics:
> (i) only movable pages can be allocated from MIGRATE_CMA
> pageblocks and (ii) page allocator will never change migration
> type of MIGRATE_CMA pageblocks.
>
> This guaran
On 17:13 Sun 12 Dec 2010, Torsten Kaiser wrote:
> * change &fh->cap.vb_lock in bttv_open() AND radio_open() to
> &btv->init.cap.vb_lock
> * add a mutex_init(&btv->init.cap.vb_lock) to the setup of init in
> bttv_probe()
That seems like a reasonable suggestion. An openSUSE user submitted this
bu
On Mon, 13 Dec 2010 11:27:24 -0200
Mauro Carvalho Chehab wrote:
> > case SENSOR_OV7660:
> > init = ov7660_sensor_param1;
> > - if (sd->bridge == BRIDGE_SN9C120) {
> > - if (mode) { /* 320x240 - 160x120 */
> > - reg1
On Mon, Dec 13, 2010 at 3:04 PM, Dave Young wrote:
> On Sun, Dec 12, 2010 at 05:13:47PM +0100, Torsten Kaiser wrote:
>> On Sun, Dec 12, 2010 at 2:15 PM, Dave Young
>> wrote:
>> > oops happen in bttv_open while locking uninitialized mutex fh->cap.vb_lock
>> > add mutex_init before usage
>>
>> I h
On Monday, December 13, 2010 14:31:18 Andy Walls wrote:
> On Mon, 2010-12-13 at 08:32 +0100, Hans Verkuil wrote:
> > On Sunday, December 12, 2010 19:46:33 Andy Walls wrote:
>
> Hi Hans,
>
> > > 1. Why set the vol step to 655, when the volume will actaully step at
> > > increments of 512?
> >
>
Hi,
On 12/13/2010 02:27 PM, Mauro Carvalho Chehab wrote:
Em 13-12-2010 11:04, Jean-Francois Moine escreveu:
I'm not sure about this... On my tests with the two devices I have with ov7660
(sn9c105 and sn9c120), the original driver uses 48 MHz for all resolutions.
My 2 cents:
In my experien
On Mon, Dec 13, 2010 at 01:06:00AM -0800, Dmitry Torokhov wrote:
> On Thu, Dec 09, 2010 at 11:16:47AM -0800, Dmitry Torokhov wrote:
> > On Thu, Dec 09, 2010 at 08:04:36PM +0100, Henrik Rydberg wrote:
> > > On 12/09/2010 10:39 AM, Dmitry Torokhov wrote:
> > >
> > > > The desire to keep old names fo
This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.
Results of the daily build of v4l-dvb:
date:Mon Dec 13 19:00:06 CET 2010
git master: 59365d136d205cc20fe666ca7f89b1c5001b0d5a
git media-master: gcc version: i6
Autodetect input's standard using field frequency detection
feature (FIDT in status byte at 0x1F) of the SAA7113.
Signed-off-by: Anatolij Gustschin
---
drivers/media/video/saa7115.c | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/drivers/media/video/saa7115.c
VIDIOC_QUERYSTD and VIDIOC_G_STD ioctls are currently not
supported in the FSL VIU driver. The decoder subdevice
driver saa7115 extended by previous patch supports QUERYSTD
for saa7113, so we add the appropriate ioctls to the VIU
driver to be able to determine the video input's standard.
Signed-of
On Mon, Dec 13, 2010 at 03:52:20PM +, Catalin Marinas wrote:
> On 10 December 2010 17:03, Russell King - ARM Linux
> wrote:
> > On Fri, Dec 10, 2010 at 12:03:07PM +0100, Janusz Krzysztofik wrote:
> >> void __init omap1_camera_init(void *info)
> >> {
> >> struct platform_device *dev = &
KERNEL_VERSION: 2.6.36
SUBJECT: return from function without mutex_unlock in
drivers/media/video/cx231xx/cx231xx-core.c
SUBSCRIBE:
1. In line 282 in function cx231xx_read_ctrl_reg mutex was locked.
2. If usb_control_msg returns ret<0 then we exit from function
cx231x
I wrote:
> I'll see if I can draw up the ALSA-specific media stuff over the weekend.
Sorry, wrong weekend.
Anyway, below are some remarks and a patch.
* Entity types
TYPE_NODE was renamed to TYPE_DEVICE because "node" sounds like a node
in a graph, which does not distinguish it from other enti
KERNEL_VERSION: 2.6.36
SUBJECT: double mutex_lock in drivers/media/video/tlg2300/pd-video.c
in function vidioc_s_fmt
SUBSCRIBE:
First mutex_unlock in function pd_vidioc_s_fmt in line 767:
764ret |= send_set_req(pd, VIDEO_ROSOLU_SEL,
765
On 10 December 2010 17:03, Russell King - ARM Linux
wrote:
> On Fri, Dec 10, 2010 at 12:03:07PM +0100, Janusz Krzysztofik wrote:
>> void __init omap1_camera_init(void *info)
>> {
>> struct platform_device *dev = &omap1_camera_device;
>> + dma_addr_t paddr = omap1_camera_phys_mempool_ba
Manju,
>2. Fixed Murali's comments on moving davinci_vpbe_readme.txt to different
>patch
different patch or path? My comment was to move the documentation to
Documentation folder. But it is still in it's original path :(
>
>Manjunath Hadli (6):
> davinci vpbe: V4L2 display driver for DM644X So
On Sun, Dec 12, 2010 at 05:13:47PM +0100, Torsten Kaiser wrote:
> On Sun, Dec 12, 2010 at 2:15 PM, Dave Young wrote:
> > oops happen in bttv_open while locking uninitialized mutex fh->cap.vb_lock
> > add mutex_init before usage
>
> I have seen the same problem twice since I switched of the BKL in
I use several (from three to five) saa7134-based cards on single PC. Currently
I'm trying to migrate from 2.6.22 to 2.6.32 (ubuntu lts).
I've got problems which I did not have with 2.6.22 kernel:
1. Depending on configuration load average holds 1 or 2 when saa7134 module is
loaded. The reason
Em 13-12-2010 11:02, Jean-Francois Moine escreveu:
> Here is an other way to fix the inv powerdown bug.
Didn't test yet, but it seems that this series will properly address the issue.
>
> These patches are not tested yet.
>
> Jean-François Moine (6):
> gspca - sonixj: Move bridge init to s
On Mon, 2010-12-13 at 08:32 +0100, Hans Verkuil wrote:
> On Sunday, December 12, 2010 19:46:33 Andy Walls wrote:
Hi Hans,
> > 1. Why set the vol step to 655, when the volume will actaully step at
> > increments of 512?
>
> The goal of the exercise is to convert to the control framework. I don'
Em 13-12-2010 11:03, Jean-Francois Moine escreveu:
>
> Signed-off-by: Jean-François Moine
>
> diff --git a/drivers/media/video/gspca/sonixj.c
> b/drivers/media/video/gspca/sonixj.c
> index 5978676..bd5858e 100644
> --- a/drivers/media/video/gspca/sonixj.c
> +++ b/drivers/media/video/gspca/sonix
Em 13-12-2010 11:04, Jean-Francois Moine escreveu:
>
> The initial values of the registers 0x01 and 0x17 are taken from the
> senso table at capture start and updated according to the flag PDN_INV.
>
> Their values are updated at each step of the capture initialization and
> memorized for reuse i
The initial values of the registers 0x01 and 0x17 are taken from the
senso table at capture start and updated according to the flag PDN_INV.
Their values are updated at each step of the capture initialization and
memorized for reuse in capture stop.
This patch also fixed automatically some bad h
Signed-off-by: Jean-François Moine
diff --git a/drivers/media/video/gspca/sonixj.c
b/drivers/media/video/gspca/sonixj.c
index 9b7e28a..4c10324 100644
--- a/drivers/media/video/gspca/sonixj.c
+++ b/drivers/media/video/gspca/sonixj.c
@@ -100,6 +100,19 @@ enum sensors {
/* device flags */
#defin
The flag PDN_INV indicates that the sensor pin S_PWR_DN has not the same
value as other webcams with the same sensor. For now, only two webcams
have been detected so: the Microsoft's VX1000 and VX3000.
Signed-off-by: Jean-François Moine
diff --git a/drivers/media/video/gspca/sonixj.c
b/drivers
Signed-off-by: Jean-François Moine
diff --git a/drivers/media/video/gspca/sonixj.c
b/drivers/media/video/gspca/sonixj.c
index 5978676..bd5858e 100644
--- a/drivers/media/video/gspca/sonixj.c
+++ b/drivers/media/video/gspca/sonixj.c
@@ -64,6 +64,7 @@ struct sd {
u8 jpegqual;
Signed-off-by: Jean-François Moine
diff --git a/drivers/media/video/gspca/sonixj.c
b/drivers/media/video/gspca/sonixj.c
index 4660cbe..5978676 100644
--- a/drivers/media/video/gspca/sonixj.c
+++ b/drivers/media/video/gspca/sonixj.c
@@ -1794,7 +1794,7 @@ static int sd_init(struct gspca_dev *gspc
Signed-off-by: Jean-François Moine
diff --git a/drivers/media/video/gspca/sonixj.c
b/drivers/media/video/gspca/sonixj.c
index 2229847..4660cbe 100644
--- a/drivers/media/video/gspca/sonixj.c
+++ b/drivers/media/video/gspca/sonixj.c
@@ -1755,141 +1755,6 @@ static void po2030n_probe(struct gspca_
Here is an other way to fix the inv powerdown bug.
These patches are not tested yet.
Jean-François Moine (6):
gspca - sonixj: Move bridge init to sd start
gspca - sonixj: Fix a bad probe exchange
gspca - sonixj: Add a flag in the driver_info table
gspca - sonixj: Set the f
Hi HyunWoong,
Thanks for catching those YUV order errors.
On 12/13/2010 02:50 AM, Hyunwoong Kim wrote:
> Some color formats are mismatched in s5p-fimc driver.
> CICICTRL[1:0], order422_out, should be set 2b'00 not 2b'11 to use
> V4L2_PIX_FMT_YUYV.
s/CICICTRL[1:0]/CIOCTRL[1:0]
> Because in V4L
The later makes extensive use of structures defined in the former.
Signed-off-by: Laurent Pinchart
---
include/media/v4l2-ctrls.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
Hans, if you're OK with this patch, can you please apply it to your tree and
push it for 2.6.38 ?
diff --
The MIGRATE_CMA migration type has two main characteristics:
(i) only movable pages can be allocated from MIGRATE_CMA
pageblocks and (ii) page allocator will never change migration
type of MIGRATE_CMA pageblocks.
This guarantees that page in a MIGRATE_CMA page block can
always be migrated somewher
From: KAMEZAWA Hiroyuki
This commit introduces alloc_contig_free_pages() function
which allocates (ie. removes from buddy system) free pages
in range. Caller has to guarantee that all pages in range
are in buddy system.
Along with alloc_contig_free_pages(), a free_contig_pages()
function is pro
From: KAMEZAWA Hiroyuki
Memory hotplug is a logic for making pages unused in the specified
range of pfn. So, some of core logics can be used for other purpose
as allocating a very large contigous memory block.
This patch moves some functions from mm/memory_hotplug.c to
mm/page_isolation.c. This
This commit adds a bitmap_find_next_zero_area_off() function which
works like bitmap_find_next_zero_area() function expect it allows an
offset to be specified when alignment is checked. This lets caller
request a bit such that its number plus the offset is aligned
according to the mask.
Signed-of
This commit adds a gen_pool_alloc_aligned() function to the
generic allocator API. It allows specifying alignment for the
allocated block. This feature uses
the bitmap_find_next_zero_area_off() function.
It also fixes possible issue with bitmap's last element being
not fully allocated (ie. space
This commit adds CMA memory reservation code to Aquila, Goni and c210
universal boards.
Signed-off-by: Michal Nazarewicz
Signed-off-by: Kyungmin Park
---
arch/arm/mach-s5pv210/mach-aquila.c |2 +
arch/arm/mach-s5pv210/mach-goni.c |2 +
arch/arm/mach-s5pv310/mach-univer
This commit changes various functions that change pages and
pageblocks migrate type between MIGRATE_ISOLATE and
MIGRATE_MOVABLE in such a way as to allow to work with
MIGRATE_CMA migrate type.
Signed-off-by: Michal Nazarewicz
Signed-off-by: Kyungmin Park
---
include/linux/page-isolation.h | 3
This patch adds a "cma" misc device which lets user space use the
CMA API. This device is meant for testing. A testing application
is also provided.
Signed-off-by: Michal Nazarewicz
Signed-off-by: Kyungmin Park
---
drivers/misc/Kconfig | 10 +
drivers/misc/Makefile |1 +
drivers/misc
Hello everyone,
This is yet another version of CMA this time stripped from a lot of
code and with working migration implementation.
The Contiguous Memory Allocator (CMA) makes it possible for
device drivers to allocate big contiguous chunks of memory after
the system has booted.
For mor
The Contiguous Memory Allocator is a set of functions that lets
one initialise a region of memory which then can be used to perform
allocations of contiguous memory chunks from. The implementation
uses MIGRATE_CMA migration type which means that the memory is
shared with standard page allocator, i
GCC complained about update_mmu_cache() not being defined
in migrate.c. Including seems to solve the problem.
Signed-off-by: Michal Nazarewicz
Signed-off-by: Kyungmin Park
---
mm/migrate.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/mm/migrate.c b/mm/migrate.c
in
Hi Sungchun,
On 12/10/2010 03:21 AM, Sungchun Kang wrote:
>
>
>> -Original Message-
>> From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
>> ow...@vger.kernel.org] On Behalf Of Sylwester Nawrocki
>> Sent: Monday, December 06, 2010 6:46 PM
>> To: sungchun.k...@samsung.com
>> Cc
On Thu, Dec 09, 2010 at 11:16:47AM -0800, Dmitry Torokhov wrote:
> On Thu, Dec 09, 2010 at 08:04:36PM +0100, Henrik Rydberg wrote:
> > On 12/09/2010 10:39 AM, Dmitry Torokhov wrote:
> >
> > > The desire to keep old names for the EVIOCGKEYCODE/EVIOCSKEYCODE while
> > > extending them to support lar
50 matches
Mail list logo
