On Thu, May 29, 2014 at 11:41:53PM -0500, Chase Southwood wrote:
> The addi-data drivers use send_sig() to let the user know when an
> interrupt has occurred. The "standard" way to do this in the comedi
> subsystem is to have a subdevice that supports asynchronous commands
> and use comedi_event()
On Thu, May 29, 2014 at 11:41:53PM -0500, Chase Southwood wrote:
The addi-data drivers use send_sig() to let the user know when an
interrupt has occurred. The standard way to do this in the comedi
subsystem is to have a subdevice that supports asynchronous commands
and use comedi_event() to
On Thursday, May 29, 2014 9:42 PM, Chase Southwood wrote:
> The addi-data drivers use send_sig() to let the user know when an
> interrupt has occurred. The "standard" way to do this in the comedi
> subsystem is to have a subdevice that supports asynchronous commands
> and use comedi_event() to
On Thursday, May 29, 2014 9:42 PM, Chase Southwood wrote:
The addi-data drivers use send_sig() to let the user know when an
interrupt has occurred. The standard way to do this in the comedi
subsystem is to have a subdevice that supports asynchronous commands
and use comedi_event() to signal
The addi-data drivers use send_sig() to let the user know when an
interrupt has occurred. The "standard" way to do this in the comedi
subsystem is to have a subdevice that supports asynchronous commands
and use comedi_event() to signal the user.
Remove the send_sig() usage in this driver.
The addi-data drivers use send_sig() to let the user know when an
interrupt has occurred. The standard way to do this in the comedi
subsystem is to have a subdevice that supports asynchronous commands
and use comedi_event() to signal the user.
Remove the send_sig() usage in this driver.
6 matches
Mail list logo
