On Tue, 4 Sep 2012 13:43:56 +0100, Sean Young s...@mess.org wrote:
This interface is much better but it's also an ABI change. How should
this
be handled? Should rc-core expose it's own /dev/rc[0-9] device with its
own ioctls?
That was the plan yes. I've posted a patchbomb in the past to the
On Fri, Sep 14, 2012 at 10:58:53AM +0300, Timo Kokkonen wrote:
It appears that all modern lirc drivers are now using the rc-core
functionalities to implement the common stuff. When the rx51 lirc driver
was first written, the core was not in place yet. Therefore it is
implementing the file
On 09/03/12 15:36, Sean Young wrote:
On Sun, Sep 02, 2012 at 11:08:20PM +0300, Timo Kokkonen wrote:
On 09/02/12 22:41, Sakari Ailus wrote:
On Sun, Sep 02, 2012 at 06:20:27PM +0300, Timo Kokkonen wrote:
On 09.02 2012 18:06:34, Sakari Ailus wrote:
Heippa,
Timo Kokkonen wrote:
Terve,
On
On Mon, Sep 03, 2012 at 11:41:55PM +0200, David Härdeman wrote:
Hej,
On Mon, Sep 03, 2012 at 01:36:53PM +0100, Sean Young wrote:
On Sun, Sep 02, 2012 at 11:08:20PM +0300, Timo Kokkonen wrote:
I guess the assumption is to avoid
breaking the transmission in the middle in case the process is
On Sun, Sep 02, 2012 at 11:08:20PM +0300, Timo Kokkonen wrote:
On 09/02/12 22:41, Sakari Ailus wrote:
On Sun, Sep 02, 2012 at 06:20:27PM +0300, Timo Kokkonen wrote:
On 09.02 2012 18:06:34, Sakari Ailus wrote:
Heippa,
Timo Kokkonen wrote:
Terve,
On 09/01/12 20:14, Sakari Ailus
Hej,
On Mon, Sep 03, 2012 at 01:36:53PM +0100, Sean Young wrote:
On Sun, Sep 02, 2012 at 11:08:20PM +0300, Timo Kokkonen wrote:
I guess the assumption is to avoid
breaking the transmission in the middle in case the process is signaled.
And that's why we shouldn't use interruptible waits.
Terve,
On 09/01/12 20:14, Sakari Ailus wrote:
Moi,
On Thu, Aug 30, 2012 at 08:54:24PM +0300, Timo Kokkonen wrote:
@@ -273,9 +281,18 @@ static ssize_t lirc_rx51_write(struct file *file, const
char *buf,
/*
* Don't return back to the userspace until the transfer has
- *
Heippa,
Timo Kokkonen wrote:
Terve,
On 09/01/12 20:14, Sakari Ailus wrote:
Moi,
On Thu, Aug 30, 2012 at 08:54:24PM +0300, Timo Kokkonen wrote:
@@ -273,9 +281,18 @@ static ssize_t lirc_rx51_write(struct file *file, const
char *buf,
/*
* Don't return back to the userspace
On 09.02 2012 18:06:34, Sakari Ailus wrote:
Heippa,
Timo Kokkonen wrote:
Terve,
On 09/01/12 20:14, Sakari Ailus wrote:
Moi,
On Thu, Aug 30, 2012 at 08:54:24PM +0300, Timo Kokkonen wrote:
@@ -273,9 +281,18 @@ static ssize_t lirc_rx51_write(struct file *file,
const char *buf,
On Sun, Sep 02, 2012 at 06:20:27PM +0300, Timo Kokkonen wrote:
On 09.02 2012 18:06:34, Sakari Ailus wrote:
Heippa,
Timo Kokkonen wrote:
Terve,
On 09/01/12 20:14, Sakari Ailus wrote:
Moi,
On Thu, Aug 30, 2012 at 08:54:24PM +0300, Timo Kokkonen wrote:
@@ -273,9 +281,18
On 09/02/12 22:41, Sakari Ailus wrote:
On Sun, Sep 02, 2012 at 06:20:27PM +0300, Timo Kokkonen wrote:
On 09.02 2012 18:06:34, Sakari Ailus wrote:
Heippa,
Timo Kokkonen wrote:
Terve,
On 09/01/12 20:14, Sakari Ailus wrote:
Moi,
On Thu, Aug 30, 2012 at 08:54:24PM +0300, Timo Kokkonen
Moi,
On Thu, Aug 30, 2012 at 08:54:24PM +0300, Timo Kokkonen wrote:
@@ -273,9 +281,18 @@ static ssize_t lirc_rx51_write(struct file *file, const
char *buf,
/*
* Don't return back to the userspace until the transfer has
- * finished
+ * finished. However, we wish
The lirc-dev expects the ir-code to be transmitted when the write call
returns back to the user space. We should not leave TX ongoing no
matter what is the reason we return to the user space. Easiest
solution for that is to simply remove interruptible sleeps.
The first wait_event_interruptible is
13 matches
Mail list logo
