Alan Cox wrote:
Or, maybe the userspace program can receive some sort of interrupt
from the TTY device when it is ready for I/O.
Perhaps there is another way to avoid continued polling?
TIOCMIWAIT ioctl for modem signals, and just using poll/select() on the
tty for I/O.
Ah yes, the
Or, maybe the userspace program can receive some sort of interrupt
from the TTY device when it is ready for I/O.
Perhaps there is another way to avoid continued polling?
TIOCMIWAIT ioctl for modem signals, and just using poll/select() on the
tty for I/O.
--
To unsubscribe from this list:
Hi Greg,
On Wed, Jul 1, 2009 at 1:41 AM, Greg KHg...@kroah.com wrote:
Shouldn't the userspace just be monitoring the tty line settings (like
CTS) to know when to start sending data? I wouldn't recommend adding a
new interface to a very old, and standardized, interface.
Does this mean the
Hi,
I'm trying to send a uevent from my USB Gadget Serial driver using:
kobject_uevent(cdev-gadget-dev.kobj, KOBJ_ONLINE);
However, the uevent gets filtered out with the error message:
filter function caused the event to drop!
-from kobject_uevent.c line 124
The filter function used is
On Tue, 30 Jun 2009, Daniel Ng wrote:
Hi,
I'm trying to send a uevent from my USB Gadget Serial driver using:
kobject_uevent(cdev-gadget-dev.kobj, KOBJ_ONLINE);
However, the uevent gets filtered out with the error message:
filter function caused the event to drop!
-from
