[parisc-linux] HIL -> Keymap ok?

[parisc-linux] HIL -> Keymap ok?

[Carlos O'Donell Jr.]

pa's,

I recently needed to connect an HIL keyboard to our 715/50 boxes and
was surprised to find that the key mapping was less than correct
(2.4.18-pa22).

--
5. Scorpio Core HIL (10) at 0xf0821000 [2/0/3], versions 0x7, 0x0, 0x73
Found HIL at 0xf0821000, IRQ 94
HIL: keyboard found at id 0
HIL: keymap loaded.
--

Looks okay. But I get all the wrong letters and control commands in 
all the wrong places (e.g. a=x, i=\n).

I've tried on two or three boxes with two or three different keyboards
(have a whole box of HIL keyboards if anyone is in desperate need of
one).

The install is based on 0.9.3 with all the latest apt-get updates.
I stopped running keymap.sh with no adverse effects (since the keymap
is loaded by the HIL driver).

The HIL driver is the old one?
[Character Devices]-[Support for Console on VT]-[HIL kbd support]

CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HIL=y

I also have a serial console enabled.

I haven't tried HP System Device Driver (i8042) yet... (Though from
the looks of it, it's not quite complete?)

Any thoughts? (I've wadded through the list archives but no success).

c.

p.s. This is just the start of my quest to stop the unbliking eye...
     a.k.a. "hardware cusor blinking" ... from _always_ appearing 
     during framebuffer writes.

Re: [parisc-linux] HIL -> Keymap ok?

[Helge Deller]

On Saturday 27 April 2002 23:11, Carlos O'Donell Jr. wrote:
> I recently needed to connect an HIL keyboard to our 715/50 boxes and
> was surprised to find that the key mapping was less than correct
> (2.4.18-pa22).

Hmm, I've no problems with my HIL keyboard on console.
(In X11 you have of course to use the correct mapping.)

> p.s. This is just the start of my quest to stop the unbliking eye...
>      a.k.a. "hardware cusor blinking" ... from _always_ appearing
>      during framebuffer writes.

Shouldn't be that hard.

Greetings,
Helge

Re: [parisc-linux] HIL -> Keymap ok?

[Carlos O'Donell Jr.]

Helge,

> > p.s. This is just the start of my quest to stop the unbliking eye...
> >      a.k.a. "hardware cusor blinking" ... from _always_ appearing
> >      during framebuffer writes.
> 
> Shouldn't be that hard.
>

I've done a few nasty things to /drivers/video/sti to attempt to
stop the hardware cursor bliking, but I've not succeeded.

Even if I have no console on /dev/fb0 the penguin and blinking
cursor are the first things to appear as the fb device is initialized.

Any hints?

c.