Re: newer xfree86 4.0.1 patches

Franz Sirl wrote:

quoted

quoted

- what's the keycode situation in XF3/4 for Apus?

AFAIK it isn't very clean with either, the best bet is still to disable
Xkb.

On PPC we can switch the keycodes between ADB and Linux with a sysctl. Linux
keycodes are ~95% compatible with AT keycodes, so XKB will work.

That would be great IMHO.

quoted

quoted

- if your developer repository for 2.4 is different from BK
linuxppc_2_3, did you integrate your input layer drivers in your trees
and plan to submit them for 2.4?

We have a CVS repository at SourceForge. Roman Zippel integrates bitkeeper
into it, but unfortunately we don't have anyone for the reverse direction.
How could that be done?

Via Linus probably, but in this special case we could arrange something.

Please post to linux-apus-devel@lists.sourceforge.net what we'd have to do.

quoted

quoted

If you want to keep the current state of affairs I can see in the
linuxppc_2_3 tree, there's not much point in using machid.c, AFAICS. On
the other hand, if you plan to integrate your input drivers into 2.4, it
makes perfect sense.

I think it would be nice, but to be honest I don't fully understand what
would be involved.

Actually not much, given the Apus input drivers in the linuxconsole
repository ("ruby") on sourceforge are already functional,

I don't know, so I assume not :(

it's simply a matter of copying the files and modifying the configuration
scripts. If you want to continue to support Apus keycodes, you need some
translation code in input/keybdev.c too.

Thanks.


Michel


--
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86 and The DRI Project

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/