linuxconsole-dev

keyboard

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

newbie to ruby,
(I follow the linuxconsole mailing list regularly, but that was not
enough I am afraid)

I had to remove a line preventing util/inputattach.c from working.
(but didn't want to update in cvs as I dunno who's changing what)
offending line:
# { "--stinger",          "-sting",       B1200,
CS8,                     SERIO_STINGER,  0x00,   1,      stinger_init },

SERIO_STINGER not defined.

with 2.40-test7 + patched:
make menuconfig wouldn't work as is (it complained about include/asm
being a directory or
whatever so I changed the makefile and removed the rm -f include/asm -
maybe it should
be a rm -rf ?)

Is devfs required/advisable/not needed?

I could test my usb keyboard with evtest, but there is only one event
interface
where is my ps2 keyboard (as a device)?
How do I set the multiplexing?
btw, linux refuses to boot sometimes when my usb keyboard is plugged
(stops after you press return in lilo) but if I unplug and then replug
after the boot it's fine..

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?
Or maybe X will start up using whatever keyboard was being used upon
start up?
Can someone explain briefly how that's going to work?
I will be looking at X docs today to try and understand a bit more about
drivers.

Please help me help you.
Thanks
Antoine

Re: keyboard

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

> I had to remove a line preventing util/inputattach.c from working.
> (but didn't want to update in cvs as I dunno who's changing what)
> offending line:
> # { "--stinger",          "-sting",       B1200,
> CS8,                     SERIO_STINGER,  0x00,   1,      stinger_init },
> 
> SERIO_STINGER not defined.

Strange. I gave it a run and had no problem. Is this with the current CVS?
SERIO_STINGER is defined in serio.h in linux/include/linux. Please try it
again with the latest CVS and let me know if you have the same problem.
Also make sure /usr/include/linux points to the ruby tree. I have made
this mistake before.

> with 2.40-test7 + patched:
> make menuconfig wouldn't work as is (it complained about include/asm
> being a directory or
> whatever so I changed the makefile and removed the rm -f include/asm -
> maybe it should
> be a rm -rf ?)

That is also strange. Normally include/asm is a symbolic link to
include/asm-xxx where xxx is the platform you are on. 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. 
You wouldn't happen to be running a Debian distro?
 
> Is devfs required/advisable/not needed?

Same as any other system. It is not needed but if you do use devfs
remember to run the devfsd deamon. 

> 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

Aug 29 13:05:52 maxwell kernel: keyboard.c: Adding keyboard: input0
Aug 29 13:05:52 maxwell kernel: input0: AT Set 2 Extended keyboard
Aug 29 13:05:52 maxwell kernel:  on serio0
Aug 29 13:05:52 maxwell kernel: mice: PS/2 mouse device common for all
mice
Aug 29 13:05:52 maxwell kernel: event0: Event device for input0

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

> 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 :-) 

> btw, linux refuses to boot sometimes when my usb keyboard is plugged
> (stops after you press return in lilo) but if I unplug and then replug
> after the boot it's fine..

That sounds like a BIOS problem. I have the same problem with plugging in
2 ps/2 keyboards. It confuses the BIOS. I have to plug in my second PS/2
keyboard while the kernel is booting. I might be wrong as I don't have a
usb keyboard. 

> 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. 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. 

> Or maybe X will start up using whatever keyboard was being used upon
> start up?
> Can someone explain briefly how that's going to work?
> I will be looking at X docs today to try and understand a bit more about
> drivers.

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.

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

Re: keyboard

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

> > 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?

No. For every input device a /dev/input/event should appear if you
are using devfs. Otherwise you have to create the device file yourself
(man mknod). The console system behave indpendent of the userland input
interface. This is a more powerful approach. 

> Actually, I have 2 displays (rage128 agp and g200 pci), 2 keyboards (ps2
> and usb) and 2 rodents (ps2 and usb).

Cool. 

> 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...

Well that is a little more complex. I seen another posting about this.

> 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!?

Right now with ruby only vgacon, mdacon, and nvida text mode are
supported. The fbdev layer is incomplete. I have found matrox cards
usually like to be booted first. I know of no way to make one card boot
before another. Petr, you have any ideas ?

> 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

  How do you get the fbcon layer to even compile for ruby? I didn't think
it compiled. Also alot of the fbcon layer has global variables meaning it
not really multihead safe. I'm rewriting that code to make it really
multihead safe but I'm not finished. 
   The reason con2fb doesn't work is because with the new console
