Re: h5500 keys

On Po, 2007-07-02 at 15:43 +0200, Hinko Kocevar wrote:
> Hi all,
>
> I've managed to boot my h5500 with 2.6 yesterday, finally!

  First of all -- development of 2.6 kernels has so far been done on
h5550 devices. If there are and differences between models, we probably
missed them. I'm answering following questions to the extent I know from
h5550.

> I have some questions:
> - is it normal that once the 2.6 kernel boots, and mounts jffs2
> rootfs on mtdblock1 fails to execute /linuxrc, when rootfs that came
> with familiar-0.8.4 is used?

  I'm not sure, if there isn't linuxrc on the rootfs, it should not be
problem.

> - I've might overlooked it on your site, but is there a 2.6 rootfs
> for use with 2.6 kernel available on handhelds?

  Not in official distributions, 2.6 for h5000 is not considered stable.
There are Angstrom images which contains some older 2.6 kernel... .

> - On my device only power button seems to generate input events -
> joystick and other four buttons are dead, eg. no event is propagated
> to input subsystem (IMHO not even interrupt is generated, when key is
> presed),

  I'm not sure which kernel version do you use -- there is sort of
support for h5000 keys, see gpiodev-keys and gpiodev-diagonal drivers in
CVS HEAD and also few most recent -hh tags.

> - touchscreen is also dead, although it is bind to /dev/input/eventx,
> like the buttons, touching it doesn't generate an interrupt..

  Are you sure you have touchscreen driver enabled? Also, there were
some issues related to touchscreen, again, kernel version is important

>
> Funny thing is that upon boot all three input devices are detected and
> assigned unique eventx device entry; event0, event1, event2. I've
> enabled input debugging and only when pressing power button I can see
> interrupt messages are logged on the console, when pressing other 4
> buttons nothing is logged to console..

  I'm not quite sure -- by having three devices I assume you have also
gpiodev-* modules loaded. Try cat /proc/interrupts, there should be
(except for other things) also listed interrupts assigned to buttons, if
any.

>
> best regards,
> hinko

        Milan
Received on Mon Jul 02 2007 - 17:33:38 EDT