9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9atom and USB Keyboard Problem
Date: Sun, 19 May 2013 15:20:30 -0400	[thread overview]
Message-ID: <7b53b089a2353b4755c9a7dd2628f0d9@ladd.quanstro.net> (raw)
In-Reply-To: <51991ed3.eab0ec0a.2d3e.119b@mx.google.com>

> I installed 9atom downloaded from Erik's site on 5/12 on a
> Gigabyte GA-D525TUD
> (http://www.gigabyte.com/products/product-page.aspx?pid=3549#ov).
>
> When I have *nomp=1 in plan9.ini, I am able to log in and
> things work OK (except the mouse wheel scroll direction is
> opposite to what I would expect), When I remove *nomp=1 from
> plan9.ini, 9atom reports four processors, and every keystroke
> produces 6 or 8 or more tokens of the character I am trying to
> type. If I'm lucky and I tap a key lightly and quickly enough, I
> can get a single character, but it's not easy.
>
> I tried the only other usb keyboard I have and had the same
> problem.
>
> Any suggestions?

9atom's usb is identical to sources, with the exception that i've
grabbed cinap's bios handoff code for ehci and enabled all
the controllers.  this was necessary to get usb to work on some
new hardware.

i'd recommend doing pull (as glenda) and rebuilding the
kernel, first.

i do know there is a bug that causes spurious kb repeating.
but typically it's not quite as severe, and depends a lot on
the keyboard in question.  it's interesting that you corellate
this to mp interrupts.  does the same hapen without *nomp
and with *ncpu=1?

i haven't done much research on this, so although the usb/kb
repeat mechanism at first blush looks like a good place to start,
it's not clear to me that this is the issue.

- erik



  reply	other threads:[~2013-05-19 19:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-19 12:22 Gregory Pavelak
2013-05-19 19:20 ` erik quanstrom [this message]
2013-05-19 22:38 ` erik quanstrom
2013-05-20 10:58   ` Gregory Pavelcak

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=7b53b089a2353b4755c9a7dd2628f0d9@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).