iLiad My next porting project really bites!

[scotty1024]

Originally Posted by Matthijs

I can post the kernel config file if that helps?

Actually that would be a huge help. Part of the house of cards to this has been tweaking the kernel config to try and match the one of the kernel in the iLiad (kmod or no kmod, Exelon Development board or Intel pXA255, PXA255 USB support or ....)

This is actually very safe development for developers as I've proven over and over again by crashing and restarting my iLiad.

Of course if you all wanted to post a working USB keyboard loadable kernel driver... it would enable a whole new collection of applications for the iLiad.

And of course iRex could work with Eleksen to produce an iLiad keyboard/slipcover: http://www.engadget.com/2006/10/30/e...e-in-the-wild/

[Matthijs]

I don't have a working USB keyboard driver, otherwise I would have shared that a long time ago. It might be easy to create one, but I've never tried...

Anyway, see attached file.

Just a warning: please don't try to load a custom kernel, it will brick you iLiad (no working filesystem, no working ethernet, etc, etc.)

[henkvdg]

#
# Input core support
#
# CONFIG_INPUT is not set
# CONFIG_INPUT_KEYBDEV is not set
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set

#

[scotty1024]

Thank you for posting the kernel configuration.

input is available as a module but perhaps it doesn't work either if the base kernel was set to NO rather than MODULE... This is what I was starting to suspect!

As Barb from Princess of Wands would say: Sugar!

I don't suppose there is any chance of reconfiguring the kernel to Module for:
CONFIG_INPUT
CONFIG_INPUT_KEYBDEV
CONFIG_INPUT_MOUSEDEV

Like for perhaps a 2.8.1 release?

And yes, I'm not crazy enough to flash my own Kernel without JTAG.

[scotty1024]

Originally Posted by Matthijs

Just a warning: please don't try to load a custom kernel, it will brick you iLiad (no working filesystem, no working ethernet, etc, etc.)

In case anyone didn't understand the above, he isn't say it might, he's saying it will. The reason is that the iLiad uses proprietary kernel code to support the Sandisk Disk on Chip which is the device that provides the iLiad's onboard storage.

That code is not available publicly and with out that code you can't produce a working kernel for the iLiad.