linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: bob@kunk.jriver.com
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Missing USB keys
Date: Tue, 26 Oct 1999 21:44:13 -0500 (CDT)	[thread overview]
Message-ID: <19991027024413.28285.qmail@kunk.jriver.com> (raw)


Martin Costabel Said:
.
.
I dug into this USB->ADB keycode
translation stuff, and I think I understand some of it now. As I see it,
this part of the kernel sources is a pretty ugly hack,
.
.

End of quote...

Am I beating a dead horse? But this ugly hack is perhaps responsible for
the lack of N-KEY rollover in the "new" USB keyboard driver????

Bob
-- 
Robert E. Brose II    N0QBJ
http://www.jriver.com/~bob/
bob@kunk.jriver.com

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

             reply	other threads:[~1999-10-27  2:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-27  2:44 bob [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-10-27  1:45 Missing USB keys (Was Re: Problems compiling ppc kernels.) Martin Costabel
1999-10-27  9:24 ` Missing USB keys Gerd Knorr
1999-10-27 12:05   ` Martin Costabel

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=19991027024413.28285.qmail@kunk.jriver.com \
    --to=bob@kunk.jriver.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).