On Thu, Aug 16, 2012 at 11:15:14PM +0100, Sean Young wrote:
The lirc TX functionality expects the process which writes (TX) data to
the lirc dev to sleep until the actual data has been transmitted by the
hardware.
Since the same timeout calculation is duplicated in more than one driver
On Sat, Aug 25, 2012 at 12:16:04AM +0200, David Härdeman wrote:
On Thu, Aug 16, 2012 at 11:15:14PM +0100, Sean Young wrote:
The lirc TX functionality expects the process which writes (TX) data to
the lirc dev to sleep until the actual data has been transmitted by the
hardware.
Since
On Mon, Aug 20, 2012 at 07:02:47PM -0300, Mauro Carvalho Chehab wrote:
Em 20-08-2012 18:36, David Härdeman escreveu:
On Thu, Aug 16, 2012 at 08:12:34PM -0300, Mauro Carvalho Chehab wrote:
Em 16-08-2012 19:15, Sean Young escreveu:
Could we have a flag in rc_dev to signify whether a driver
On Mon, Aug 20, 2012 at 07:02:47PM -0300, Mauro Carvalho Chehab wrote:
Em 20-08-2012 18:36, David Härdeman escreveu:
On Thu, Aug 16, 2012 at 08:12:34PM -0300, Mauro Carvalho Chehab wrote:
Em 16-08-2012 19:15, Sean Young escreveu:
The lirc TX functionality expects the process which writes
On Mon, Aug 20, 2012 at 06:10:16PM -0400, Devin Heitmueller wrote:
On Mon, Aug 20, 2012 at 6:02 PM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
So, IMO, it makes sense to have a high end API that accepts
writing keystrokes like above, working with both raw drivers
using some kernel IR
On Tue, Aug 21, 2012 at 01:55:12PM +0100, Sean Young wrote:
On Mon, Aug 20, 2012 at 07:02:47PM -0300, Mauro Carvalho Chehab wrote:
Em 20-08-2012 18:36, David Härdeman escreveu:
On Thu, Aug 16, 2012 at 08:12:34PM -0300, Mauro Carvalho Chehab wrote:
Em 16-08-2012 19:15, Sean Young escreveu:
On Thu, Aug 16, 2012 at 08:12:34PM -0300, Mauro Carvalho Chehab wrote:
Em 16-08-2012 19:15, Sean Young escreveu:
The lirc TX functionality expects the process which writes (TX) data to
the lirc dev to sleep until the actual data has been transmitted by the
hardware.
Since the same timeout
Em 20-08-2012 18:36, David Härdeman escreveu:
On Thu, Aug 16, 2012 at 08:12:34PM -0300, Mauro Carvalho Chehab wrote:
Em 16-08-2012 19:15, Sean Young escreveu:
The lirc TX functionality expects the process which writes (TX) data to
the lirc dev to sleep until the actual data has been
On Mon, Aug 20, 2012 at 6:02 PM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
So, IMO, it makes sense to have a high end API that accepts
writing keystrokes like above, working with both raw drivers
using some kernel IR protocol encoders, and with devices that can
accept processed
The lirc TX functionality expects the process which writes (TX) data to
the lirc dev to sleep until the actual data has been transmitted by the
hardware.
Since the same timeout calculation is duplicated in more than one driver
(and would have to be duplicated in even more drivers as they
Em 16-08-2012 19:15, Sean Young escreveu:
The lirc TX functionality expects the process which writes (TX) data to
the lirc dev to sleep until the actual data has been transmitted by the
hardware.
Since the same timeout calculation is duplicated in more than one driver
(and would have to
11 matches
Mail list logo
