This adds the tw68 PCI driver.
These two patches are identical to the v3 patch series I posted earlier:
http://comments.gmane.org/gmane.linux.drivers.video-input-infrastructure/81407
Regards,
Hans
The following changes since commit b250392f7b5062cf026b1423e27265e278fd6b30:
[media]
Hi Mauro,
This adds the new vivid driver as a replacement for the old vivi.
This pull request is identical to the v2 patch series posted earlier:
http://comments.gmane.org/gmane.linux.drivers.video-input-infrastructure/81354
except for the final patch that removes the vivi driver which is new
Hi Mauro,
This pull request converts the cx23885 driver to the latest V4L2 core
frameworks, removing about 1000 lines in the process.
It now passes the v4l2-compliance tests and, frankly, feels much more
robust.
I have tested this with my HVR-1800 board with video (compressed and
uncompressed),
, but the error still persists in next-20140829
also.
drivers/media/radio/radio-miropcm20.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/radio/radio-miropcm20.c
b/drivers/media/radio/radio-miropcm20.c
index 998919e..3309f7c 100644
--- a/drivers/media/radio/radio-miropcm20.c
moikka,
Start polling thread, which polls once per 2 sec or so, which reads RSSI
and writes value to struct dtv_frontend_properties. That it is, in my
understanding. Same for all those DVBv5 stats. Mauro knows better as he
designed that functionality.
I understand that RSSI property should
The following changes since commit b250392f7b5062cf026b1423e27265e278fd6b30:
[media] media: ttpci: fix av7110 build to be compatible with
CONFIG_INPUT_EVDEV (2014-08-21 15:25:38 -0500)
are available in the git repository at:
git://linuxtv.org/hverkuil/media_tree.git cx18
for you to fetch
We still have too many sparse warnings, so this is another round of sparse
warning cleanups.
Regards,
Hans
The following changes since commit b250392f7b5062cf026b1423e27265e278fd6b30:
[media] media: ttpci: fix av7110 build to be compatible with
CONFIG_INPUT_EVDEV (2014-08-21
On 08/29/2014 01:21 PM, Hans Verkuil wrote:
We still have too many sparse warnings, so this is another round of sparse
warning cleanups.
I forgot to mention that this pull request combines these two patch series:
https://www.mail-archive.com/linux-media@vger.kernel.org/msg78429.html
This is based on reg and reg-names in DT.
Example:
reg = 0x10 0x20 0x30;
reg-names = main, io, test;
This function will create dummy devices io and test
with addresses 0x20 and 0x30 respectively.
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb...@vodalys.com
---
drivers/i2c/i2c-core.c |
This patch uses DT in order to parse addresses for dummy devices of adv7604.
If nothing is defined, it uses default addresses.
The main prupose is using two adv76xx on the same i2c bus.
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb...@vodalys.com
---
Hi Kamil,
after a discussion on IRC, we concluded that s5p-mfc have this bug that
disallow multiple reqbufs calls before streaming. This has the impact
that it forces to call REQBUFS(0) before setting the new number of
buffers during re-negotiation, and is against the spec too.
As an
On 08/29/2014 03:28 PM, Jean-Michel Hautbois wrote:
This patch uses DT in order to parse addresses for dummy devices of adv7604.
If nothing is defined, it uses default addresses.
The main prupose is using two adv76xx on the same i2c bus.
Signed-off-by: Jean-Michel Hautbois
Hi,
On Fri, Aug 29, 2014 at 02:28:17PM +0100, Jean-Michel Hautbois wrote:
This patch uses DT in order to parse addresses for dummy devices of adv7604.
If nothing is defined, it uses default addresses.
The main prupose is using two adv76xx on the same i2c bus.
This is rather opaque.
It seems
This patch uses DT in order to parse addresses for dummy devices of adv7604.
The ADV7604 has thirteen 256-byte maps that can be accessed via the main
I²C ports. Each map has it own I²C address and acts
as a standard slave device on the I²C bus.
If nothing is defined, it uses default addresses.
This is based on reg and reg-names in DT.
Example:
reg = 0x10 0x20 0x30;
reg-names = main, io, test;
This function will create dummy devices io and test
with addresses 0x20 and 0x30 respectively.
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb...@vodalys.com
---
drivers/i2c/i2c-core.c |
On 08/29/2014 05:15 PM, Jean-Michel Hautbois wrote:
This is based on reg and reg-names in DT.
Example:
reg = 0x10 0x20 0x30;
reg-names = main, io, test;
This function will create dummy devices io and test
with addresses 0x20 and 0x30 respectively.
Signed-off-by: Jean-Michel Hautbois
On 08/29/2014 05:15 PM, Jean-Michel Hautbois wrote:
This is based on reg and reg-names in DT.
Example:
reg = 0x10 0x20 0x30;
reg-names = main, io, test;
This function will create dummy devices io and test
with addresses 0x20 and 0x30 respectively.
Signed-off-by: Jean-Michel Hautbois
Building with the attached random configuration file,
LD init/built-in.o
drivers/built-in.o: In function `technisat_usb2_set_voltage':
technisat-usb2.c:(.text+0x3b4919): undefined reference to `stv090x_set_gpio'
make: *** [vmlinux] Error 1
#
# Automatically generated file; DO NOT EDIT.
#
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: Sat Aug 30 04:00:20 CEST 2014
git branch: test
git hash: b250392f7b5062cf026b1423e27265e278fd6b30
gcc
TO CLAIM YOUR PRICE CONTACT US VIA: sirneedm...@gmail.com
-
Statement of Confidentiality
This message (including attachments) may contain confidential or privileged
information intended for a specific individual or organization. If you have
received this communication
20 matches
Mail list logo
