On Mar 30 at 12:02 -0700, Maksim Yevmenkin wrote:
> On 3/29/07, Timothy Bourke <[EMAIL PROTECTED]> wrote:
> >It seems that, for the extant drivers:
> >* enable only increments kb_active,
> >* disable only decrements kb_active.
>
> well, yes, if all kbdmux did was call KBD_ACTIVATE/_DEACTIV
On 3/29/07, Timothy Bourke <[EMAIL PROTECTED]> wrote:
[...]
> >Does the attached patch seem reasonable? It would fix my immediate
> >problem.
>
> sorry for the delay. i'm not sure about this patch. basically, i do
> not think that keyboard should be disabled if it is released from
> kbdmux. it
Thanks for responding, Max.
On Mar 29 at 09:08 -0800, Maksim Yevmenkin wrote:
> On 3/24/07, Timothy Bourke <[EMAIL PROTECTED]> wrote in part:
> >However, enable is called too many times and disable is never called.
> >
> >In the kbdmux_ioctl routine:
> >KBADDKBD: enable is called via the KBDMU
On 3/24/07, Timothy Bourke <[EMAIL PROTECTED]> wrote:
I have almost finished a ppbus-based driver for Super Nintendo
controllers. It presents itself as a keyboard to the operating system. I
wanted to start and stop the polling thread via, respectively, the
kbd_enable_t and kbd_disable_t hooks, bu
I have almost finished a ppbus-based driver for Super Nintendo
controllers. It presents itself as a keyboard to the operating system. I
wanted to start and stop the polling thread via, respectively, the
kbd_enable_t and kbd_disable_t hooks, but these do not seem to be called
properly. Hence this po
5 matches
Mail list logo
