Re: question about ruby's keyboard.c & keybdev.c

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

> > Just a few more steps to go. I submited the console patches to Linus. Now
> > to wait for them to go in.
>
> Well, what are a few weeks more, I'm waiting for 2 years now for this code to
> go in.

Well it is a matter of convincing Linus to take the code. I sent him the
BK link for the console code some time ago. He hasn't applied it.


> > layer is if you want to change the api you need to change the upper
> > layer first and break every driver. Its the only way it will work.
>
> No complaint here, just searching for a solution :-).

Its the only way. BT Wprepare for major breakage for teh fbdev layer. Only
a few drivers will work very soon.

> Exactly. i8042.c has quite a few assumptions in it. It uses inb/out instead of
> ioremap/readb/writeb, it assumes control and data register are 4 addresses
> apart and it assumes no special sequences are necessary to access these
> registers.

Some time ago I thought about this when I looked at the sparc i8042
driver. I tried a few things but I didn't come up with a solution.