Re: Latest analog joystick code

[James S. <jsi...@ac...>]

> > It's not only when I VT switch away. If I'm on VT 1 and keep pressing 
> > Alt-F1 it also prints out a A. 
> 
> Thanks for the info. But it's even weirder than just that. Try running
> a 'cat' on the VT - the problem disappears. I'll try to look into it.

That is strange. I haven't been able to see anything. The 3Dfx driver with
the new API is giving me the infamous blank screen. So I will be looking
threw that code tomorrow. Video drivers are the worst to debug. The vgacon
driver works like a charm. Once I get the first driver working like a
charm the rest should be easy. The matrox works great. OF course I haven't
touched it.

> Oh, yes. Per-VT keymaps will consume quite a lot of memory, btw ...

Not if you take the write on copy approach. All VC keymap point to same
keymap. If userland wants a different keymap it changes the pointer of the
the VC keymap to the new keymap. The bigger problem is the number of
vc_data we can have. With the present console system we have 64 allocated
vc_data structs for one head. With fbdev you can have up to 256 heads and
USB up to 127 keyboards. With a AT or PS/2 keyboard we can a total of 128
complete VTs. This means 128 * 64 = 8,192 vc_data structs. This means we
have to adopt a dynamic approach to allocating VCs.