Quote:
Originally Posted by tshering
|
It does, indeed !
I did a diff on the native Kobo kernel config, and the one he is using.
There are more than just USB keyboard settings changed in his kernel, for example he's using the auto-update e-paper driver patch; which allows regular linux applications to run on the framebuffer -- but I think that would cause conflicts with nickel / QT doing manual updates; and since I need them to run together for right now; I don't want to replace the kernel yet.
There are three USB settings which he obviously changed, so I did a make menuconfig and added these options:
under: Device Drivers --> enabled[*] HID Devices (submenu enable), then
{M} Generic HID support
<M> USB Hum Interface Device (full HID) support
under: Device Drivers -> USB support --> [*] Support for DR host port on Freescale controller
But -- I think A keyboard runs in low-speed mode, so I'm thinking the last change is probably not necessary ? That's more of something needed to make external thumb drives work...
I'm hoping I can compile in the needed keyboard drivers as modules, and won't have to replace the kobo native kernel -- but only run insmod.
Hmmm... Now all I need is a power cord with USBOTG to USB adapter combo, as apparently these code changes are insufficient to get the OTG controller to supply power to the port -- but maybe that's just because he was using a USB hub ? ( EDIT: Just got one and tested, the keyboard didn't work, although the hid modules do load.).
There's probably a way to turn power on through the /sys interface, if I only knew the appropriate echo command to make it happen.... Well, guess I'll figure that out after I get everything else working since I know the keyboard can be operated with external power, I'll try that first.
....
I just discovered that udev doesn't like to have the 'info' mode set for debugging; eg: to test why a rule I made isn't being run.... and the rules do not appear to be in the default /etc/udev/rules.d directory; ugh! Udev behaves differently when debugging is attempted; and it also doesn't appear to be logging the info messages to the dmesg file. Anyone have an idea how udev is set up on an AuraHD? or where the log file is stored on a kobo?
I tested the android keyboard on a regular PC, and it came up fine; although my PC's dmesg log says hid-raw was involved. So I'll see if adding a kernel module for hid-raw helps. But on the KOBO the only message that appears is one saying "USB-plug" and "USB-unplug" when I insert and remove the keyboard. SO the hid modules are necessary, but not enough to make the keyboard work
MD5sums.
0f96250966d77aca5d3bbe44329d68d0 hid.ko.bz2
fefa81f74510f11251d01f954ca826d3 usbhid.ko.bz2