> How does it recognise a keyboard, anyway?
Hardware manufacturer id, device id and device class (e.g. Mass storage, input
device, etc)
> Does that driver have to be installed specially?
No, nothing needs to be installed in Chinook and Diablo, it just "works".
> -- hendrik
___
On Sun, 28 Sep 2008 08:00:55 -0600, Mark wrote:
> On Sun, Sep 28, 2008 at 6:50 AM, Hendrik Boom <[EMAIL PROTECTED]>
> wrote:
>> On Sat, 27 Sep 2008 23:49:08 +0100, Matt Emson wrote:
>>
>>> This should get you started...
>>>
>>> Get what the mode is currently set:
>>> cat /sys/devices/platform/musb
On Sun, Sep 28, 2008 at 6:50 AM, Hendrik Boom <[EMAIL PROTECTED]> wrote:
> On Sat, 27 Sep 2008 23:49:08 +0100, Matt Emson wrote:
>
>> This should get you started...
>>
>> Get what the mode is currently set:
>> cat /sys/devices/platform/musb_hdrc/mode)
>>
>> Turn off the onscreen kbd:
>> gconftool-2
On Sat, 27 Sep 2008 23:49:08 +0100, Matt Emson wrote:
> This should get you started...
>
> Get what the mode is currently set:
> cat /sys/devices/platform/musb_hdrc/mode)
>
> Turn off the onscreen kbd:
> gconftool-2 -t bool -s /system/osso/af/keyboard-attached true
>
> Turn on the onscreen kbd