> 1) It is step back: we used to have loadable keymaps. With ggi, kernel> contains files such as keyboard_english.c. Even if it is not run-time> bloat, it is source bloat.

Fixed by EvStack. It's being worked on already. We have to fix it to beable to handle multiple keyboards connected to the same machine.

> 2) It touches things it should not touch. It replaces big parts of> drivers/char. I know that keyboard etc. are somehow related to> graphics, but you really do not want to _replace_ low level> drivers. This way, ggi being config option would mean having drivers> twice.

Yes, well, I am not _the_ kernel hacker of GGI, but I have had itexplained to me that it was necessary to be able to send keycodes etc tothe right head/window/app/whatever. I will forward to those responsible.