system it automatically allocates 16 VCs to each head. You don't need to
do con2fb because it should be done automatically for you. With your setup
with the fbcon layer you should have 2 consoles come up for you automatically.
The console code also prevents things like VC switching to a different
head than your on.

> > Look at ruby CVS code for xfree86.
> 
> Where is this tree?

Grab the ruby tree and right at the top you see a xfree86 directory.

> > 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)
> > 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.

Go for it. I noticed the lack of docs myself. I atempted to read their
code but it was such a mess I gave up.

MS: (n) 1. A debilitating and surprisingly widespread affliction that
renders the sufferer barely able to perform the simplest task. 2. A disease.

James Simmons  [jsi...@li...]               ____/| 
fbdev/console/gfx developer                             \ o.O| 
http://www.linux-fbdev.org                               =(_)= 
http://linuxgfx.sourceforge.net                            U
http://linuxconsole.sourceforge.net

Re: keyboard

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

> 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...
>
> Well that is a little more complex. I seen another posting about this.

Anyone got any more info on this?

> Right now with ruby only vgacon, mdacon, and nvida text mode are
> supported. The fbdev layer is incomplete. I have found matrox cards
> usually like to be booted first.

My BIOS has AGP first (the matrox is on PCI), and it works quite
happily (+xinerama, fb tools...) - only error message  is:
"Video BIOS not detected in PCI space!"
"Attempting to read Video BIOS from legacy ISA space!"
But I guess that's something for my BIOS setup. (shadow rom or something)

> I know of no way to make one card boot
> before another. Petr, you have any ideas ?

It is not crucial, but it would be nice (19" instead of 14"), in the meantime
I'll boot in straight text mode, but then I can't use X (don't ask me why my
video card needs a framebuffer to be initialised properly for X...)

>   How do you get the fbcon layer to even compile for ruby? I didn't think
> it compiled.

I thought vesa or matrox did (or maybe it was an older version, or maybe
I am just going insane again)
The USB is broken too.

> Also alot of the fbcon layer has global variables meaning it
> not really multihead safe. I'm rewriting that code to make it really
> multihead safe but I'm not finished.
>    The reason con2fb doesn't work is because with the new console
> system it automatically allocates 16 VCs to each head. You don't need to
> do con2fb because it should be done automatically for you. With your setup
> with the fbcon layer you should have 2 consoles come up for you automatically.
> The console code also prevents things like VC switching to a different
> head than your on.

So how can I switch/use to the second head?
Or do I just attach a keyboard to the second head?
- no quite clear in *my* head yet, but getting there.

> > > Look at ruby CVS code for xfree86.
> > Where is this tree?
> Grab the ruby tree and right at the top you see a xfree86 directory.

I still don't see it! (ls -lR | grep -i xfree => nothing)
[antoine@shami ruby]$ ls
AGAINST-2.4.0-test7  CVS  app-patches  linux  utils

> Go for it. I noticed the lack of docs myself. I atempted to read their
> code but it was such a mess I gave up.

