On Wed, Jan 30, 2002 at 05:23:52PM +0700, Rakesh wrote:
> Hi all,
> I've compiled 2.4.13 kernel  and download it to assabet/neponset board.
> The login appeared but i m not getting any message rel;ated to the
> keyboard which is already there in "neponset.c", sa1111.c and
> sa1111_keyb.c file. I am not getting any message in the minicom.

You are not seeing anything, or you are not seeing a message related to
the keyboard?

Do you see the keyboard LEDs flash when the kernel boots?


> When i checked the pin 21 & 5 by CRO its giving some pulses. But if i m
> pressing num lock, caps lock, scroll lock, LEDs are not turning ON. Just
> when i connect the keybpard it just blink once.

The keyboard must be connected at boot, and must remain connected.
Currently, the kernel doesn't re-initialise the keyboard when it is
reconnected.  (Traditionally, this job is done by the i8042 keyboard
controller in a PC).  Oh, and its strongly recommended in all literature
that I've read on PS2 devices that PS2 devices aren't connected and
disconnected with power on.

> I am using CS4 for sa1111 chip. And neponset interrupt signal is routed
> to GPIO 1 but in the code its routed to GPIO 25. So I have made a single
> change for that by changing GPIO 25 to GPIO 1.

Umm, you haven't got an Assabet/Neponset then, but a custom design.

> I gone thr' the mailing list and they have mentioned that sa1111_keyb
> device driver works for latest kernel. And i m using the latest one only
> 2.4.13.

Its always best to try to keep up to date with the kernels - 2.4.17-rmk4
is broken, but I put out a patch that fixes it a few days ago.  However, I
don't believe any problems were reported with the sa1111 keyboard in 2.4.13.

_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.

Reply via email to