Re: keyboard

[Antoine M. <an...@go...>]

James Simmons wrote:

> > SERIO_STINGER not defined.
> Strange. I gave it a run and had no problem. Is this with the current CVS?

It was fixed within a few hours... (I had also sent a mail fo Vojtech)

> Also make sure /usr/include/linux points to the ruby tree. I have made
> this mistake before.

So have I ;-) but not this time.

> So include/asm
> should be a symbolic link. Normally make config sets this symbolic link.
> Remove the include/asm diretcory and rerun make menuconfig. I'm curious.

yep, it is a softlink.
Ok, I'll try that later. (can't do it in the office as they are all live
systems...)

> You wouldn't happen to be running a Debian distro?

no, I am running an old slackware, updated a zillion times.

>
> > I could test my usb keyboard with evtest, but there is only one event
> > interface
> > where is my ps2 keyboard (as a device)?
>
> What do you see for your dmesg? I have
>
> (...)

> This is for a single PS/2 keyboard. What do you see for your setup?

similar stuff. I'll send the logs later if needed.
but from what you said below, I understand it means that my primary
keyboard (ps2) is bound to the console and won't be in /dev/input/event,
is this correct?

>
> > How do I set the multiplexing?
>
> The way ruby works is one keyboard is mapped to one display for the
> console system. If you want to access non attached keyboard this is where
> the input interface comes in. By non attached I mean you have more
> keybaords than displays (like me). Once the kernel side is pretty much
> done I will begain work on a new consd deamon that will be able to do
> weird combos like VTs with 2 keyboards and one display. That will be
> handled in userland. As for multiple VTs the console system handles the
> multiplexing for you :-)
>

Actually, I have 2 displays (rage128 agp and g200 pci), 2 keyboards (ps2
and usb) and 2 rodents (ps2 and usb).
And I wouldn't mind running concurrently 2 full X desktops off 1 box...
(could even run q3 multiplayer off that box!?)
When I start 2 X servers (both using the ps2 keyboard since I couldn't
work it out) I need to VT switch to change which X is active, I guess
tha's because they share the same keyboard. If I get one of the Xs to use
the usb keyboard, will they both be running concurrently then? Or do I need
something extra...

Also, when using ruby, it boots off the g200 (usually boots off the r128)
and the kernel boot messages in dmesg do not contain whatever was
on the console before it switched to the g200, where can I get these early
messages? And why did they disappear!?
Are there any boot parameters to set the console to the r128 instead?
(I tried lilo append "atyfb:....." but it still went to the g200)
Then, if I try to con2fb to the r128, it does not come on (but it works on
test7).
Framebuffer tools (fbset, fbi or fbtv...) all go to the g200, even when I
specify
-c /dev/fb1 (the r128), now that's scary!
Also, on test7 I need to con2fb to the r128 before I can use it as a
framebuffer
device (all modules already loaded...), otherwise the fb mode that gets set is

incorrect and data only appears at the top of the screen (higher res).

> > I guess that for multiple keyboards, the keyboard.c file from XFree86
> > will need changing,
> > anyone fancy making a patch to allow a ' Device "/dev/inputXXX" ' option
> > in XF86Config
> > for the keyboard section?
>
> Look at ruby CVS code for xfree86.

Where is this tree?

> It has a patch to apply against the
> XFree86 3.3.6 code tree. As far as I can see XF4.0 isn't support yet with
> the CVS code. XF4.0 does have support for multiple keybaords but last I
> looked it didn't support USB keyboards or /dev/input. Which X server are
> you running.

4.0.1 from CVS (but I must have an old 3.3.6 tree somewhere)

> Depends on which X server you have. For XFree86 3.3.6 you have to apply a
> patch. For XF4.0 you play some config tricks to get it to work. From the
> last I seen USB keyboards and the new input system are not supported with
> XF4.0. With XFree86 it usually takes them 6 months to support something.

what about doing it myself?
I was looking around for docs on xinput and the whole input stuff in X4...
and I didn't find much info.

Thanks for your help, it already makes a lot more sense.

Antoine