docs what docs. ;-(
Do you think there is any chance of getting the Xfree86 people to point me in
the right direction? Or spare me a few minutes (like you guys did).

Many Thanks
Antoine

Re: keyboard

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

> > Well that is a little more complex. I seen another posting about this.
> 
> Anyone got any more info on this?

XFree86 X servers are a little different than other peices of software.
They talk directly to the hardware bypassing the kernels resource
management system. XFree86 3.3.6 has no really multihead management.
XF4.0 sort of does but it does it on its own instead of using the OS to
help it out. 

> My BIOS has AGP first (the matrox is on PCI), and it works quite
> happily (+xinerama, fb tools...) - only error message  is:
> "Video BIOS not detected in PCI space!"
> "Attempting to read Video BIOS from legacy ISA space!"
> But I guess that's something for my BIOS setup. (shadow rom or something)

Strange. I don't think this has anything to do with linux.

> It is not crucial, but it would be nice (19" instead of 14"), in the meantime
> I'll boot in straight text mode, but then I can't use X (don't ask me why my
> video card needs a framebuffer to be initialised properly for X...)

That is strange. XFree86 usually works better without fbdev. Is this what
your talking about?

> I thought vesa or matrox did (or maybe it was an older version, or maybe
> I am just going insane again)
> The USB is broken too.

Must be a older CVS download. Right now the fbdev is broken because of the
massive rewrite it needs.

> So how can I switch/use to the second head?
> Or do I just attach a keyboard to the second head?
> - no quite clear in *my* head yet, but getting there.

For a fully function VT you need one display and one keyboard. Each VT
acts independent of each other. This is done for security reasons. Imagine
at work on have one multihead linux server. Now from the server each
keyboard and monitor with extensions could run into different offices.
Here you don't want to VT switch to a terminal belonging to someone else
in some other office. 

> > > > Look at ruby CVS code for xfree86.
> > > Where is this tree?
> > Grab the ruby tree and right at the top you see a xfree86 directory.
> 
> I still don't see it! (ls -lR | grep -i xfree => nothing)
> [antoine@shami ruby]$ ls
> AGAINST-2.4.0-test7  CVS  app-patches  linux  utils

Remove the current ruby tree you have to download a new tree. I have 

AGAINST-2.4.0-test7  CVS  app-patches  linux  utils  xfree86   

> docs what docs. ;-(
> Do you think there is any chance of getting the Xfree86 people to point me in
> the right direction? Or spare me a few minutes (like you guys did).

Ask them. They have several mailing list. 

MS: (n) 1. A debilitating and surprisingly widespread affliction that
renders the sufferer barely able to perform the simplest task. 2. A disease.

James Simmons  [jsi...@li...]               ____/| 
fbdev/console/gfx developer                             \ o.O| 
http://www.linux-fbdev.org                               =(_)= 
http://linuxgfx.sourceforge.net                            U
http://linuxconsole.sourceforge.net

Re: keyboard

[Vojtech P. <vo...@su...>]

On Wed, Aug 30, 2000 at 03:25:23PM +0100, Antoine Martin wrote:

> newbie to ruby,
> (I follow the linuxconsole mailing list regularly, but that was not
> enough I am afraid)
> 
> I had to remove a line preventing util/inputattach.c from working.
> (but didn't want to update in cvs as I dunno who's changing what)
> offending line:
> # { "--stinger",          "-sting",       B1200,
> CS8,                     SERIO_STINGER,  0x00,   1,      stinger_init },
> 
> SERIO_STINGER not defined.

ruby/linux/include/linux/serio.h, line 106:

#define SERIO_STINGER   0x1e

> with 2.40-test7 + patched:
> make menuconfig wouldn't work as is (it complained about include/asm
> being a directory or
> whatever so I changed the makefile and removed the rm -f include/asm -
> maybe it should
> be a rm -rf ?)

Yes.

> Is devfs required/advisable/not needed?

Works both with and without.

> I could test my usb keyboard with evtest, but there is only one event
> interface
> where is my ps2 keyboard (as a device)?

/dev/input/eventX, as well, but perhaps you didn't enable all the needed
options.

> How do I set the multiplexing?
> btw, linux refuses to boot sometimes when my usb keyboard is plugged
> (stops after you press return in lilo) but if I unplug and then replug
> after the boot it's fine..

That's a bug in the current USB (not ruby) code.

> 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?

That would be very nice, yes. Noone has volunteered yet, afaik.

> Or maybe X will start up using whatever keyboard was being used upon
> start up?
> Can someone explain briefly how that's going to work?
> I will be looking at X docs today to try and understand a bit more about
> drivers.

-- 
Vojtech Pavlik
SuSE Labs

Re: keyboard

[<ni...@co...>]

On Thu, Aug 31, 2000 at 05:17:14PM +0200, Vojtech Pavlik wrote:
> On Wed, Aug 30, 2000 at 03:25:23PM +0100, Antoine Martin wrote:
> > 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?
> 
> That would be very nice, yes. Noone has volunteered yet, afaik.
  I've started one.  Last I used it it worked 90% for my mouse.  I was
almost up to the point of creating the keyboard event maps when I stoped
working on it.
  It wouldn't be in the keyboard section, however. Not in XF4 at least. The
keyboard and mouse sections are depreciated and ideally shouldn't be used. 
But, as there is no suitible replacement for the old keyboard driver yet the
keyboard section is still needed.

> 
> > Or maybe X will start up using whatever keyboard was being used upon
> > start up?
> > Can someone explain briefly how that's going to work?
> > I will be looking at X docs today to try and understand a bit more about
> > drivers.
  Well, if the existing way (or something similar) that X gets it's
keycodes from the console survives then yes, it will use the same keyboard
config as that VC, unless overridden.

  - Nick Lopez
    kim...@at...
--
"One World, One Web, One Program" - Microsoft Promotional Ad
"Ein Volk, Ein Reich, Ein Fuhrer" - Adolf Hitler