OK, the discussion in response to my RFC was very enlightening. Based on
that I decided on the following roadmap:
1) Remove the sysfs code from the framework for the time being.
It is not necessary for the first version. What I would like to do is to take
another good look at the data structures
Hi,
I know that this is off topic because (alas) the i.MX51 support is not
in the mainline kernel. However, if anyone is working with the camera
sensor interfaces on this device I would be very interested to talk to
them, on list or off, because I am stuck! CSI1 works fine, but CSI2
refuses
On Thu, Apr 08, 2010 at 02:10:40AM -0300, Mauro Carvalho Chehab wrote:
David Härdeman wrote:
o The RX decoding is now handled via a workqueue (I can break that up into a
separate patch later, but I think it helps the discussion to have it in
for
now), with inspiration from Andy's
Attached is a working scan file for uk-Aberdare post switchover
uk-Aberdare_dso
Description: Binary data
drivers/media/IR/ir-raw-event.c is currently written with the assumption
that all raw hardware will generate events only on state change (i.e.
when a pulse or space starts).
However, some hardware (like mceusb, probably the most popular IR receiver
out there) only generates duration data (and
Remove unused #include linux/version.h('s) in
drivers/media/dvb/ngene/ngene-core.c
Signed-off-by: Huang Weiyi weiyi.hu...@gmail.com
---
drivers/media/dvb/ngene/ngene-core.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/media/dvb/ngene/ngene-core.c
Hi Hans,
Hans Verkuil wrote:
BTW, I've also completely overhauled the vivi driver. I've used it to test
the control handling, but I took the opportunity to do a big clean up of that
driver. The combination of vivi + qv4l2 made testing of the more unusual
integer64 and string control types much
Remove unused #include linux/version.h('s) in
drivers/media/video/davinci/vpif_capture.c
drivers/media/video/davinci/vpif_display.c
Signed-off-by: Huang Weiyi weiyi.hu...@gmail.com
---
drivers/media/video/davinci/vpif_capture.c |1 -
drivers/media/video/davinci/vpif_display.c |1 -
2
David Härdeman wrote:
Your're fast!
OK, the code looks good. I'll test and apply it, if it passes on the test.
The only missed thing is the comment about the kfifo size (see the email
I just sent). If you prefer, I can add a one line comment when applying it,
to avoid you to re-send the code.
David Härdeman wrote:
drivers/media/IR/ir-raw-event.c is currently written with the assumption
that all raw hardware will generate events only on state change (i.e.
when a pulse or space starts).
However, some hardware (like mceusb, probably the most popular IR receiver
out there) only
On Thu, Apr 8, 2010 at 1:10 AM, Mauro Carvalho Chehab
mche...@infradead.org wrote:
David Härdeman wrote:
drivers/media/IR/ir-raw-event.c is currently written with the assumption
that all raw hardware will generate events only on state change (i.e.
when a pulse or space starts).
However, some
I'm trying to detect when a user unplugs a camera while I'm doing
v4l2_read, but even when I get logs like this:
libv4l2: error queuing buf 0: No such device
libv4l2: error queuing buf 1: No such device
libv4l2: error queuing buf 2: No such device
libv4l2: error dequeuing buf: Input/output error
Jon Smirl wrote:
On Thu, Apr 8, 2010 at 1:10 AM, Mauro Carvalho Chehab
mche...@infradead.org wrote:
David Härdeman wrote:
drivers/media/IR/ir-raw-event.c is currently written with the assumption
that all raw hardware will generate events only on state change (i.e.
when a pulse or space
David Härdeman wrote:
On Thu, Apr 08, 2010 at 08:50:48AM -0300, Mauro Carvalho Chehab wrote:
- size = sizeof(struct ir_raw_event) * MAX_IR_EVENT_SIZE * 2;
- size = roundup_pow_of_two(size);
+ ir-raw-input_dev = input_dev;
+ INIT_WORK(ir-raw-rx_work, ir_raw_event_work);
- rc =
On Thu, Apr 8, 2010 at 7:50 AM, Huang Weiyi weiyi.hu...@gmail.com wrote:
Remove unused #include linux/version.h('s) in
drivers/media/dvb/ngene/ngene-core.c
Signed-off-by: Huang Weiyi weiyi.hu...@gmail.com
---
drivers/media/dvb/ngene/ngene-core.c | 1 -
1 files changed, 0 insertions(+),
On Thu, Apr 08, 2010 at 10:06:53AM -0300, Mauro Carvalho Chehab wrote:
Jon Smirl wrote:
On Thu, Apr 8, 2010 at 1:10 AM, Mauro Carvalho Chehab
mche...@infradead.org wrote:
On the previous code, it is drivers responsibility to call the
function that
de-queue. On saa7134, I've scheduled
drivers/media/IR/ir-raw-event.c is currently written with the assumption
that all raw hardware will generate events only on state change (i.e.
when a pulse or space starts).
However, some hardware (like mceusb, probably the most popular IR receiver
out there) only generates duration data (and
David Härdeman wrote:
On Thu, Apr 08, 2010 at 10:06:53AM -0300, Mauro Carvalho Chehab wrote:
Jon Smirl wrote:
On Thu, Apr 8, 2010 at 1:10 AM, Mauro Carvalho Chehab
mche...@infradead.org wrote:
On the previous code, it is drivers responsibility to call the
function that
de-queue. On
Am 08.04.2010 02:47, schrieb Mike Isely:
On Thu, 8 Apr 2010, hermann pitton wrote:
Hi,
Am Mittwoch, den 07.04.2010, 20:50 +0200 schrieb Lars Hanisch:
Am 06.04.2010 16:33, schrieb Mike Isely:
[snip]
Mike, do you know of anyone actively using that additional information?
Yes.
The VDR
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:Thu Apr 8 19:00:16 CEST 2010
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 14561:7c0b887911cf
git master:
From: David Härdeman da...@hardeman.nu
drivers/media/IR/ir-raw-event.c is currently written with the assumption
that all raw hardware will generate events only on state change (i.e.
when a pulse or space starts).
However, some hardware (like mceusb, probably the most popular IR receiver
out
drivers/media/IR/ir-sysfs.c: In function ‘store_protocol’:
drivers/media/IR/ir-sysfs.c:93: warning: suggest parentheses around assignment
used as truth value
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
diff --git a/drivers/media/IR/ir-sysfs.c b/drivers/media/IR/ir-sysfs.c
index
Hardware decoders have a more limited set of decoders than software ones.
In general, they support just one protocol at a given time, but allow
changing between a few options.
Rename the previous badly named current_protocol as just protocol,
meaning the current protocol(s) accepted by the
The patch that adds the rc-map changes didn't take into account that an
a table with IR_TYPE_UNKNOWN would make change_protocol to return -EINVAL.
As this function is fundamental to initialize some data, including a
callback to the getkey function, this caused the driver to stop working,
hanging
Some spinlocks are not properly initialized on ir core:
[ 471.714132] BUG: spinlock bad magic on CPU#0, modprobe/1899
[ 471.719838] lock: f92a08ac, .magic: , .owner: none/-1,
.owner_cpu: 0
[ 471.727301] Pid: 1899, comm: modprobe Not tainted 2.6.33 #36
[ 471.733062] Call Trace:
[
From: David Härdeman da...@hardeman.nu
When the remote controller class is anyway being renamed from ir to rc
this would be a good time to also rename the devices from rcrcvX to rcX.
I know we haven't reached any agreement on whether transmission will
eventually be handled by the same device,
Yet another series of ir-core improvements.
This series contain two fixes, plus those improvements:
1) sysfs: better define the behaviour for in-hardware and in-software raw
decoders: different types require different functionalities;
2) sysfs: rename Remote Controllers as rc0, rc1, ...
Some devices have in-hardware Remote Controller decoder, while others
need a software decoder to get the IR code. As each software decoder
can be enabled/disabled individually, allowing multiple protocol
decoding capability.
On the other hand, hardware decoders have a limited protocol
support,
Signed-off-by: Muralidharan Karicheri mkarich...@gmail.com
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
phone: 301-407-9583
email: m-kariche...@ti.com
-Original Message-
From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
Mauro Carvalho Chehab wrote:
ir-core.h has the kABI to be used by the bridge drivers, when needing to
register
IR protocols and pass IR events. However, the same file also contains IR
subsystem
internal calls, meant to be used inside ir-core and between ir-core and the
raw
decoders.
da...@hardeman.nu wrote:
This patch converts drivers/media/dvb/ttpci/budget-ci.c to use ir-core
rather than rolling its own keydown timeout handler and reporting keys
via drivers/media/IR/ir-functions.c.
Hmm... had you test this patch? It got me an error here:
This patch adds RC5x support to drivers/media/IR/ir-rc5-decoder.c
Signed-off-by: David Härdeman da...@hardeman.nu
---
drivers/media/IR/ir-rc5-decoder.c | 78 -
1 files changed, 59 insertions(+), 19 deletions(-)
diff --git a/drivers/media/IR/ir-rc5-decoder.c
This patch adds NECx support to drivers/media/IR/ir-nec-decoder.c
Signed-off-by: David Härdeman da...@hardeman.nu
---
drivers/media/IR/ir-nec-decoder.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/media/IR/ir-nec-decoder.c
This patch adds an RC6 decoder (modes 0 and 6A) to ir-core.
Signed-off-by: David Härdeman da...@hardeman.nu
---
drivers/media/IR/Kconfig |9 +
drivers/media/IR/Makefile |1
drivers/media/IR/ir-core-priv.h |7 +
drivers/media/IR/ir-raw-event.c |1
On Thu, Apr 08, 2010 at 06:59:30PM -0300, Mauro Carvalho Chehab wrote:
da...@hardeman.nu wrote:
This patch converts drivers/media/dvb/ttpci/budget-ci.c to use ir-core
rather than rolling its own keydown timeout handler and reporting keys
via drivers/media/IR/ir-functions.c.
Hmm... had you
Hi David,
David Härdeman wrote:
When I converted drivers/media/dvb/ttpci/budget-ci.c to use ir-core
I missed one line. This patch fixes that mistake.
I did this already (I merged with your commit, at v4l-dvb.git), to avoid
breaking git bisect. I'll backport it to the ir.git tree after
David Härdeman wrote:
On Thu, Apr 08, 2010 at 06:59:30PM -0300, Mauro Carvalho Chehab wrote:
da...@hardeman.nu wrote:
This patch converts drivers/media/dvb/ttpci/budget-ci.c to use ir-core
rather than rolling its own keydown timeout handler and reporting keys
via
Em 01-04-2010 01:33, Dmitri Belimov escreveu:
Hi Hermann
Hi Dimitry,
Am Mittwoch, den 31.03.2010, 13:14 +1000 schrieb Dmitri Belimov:
Hi Hermann
Hi,
Am Dienstag, den 30.03.2010, 16:02 +1000 schrieb Dmitri Belimov:
Hi
The hybrid tuner FMD1216MEX_MK3 after cold start has disabled
IF.
To get additional details, samples and counts for our USA contact data please
email me at this address katelyn.r...@optinlists.co.cc
we have lots of different lists in many fields and this week is the time to buy
with lowered list prices.
have a look at this if you don't like to recieve
Jean Delvare wrote:
Hi Mauro,
On Tue, 06 Apr 2010 02:34:46 -0300, Mauro Carvalho Chehab wrote:
Jean Delvare wrote:
On Mon, 05 Apr 2010 15:26:32 -0300, Mauro Carvalho Chehab wrote:
Please, don't add new things at ir-common module. It basically contains the
decoding functions for RC5 and
istva...@mailbox.hu wrote:
This patch adds support for V4L2_CID_SHARPNESS by changing the luma peak
filter and notch filter. It can be set in the range 0 to 9, with 0 being
the original and default mode.
One minor problem is that other code that sets the registers being used
(for example when
41 matches
Mail list logo