All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: xserver-kdrive 1.4 and USB keyboard
Date: Tue, 16 Sep 2008 22:53:08 +0200	[thread overview]
Message-ID: <gap6bl$2ca$1@ger.gmane.org> (raw)
In-Reply-To: <f96d234e0809161327v2d71e99bx79192593ff99086a@mail.gmail.com>

Cliff Brake wrote:
> Does anyone have this combination working yet?
>
> On my system, ctrl-alt-f1 does not work, and caps/num lock lights do
> not work when X is running.  Keyboard works fine at the console.

I suspect that's because kdrive 1.4 lacks a default keymap. Graeme 
provided a really bare-bones one that makes X access keys (e.g. xkbd, 
matchbox-keyboard). Making USB keyboards work properly proved to be too 
much work, so I am now using full-blown Xorg on anything with a 
usb-keyboard. Having said that, the A-z keys did work on beagle, the 
fact that left-mouse button clicks produced a 'q' was the final straw 
(clock on window running powertop - boom).
Something is very broken in kdrive, which might be due to people working 
on it only care for tablets from a certain scandinavian company.

regards,

Koen


>
> It works fine with xserver-kdrive-fbdev 1.3
>
> with 1.4, it seem there are some options added:
>
> -keybd driver [,,options]      Specify the keyboard driver and its options
> -kb                    disable the X Keyboard Extension
> +kb                    enable the X Keyboard Extension
>
> In the source code, I found the following:
>
>   ./hw/kdrive/ephyr/Xephyr :1 -fp /usr/share/fonts/X11/misc/ -mouse
> ephyr -keybd ephyr,,xkblayout=br,xkbmodel=abnt2
>
> /*
>   * You can call your kdriver server with something like:
>   * $ ./hw/kdrive/yourserver/X :1 -mouse evdev,,device=/dev/input/event4 -keybd
>   * evdev,,device=/dev/input/event1,xkbmodel=abnt2,xkblayout=br
>   */
>
> there are a few patch files that might be related:
> ./xserver-kdrive-1.4.0.90/no_xkb.patch
> ./xserver-kdrive/optional-xkb.patch
>
> I'm slogging through the source code, but would appreciate any ideas
> from anyone who understands this or has it working.
>
> Thanks,
> Cliff
>





  reply	other threads:[~2008-09-16 20:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-16 20:27 xserver-kdrive 1.4 and USB keyboard Cliff Brake
2008-09-16 20:53 ` Koen Kooi [this message]
2008-09-16 21:39   ` Cliff Brake
2008-09-17 10:09     ` Koen Kooi
2008-09-17 16:25       ` Cliff Brake
2008-09-17 16:33         ` Graeme Gregory

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='gap6bl$2ca$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.