Hi Angela
On Tue, 5 Jul 2011, Angela Wan wrote:
Hi, Guennadi
The solution you said is right. We could use parameters to
distinguish different power managerment, gain, etc.
So ov5642_default_regs_init and ov5642_default_regs_finalise in the
patch could be removed in the final version,
Hi there and sorry for the email,
it seems I am too dumb to edit the wiki and I am at work right now and
there is few time to figure it out.
Device to be added:
Terratec T Stick Dual RC
USB DVB-T Device
Product Page:
http://www.terratec.net/de/produkte/Cinergy_T_Stick_Dual_RC_102260.html
This patch add implicit conversion of single plane variant of ioctl to
multiplane variant. The conversion is performed only in case if a driver
implements only mplane api. The conversion is done by substituting SYS_IOCTL
with a wrapper that converts single plane call to their mplane analogs.
When running in libv4l2 warp mode, the application did not use
v4l2_open and v4l2_close in some cases. This patch fixes this
issue substituting open/close calls with test_open/test_close
which are libv4l2-aware.
Signed-off-by: Tomasz Stanislawski t.stanisl...@samsung.com
Signed-off-by: Kyungmin
When running in libv4l2 warp mode, the application did not use
v4l2_open and v4l2_close in some cases. This patch fixes this
issue substituting open/close calls with test_open/test_close
which are libv4l2-aware.
This is already fixed in the latest version. I found the same
bug recently.
Hi Mauro,
On Wed, Jun 22, 2011 at 09:35:58, Nori, Sekhar wrote:
On Thu, Jun 02, 2011 at 22:51:58, Nori, Sekhar wrote:
Hi Mauro,
On Fri, May 20, 2011 at 19:28:49, Hadli, Manjunath wrote:
move vpif related code for capture and display drivers
from dm646x platform header file to vpif.h
Em 05-07-2011 10:20, Hans Verkuil escreveu:
I failed to see what information is provided by the presets name. If this
were removed
from the ioctl, and fps would be added instead, the API would be clearer.
The only
adjustment would be to use index as the preset selection key. Anyway, it
There has been some discussion recently regarding the preset API:
http://www.mail-archive.com/linux-media@vger.kernel.org/msg33774.html
The current presets are:
#define V4L2_DV_INVALID 0
#define V4L2_DV_480P59_94 1 /* BT.1362 */
#define V4L2_DV_576P50
Em 05-07-2011 10:20, Hans Verkuil escreveu:
I failed to see what information is provided by the presets name. If
this were removed
from the ioctl, and fps would be added instead, the API would be
clearer. The only
adjustment would be to use index as the preset selection key. Anyway,
it is
-Original Message-
From: Oliver Endriss [mailto:o.endr...@gmx.de]
Sent: lundi 4 juillet 2011 00:43
To: Linux Media Mailing List
Cc: Sébastien RAILLARD (COEXSI); Malcolm Priestley
Subject: Re: [DVB] TT S-1500b tuning issue
On Wednesday 29 June 2011 15:16:10 Sébastien RAILLARD
-Original Message-
From: Issa Gorissen [mailto:flo...@usa.net]
Sent: lundi 4 juillet 2011 14:25
To: Sébastien RAILLARD (COEXSI)
Cc: Linux Media Mailing List; abraham.m...@gmail.com
Subject: Re: [DVB] Possible regression in stb6100 module for DVBS2
transponders
On 01/07/2011
Em 06-07-2011 08:31, Hans Verkuil escreveu:
Em 05-07-2011 10:20, Hans Verkuil escreveu:
I failed to see what information is provided by the presets name. If
this were removed
from the ioctl, and fps would be added instead, the API would be
clearer. The only
adjustment would be to use index
On Wednesday 06 July 2011 13:48:35 Mauro Carvalho Chehab wrote:
Em 06-07-2011 08:31, Hans Verkuil escreveu:
Em 05-07-2011 10:20, Hans Verkuil escreveu:
I failed to see what information is provided by the presets name. If
this were removed from the ioctl, and fps would be added instead, the
Em 06-07-2011 09:03, Laurent Pinchart escreveu:
On Wednesday 06 July 2011 13:48:35 Mauro Carvalho Chehab wrote:
Em 06-07-2011 08:31, Hans Verkuil escreveu:
Em 05-07-2011 10:20, Hans Verkuil escreveu:
I failed to see what information is provided by the presets name. If
this were removed from
Greetings from yet another owner of an Asus laptop. Hopefully this is the right
place... patch included.
- device: 04f2:b1e5
- manufacturer: ASUSTeK Computer Inc.
- product: K52JT
--
Mantas
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a
---
lib/libv4lconvert/control/libv4lcontrol.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/lib/libv4lconvert/control/libv4lcontrol.c
b/lib/libv4lconvert/control/libv4lcontrol.c
index 2fddf43..c8a636b 100644
--- a/lib/libv4lconvert/control/libv4lcontrol.c
+++
On Wednesday 06 July 2011 14:09:38 Mauro Carvalho Chehab wrote:
Em 06-07-2011 09:03, Laurent Pinchart escreveu:
On Wednesday 06 July 2011 13:48:35 Mauro Carvalho Chehab wrote:
Em 06-07-2011 08:31, Hans Verkuil escreveu:
Em 05-07-2011 10:20, Hans Verkuil escreveu:
I failed to see what
Em 06-07-2011 08:31, Hans Verkuil escreveu:
Em 05-07-2011 10:20, Hans Verkuil escreveu:
I failed to see what information is provided by the presets name.
If
this were removed
from the ioctl, and fps would be added instead, the API would be
clearer. The only
adjustment would be to use
Em 06-07-2011 09:13, Laurent Pinchart escreveu:
On Wednesday 06 July 2011 14:09:38 Mauro Carvalho Chehab wrote:
Em 06-07-2011 09:03, Laurent Pinchart escreveu:
On Wednesday 06 July 2011 13:48:35 Mauro Carvalho Chehab wrote:
Em 06-07-2011 08:31, Hans Verkuil escreveu:
Em 05-07-2011 10:20, Hans
Em 06-07-2011 09:14, Hans Verkuil escreveu:
Em 06-07-2011 08:31, Hans Verkuil escreveu:
Em 05-07-2011 10:20, Hans Verkuil escreveu:
I failed to see what information is provided by the presets name.
If
this were removed
from the ioctl, and fps would be added instead, the API would be
Hi Mauro,
This pull request adds the bitmask controls, flash API and the adp1653
driver.
Laurent noticed an issue with the previous pull request and I've fixed that.
Changes since the second pull request:
- Properly call validate_new_int() from validate_new() for bitmask controls.
Changes
Em 06-07-2011 09:14, Hans Verkuil escreveu:
Em 06-07-2011 08:31, Hans Verkuil escreveu:
Em 05-07-2011 10:20, Hans Verkuil escreveu:
I failed to see what information is provided by the presets name.
If
this were removed
from the ioctl, and fps would be added instead, the API would be
Hello,
On Tuesday, July 05, 2011 1:34 PM Russell King - ARM Linux wrote:
On Tue, Jul 05, 2011 at 09:41:48AM +0200, Marek Szyprowski wrote:
The Contiguous Memory Allocator is a set of helper functions for DMA
mapping framework that improves allocations of contiguous memory chunks.
CMA
Hello,
On Friday, July 01, 2011 12:18 AM Jonathan Corbet wrote:
On Wed, 29 Jun 2011 16:10:45 +0200
Marek Szyprowski m.szyprow...@samsung.com wrote:
I do still wonder why this is an issue - why not pass the buffers
through
to the driver at VIDIOC_QBUF time? I assume there must be a
On Wednesday 06 July 2011, Marek Szyprowski wrote:
The only problem that might need to be resolved is GFP_ATOMIC allocation
(updating page properties probably requires some locking), but it can be
served from a special area which is created on boot without low-memory
mapping at all. None sane
Em 06-07-2011 09:56, Hans Verkuil escreveu:
Em 06-07-2011 09:14, Hans Verkuil escreveu:
Em 06-07-2011 08:31, Hans Verkuil escreveu:
Em 05-07-2011 10:20, Hans Verkuil escreveu:
I failed to see what information is provided by the presets name.
If
this were removed
from the ioctl, and fps
On Wed, Jul 06, 2011 at 04:09:29PM +0200, Arnd Bergmann wrote:
Maybe you can simply adapt the default location of the contiguous memory
are like this:
- make CONFIG_CMA depend on CONFIG_HIGHMEM on ARM, at compile time
- if ZONE_HIGHMEM exist during boot, put the CMA area in there
- otherwise,
On Wed, 6 Jul 2011, Russell King - ARM Linux wrote:
Another issue is that when a platform has restricted DMA regions,
they typically don't fall into the highmem zone. As the dmabounce
code allocates from the DMA coherent allocator to provide it with
guaranteed DMA-able memory, that would be
On Wednesday 06 July 2011, Russell King - ARM Linux wrote:
On Wed, Jul 06, 2011 at 04:09:29PM +0200, Arnd Bergmann wrote:
Maybe you can simply adapt the default location of the contiguous memory
are like this:
- make CONFIG_CMA depend on CONFIG_HIGHMEM on ARM, at compile time
- if
Hi Linus,
Please pull from:
ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git
v4l_for_linus
For a series of bug fixes:
- mx1-camera were using an uninitialized variable;
- pwc issues at USB disconnect;
- several mceusb and lirc fixes;
-
Hello,
On Wednesday, July 06, 2011 4:09 PM Arnd Bergmann wrote:
On Wednesday 06 July 2011, Marek Szyprowski wrote:
The only problem that might need to be resolved is GFP_ATOMIC allocation
(updating page properties probably requires some locking), but it can be
served from a special area
On Wednesday 06 July 2011, Nicolas Pitre wrote:
On Wed, 6 Jul 2011, Russell King - ARM Linux wrote:
Another issue is that when a platform has restricted DMA regions,
they typically don't fall into the highmem zone. As the dmabounce
code allocates from the DMA coherent allocator to
Hello Mauro,
The following changes since commit 66ef90675ad5e45717ff84e4a106c0d22e690803:
[media] DocBook/v4l: Document the new system-wide version behavior
(2011-06-29 17:45:31 -0300)
are available in the git repository at:
git://git.infradead.org/users/kmpark/linux-2.6-samsung
Hi Mauro,
Recently I have send the MFC 5.1 driver v10 with necessary v4l2 patches.
The following changes since commit df6aabbeb2b8799d97f3886fc994c318bc6a6843:
[media] v4l2-ctrls.c: add support for V4L2_EVENT_SUB_FL_ALLOW_FEEDBACK
(2011-07-01 20:54:51 -0300)
are available in the git
Em 06-07-2011 11:55, Mauro Carvalho Chehab escreveu:
Hi Linus,
Please pull from:
ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git
v4l_for_linus
For a series of bug fixes:
- mx1-camera were using an uninitialized variable;
- pwc issues at USB
On Wed, Jul 06, 2011 at 04:56:23PM +0200, Marek Szyprowski wrote:
This will not solve our problems. We need CMA also to create at least one
device private area that for sure will be in low memory (video codec).
You make these statements but you don't say why. Can you please
explain why the
Hello,
On Wednesday, July 06, 2011 5:37 PM Russell King - ARM Linux wrote:
On Wed, Jul 06, 2011 at 04:56:23PM +0200, Marek Szyprowski wrote:
This will not solve our problems. We need CMA also to create at least one
device private area that for sure will be in low memory (video codec).
On Wed, Jul 06, 2011 at 04:51:49PM +0200, Arnd Bergmann wrote:
On Wednesday 06 July 2011, Russell King - ARM Linux wrote:
On Wed, Jul 06, 2011 at 04:09:29PM +0200, Arnd Bergmann wrote:
Maybe you can simply adapt the default location of the contiguous memory
are like this:
- make
Hi Stefan,
I'm validating if all drivers are behaving equally with respect to the
error codes returned to userspace, and double-checking with the API.
On almost all places, -EFAULT code is used only to indicate when
copy_from_user/copy_to_user fails. However, firedtv uses a lot of
-EFAULT, where
On Wed, 06 Jul 2011 18:05:00 +0200, Christoph Lameter c...@linux.com wrote:
ZONE_DMA is a zone for memory of legacy (crippled) devices that cannot
DMA into all of memory (and so is ZONE_DMA32). Memory from ZONE_NORMAL
can be used for DMA as well and a fully capable device would be expected
to
On Wed, 6 Jul 2011, Russell King - ARM Linux wrote:
they typically don't fall into the highmem zone. As the dmabounce
code allocates from the DMA coherent allocator to provide it with
guaranteed DMA-able memory, that would be rather inconvenient.
True. The dmabounce code would
On Wed, 6 Jul 2011, Michal Nazarewicz wrote:
On Wed, 06 Jul 2011 18:05:00 +0200, Christoph Lameter c...@linux.com wrote:
ZONE_DMA is a zone for memory of legacy (crippled) devices that cannot DMA
into all of memory (and so is ZONE_DMA32). Memory from ZONE_NORMAL
can be used for DMA as
On 07/05/11 17:35, Jonathan Cameron wrote:
On 07/05/11 16:22, Jonathan Cameron wrote:
On 07/05/11 16:02, Laurent Pinchart wrote:
On Tuesday 05 July 2011 16:38:07 Sakari Ailus wrote:
On Tue, Jul 05, 2011 at 02:48:57PM +0100, Jonathan Cameron wrote:
On 07/05/11 13:19, Sakari Ailus wrote:
On
On Wednesday 06 July 2011, Russell King - ARM Linux wrote:
On Wed, Jul 06, 2011 at 04:51:49PM +0200, Arnd Bergmann wrote:
On Wednesday 06 July 2011, Russell King - ARM Linux wrote:
I don't see how. The pages get allocated from an unmapped area
or memory, mapped into the kernel address
On Wed, Jul 06, 2011 at 11:05:00AM -0500, Christoph Lameter wrote:
On Wed, 6 Jul 2011, Russell King - ARM Linux wrote:
they typically don't fall into the highmem zone. As the dmabounce
code allocates from the DMA coherent allocator to provide it with
guaranteed DMA-able memory,
Set v4l2_subdev flags for a host driver to create a sub-device
node for the driver so the subdev can be directly configured
by applications.
Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
---
Do not resume the device during system resume if it was idle
before system suspend, as this causes resume from suspend
to RAM failures on exynos4. For this purpose runtime PM and
system sleep helpers are separated.
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
Signed-off-by: Kyungmin
The following are a few updates for s5p-csis MIPI-CSI receiver driver.
I have originally missed the fact there are multiple voltages to be
supplied externally for the MIPI-CSI receiver and PHY and the driver
have to make sure they are all enabled at PMIC. The patch 1/3 fixes
it by adding a
On the SoCs this driver is intended to support the are three
separate pins to supply the MIPI-CSIS subsystem: 1.1V or 1.2V,
1.8V and power supply for an internal PLL.
This patch adds support for two separate voltage supplies
to cover properly board configurations where PMIC requires
to configure
On Wed, Jul 06, 2011 at 11:19:00AM -0500, Christoph Lameter wrote:
What I described is the basic memory architecture of Linux. I am not that
familiar with ARM and the issue discussed here. Only got involved because
ZONE_DMA was mentioned. The nature of ZONE_DMA is often misunderstood.
The
Mauro Carvalho Chehab wrote:
I'm validating if all drivers are behaving equally with respect to the
error codes returned to userspace, and double-checking with the API.
On almost all places, -EFAULT code is used only to indicate when
copy_from_user/copy_to_user fails. However, firedtv uses a
Hi.
I think that you could reuse lots of code with smart suspend / resume.
What do you think about this DVB power saving case (about the concept, don't
look at details, please):
- One device has responsibility to do the power off when it can be done
(mantis_core.ko)
- In my case there is
While here, removes the bogus EINTERNAL error codes.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git a/Documentation/DocBook/media/dvb/video.xml
b/Documentation/DocBook/media/dvb/video.xml
index 0b1b662..25fb823 100644
--- a/Documentation/DocBook/media/dvb/video.xml
+++
Move generic stuff into gen-errors.xml, and remove them from
DVB API. While here, removes two bogus error codes that aren't
supported or used on Linux: EINTERNAL and ENOSIGNAL.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git a/Documentation/DocBook/media/dvb/dvbproperty.xml
Be sure that all VIDIOC_* ioctl are using the return error macro, and
aren't specifying generic error codes internally.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git a/Documentation/DocBook/media/v4l/gen-errors.xml
b/Documentation/DocBook/media/v4l/gen-errors.xml
index
The EBUSY is already described as a generic error condition, with a
similar text.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git a/Documentation/DocBook/media/v4l/media-ioc-setup-link.xml
b/Documentation/DocBook/media/v4l/media-ioc-setup-link.xml
index cec97af..fc2e522
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git a/Documentation/DocBook/media/v4l/lirc_device_interface.xml
b/Documentation/DocBook/media/v4l/lirc_device_interface.xml
index 0e0453f..a060f3f 100644
--- a/Documentation/DocBook/media/v4l/lirc_device_interface.xml
+++
V4L ioctl function descripton also has a generic error chapter.
Remove it, as it is now obsoleted by a general, multi-API generic
error descriptions.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git a/Documentation/DocBook/media/v4l/func-ioctl.xml
Instead of having their own generic error codes at the MC API, move
its section to the generic one and be sure that all media ioctl's
will point to it.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git a/Documentation/DocBook/media/v4l/gen-errors.xml
Add a reference for the generic error code chapter to LIRC ioctl
description.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git a/Documentation/DocBook/media/v4l/lirc_device_interface.xml
b/Documentation/DocBook/media/v4l/lirc_device_interface.xml
index a060f3f..8d7eb6b 100644
Just like the V4L, MC and LIRC API's, point to the generic error
chapter for ioctl's. This will allow moving generic error codes
to just one place inside all media API's.
A latter patch will remove the generic errors from each specific
ioctl.
Signed-off-by: Mauro Carvalho Chehab
Remove generic errors from ioctl() descriptions. For other ioctl's,
there's no generic section. So, just keep whatever is there.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git a/Documentation/DocBook/media/dvb/demux.xml
b/Documentation/DocBook/media/dvb/demux.xml
index
-EFAULT is used to indicate that there were a problem when copying
data from/to userspace. Don't mix it with I2C bus error (-EIO).
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git a/drivers/media/dvb/frontends/nxt6000.c
b/drivers/media/dvb/frontends/nxt6000.c
index
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git a/drivers/media/dvb/siano/smscoreapi.c
b/drivers/media/dvb/siano/smscoreapi.c
index 78765ed..7331e84 100644
--- a/drivers/media/dvb/siano/smscoreapi.c
+++ b/drivers/media/dvb/siano/smscoreapi.c
@@ -1147,7 +1147,7 @@ static int
Currently, -EINVAL is used to return either when an IOCTL is not
implemented, or if the ioctl was not implemented.
Note: Drivers that don't use video_ioctl2, will need extra patches.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git
When a device (or their PCI structs) are not found, the error should
be -ENODEV. -EFAULT is reserved for errors while copying arguments
from/to userspace.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git a/drivers/media/dvb/bt8xx/dvb-bt8xx.c
There are several errors reported by V4L that aren't described.
They can occur on almost all ioctl's. Instead of adding them
into each ioctl, create a new chapter.
For V4L, the new chapter will automatically be listed on all
places, as there's a macro used everywhere there.
Signed-off-by: Mauro
This patch series contain some fixes on how error codes are handled
at the media API's. It consists on two parts.
The first part have the DocBook changes:
- Create a generic errno xml file, used by all media API's
(V4L, MC, LIRC and DVB);
- Move the generic errorcodes to the new file;
-
Remove generic errors from ioctl() descriptions. For other ioctl's,
there's no generic section. So, just keep whatever is there.
Also remove the EINTERNAL error code, as no DVB driver returns
it, and this error code is not defined on POSIX or on Linux.
Signed-off-by: Mauro Carvalho Chehab
Those drivers are not relying at the V4L2 core to handle the ioctl's.
So, we need to manually patch them every time a change goes to the
core.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git a/drivers/media/video/et61x251/et61x251_core.c
On Wed, Jul 6, 2011 at 1:53 PM, Marko Ristola marko.rist...@kolumbus.fi wrote:
Hi.
I think that you could reuse lots of code with smart suspend / resume.
What do you think about this DVB power saving case (about the concept, don't
look at details, please):
- One device has responsibility
Hi Stefan,
Em 06-07-2011 14:33, Stefan Richter escreveu:
Mauro Carvalho Chehab wrote:
I'm validating if all drivers are behaving equally with respect to the
error codes returned to userspace, and double-checking with the API.
On almost all places, -EFAULT code is used only to indicate when
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:Wed Jul 6 19:00:35 CEST 2011
git hash:df6aabbeb2b8799d97f3886fc994c318bc6a6843
gcc version: i686-linux-gcc (GCC)
Mauro Carvalho Chehab wrote:
I'm validating if all drivers are behaving equally with respect to the
error codes returned to userspace, and double-checking with the API.
On almost all places, -EFAULT code is used only to indicate when
copy_from_user/copy_to_user fails. However, firedtv uses a
On Wed, 6 Jul 2011, Russell King - ARM Linux wrote:
So, ARM is no different from x86, with the exception that the 16MB DMA
zone due to ISA ends up being different sizes on ARM depending on our
restrictions.
Sounds good. Thank you.
--
To unsubscribe from this list: send the line unsubscribe
On Wed, 6 Jul 2011, Arnd Bergmann wrote:
On Wednesday 06 July 2011, Russell King - ARM Linux wrote:
On Wed, Jul 06, 2011 at 04:51:49PM +0200, Arnd Bergmann wrote:
On Wednesday 06 July 2011, Russell King - ARM Linux wrote:
I don't see how. The pages get allocated from an unmapped area
Hi all,
attached are the updates for dvb-t scan files valid for Slovakia.
Kind regards
Peter Butkovic
diff -r 148ede2a6809 util/scan/dvb-t/sk-BanskaBystrica
--- a/util/scan/dvb-t/sk-BanskaBystrica Tue Jun 28 07:50:24 2011 +0200
+++ b/util/scan/dvb-t/sk-BanskaBystrica Wed Jul 06 21:25:01 2011
Em 06-07-2011 09:14, Hans Verkuil escreveu:
Em 06-07-2011 08:31, Hans Verkuil escreveu:
Em 05-07-2011 10:20, Hans Verkuil escreveu:
I failed to see what information is provided by the presets name.
If
this were removed
from the ioctl, and fps would be added instead, the API would be
06.07.2011 21:17, Devin Heitmueller kirjoitti:
On Wed, Jul 6, 2011 at 1:53 PM, Marko Ristola marko.rist...@kolumbus.fi
wrote:
All that said, I believe that you are correct in that the business
logic needs to ultimately be decided by the bridge driver, rather than
having the dvb/tuner core
On Wednesday 06 July 2011 21:10:07 Nicolas Pitre wrote:
If you get a highmem page, because the cache is VIPT, that page might
still be cached even if it wasn't mapped. With a VIVT cache we must
flush the cache whenever a highmem page is unmapped. There is no such
restriction with VIPT
On Wed, 2011-07-06 at 13:34 +0200, Sébastien RAILLARD (COEXSI) wrote:
-Original Message-
From: Oliver Endriss [mailto:o.endr...@gmx.de]
Sent: lundi 4 juillet 2011 00:43
To: Linux Media Mailing List
Cc: Sébastien RAILLARD (COEXSI); Malcolm Priestley
Subject: Re: [DVB] TT
On Tue, 5 Jul 2011, JAIN, AMBER wrote:
diff --git a/drivers/media/video/omap24xxcam.c
b/drivers/media/video/omap24xxcam.c
index f6626e8..d92d4c6 100644
--- a/drivers/media/video/omap24xxcam.c
+++ b/drivers/media/video/omap24xxcam.c
@@ -309,11 +309,11 @@ static int
Hi all,
I have hacked together a patch, which adds support for mediabus in
adv7175 driver. I am not sending
this out as a patch series instead I show you one (big) patch with
questions about my code. Also
I want to note that I am not quite sure if I introduced the correct
formats and the
Hi Sylwester,
On Wednesday 06 July 2011 19:13:39 Sylwester Nawrocki wrote:
On the SoCs this driver is intended to support the are three
separate pins to supply the MIPI-CSIS subsystem: 1.1V or 1.2V,
1.8V and power supply for an internal PLL.
This patch adds support for two separate voltage
On Tue, 5 Jul 2011 14:07:17 +0200
Arnd Bergmann a...@arndb.de wrote:
On Tuesday 05 July 2011, Marek Szyprowski wrote:
This is yet another round of Contiguous Memory Allocator patches. I hope
that I've managed to resolve all the items discussed during the Memory
Management summit at Linaro
This patch add suport for the dvb-t part of CT-3650.
Jose Alberto
Signed-off-by: Jose Alberto Reguero jaregu...@telefonica.net
diff -ur linux/drivers/media/common/tuners/tda827x.c linux.new/drivers/media/common/tuners/tda827x.c
--- linux/drivers/media/common/tuners/tda827x.c 2010-07-03
Hi Javier,
On Monday 04 July 2011 13:25:10 javier Martin wrote:
Hi, Laurent.
How is it going?
Is there any chance these changes to be included for next release?
We are afraid that changes in the framework may turn the patches useless.
I've applied the patch to my tree and I'm working on a
On Wed, 6 Jul 2011, Arnd Bergmann wrote:
On Wednesday 06 July 2011 21:10:07 Nicolas Pitre wrote:
If you get a highmem page, because the cache is VIPT, that page might
still be cached even if it wasn't mapped. With a VIVT cache we must
flush the cache whenever a highmem page is unmapped.
-Original Message-
From: David Rientjes [mailto:rient...@google.com]
Sent: Thursday, July 07, 2011 2:14 AM
To: JAIN, AMBER
Cc: Mauro Carvalho Chehab; Hiremath, Vaibhav; linux-media@vger.kernel.org;
Andrew Morton
Subject: RE: [GIT PULL for v3.0] OMAP_VOUT bug fixes and code cleanup
-Original Message-
From: Hiremath, Vaibhav
Sent: Thursday, July 07, 2011 11:25 AM
To: David Rientjes; JAIN, AMBER
Cc: Mauro Carvalho Chehab; linux-media@vger.kernel.org; Andrew Morton
Subject: RE: [GIT PULL for v3.0] OMAP_VOUT bug fixes and code cleanup
-Original
90 matches
Mail list logo
