Re: [media] rc-core: move timeout and checks to lirc

2012-08-16 Thread Sean Young
> 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

Re: [media] rc-core: move timeout and checks to lirc

2012-08-16 Thread Mauro Carvalho Chehab
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 wou

Re: [media] rc-core: move timeout and checks to lirc

2012-08-20 Thread David Härdeman
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

Re: [media] rc-core: move timeout and checks to lirc

2012-08-20 Thread Mauro Carvalho Chehab
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

Re: [media] rc-core: move timeout and checks to lirc

2012-08-20 Thread Devin Heitmueller
On Mon, Aug 20, 2012 at 6:02 PM, Mauro Carvalho Chehab 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" keystrokes, like H

Re: [media] rc-core: move timeout and checks to lirc

2012-08-21 Thread Sean Young
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

Re: [media] rc-core: move timeout and checks to lirc

2012-08-21 Thread David Härdeman
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 wh

Re: [media] rc-core: move timeout and checks to lirc

2012-08-21 Thread David Härdeman
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 > 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 enc

Re: [media] rc-core: move timeout and checks to lirc

2012-08-21 Thread David Härdeman
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 escr

Re: [media] rc-core: move timeout and checks to lirc

2012-08-24 Thread David Härdeman
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

Re: [media] rc-core: move timeout and checks to lirc

2012-08-24 Thread Sean Young
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.