linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: jingai <jingai@floatingpenguins.com>
To: "linuxppc-dev" <linuxppc-dev@lists.linuxppc.org>
Subject: USB keyboard & 2.2.18pre17
Date: Sun, 29 Oct 2000 19:50:36 -0500	[thread overview]
Message-ID: <200010300050.e9U0oej23495@shell.faradic.net> (raw)


Hello list, got a bit of a problem.  I just rsync'ed both Paul's and Ben's
stable tree, 2.2.18pre17, and with both my USB keyboard no longer
works.  With verbose debugging output enabled, I see that the
keyboard, mouse, and printer are all detected, but for some reason
the keyboard is not attached as a keyboard device.  I have a feeling
it may have something to do with the new ADB keyboard/mouse
drivers, because I also have an ADB keyboard and mouse connected,
both of which work.  However, my USB mouse and printer function
properly, so I'm thinking the new input layer stuff is seeing the ADB
keyboard first and it doesn't attempt to attach the USB keyboard
because it's already found one (ie, bug).

I'll try to have a look over the code and find the bug myself, but I
was just wondering if anyone else has noticed this, and if there is
already a patch available..

BTW, the keyboard works fine with 2.2.17 and 2.4.0-test10, although
with 2.2.17 it would sporadically lose my keyboard entirely, but it
doesn't happen *too* often.

Also, the keyboard is a Macally iKey (the blue one to match the
blue G3s..)

Regards,
Jonathan


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

                 reply	other threads:[~2000-10-30  0:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200010300050.e9U0oej23495@shell.faradic.net \
    --to=jingai@floatingpenguins.com \
    --cc=linuxppc-dev@lists.linuxppc.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 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).