From: cliff white <cliffw@osdl.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Keyboard broken on iBook - linuxppc-2.5 latest
Date: Mon, 6 Oct 2003 12:58:29 -0700 [thread overview]
Message-ID: <20031006125829.58943956.cliffw@osdl.org> (raw)
Symptoms are identical to those reported on Bugzilla Bug #1025
Kernel: lastest from ppc.bkbits.net/linuxppc-2.5
(10/06/03 AM)
Single keypress produces > 2 repeated characters. Can't even login to
the system, as i cannot enter my uid.
Last successful kernel was from this changeset:
ChangeSet@1.1065, 2003-09-26 22:33:42+10:00, paulus@samba.org
Everything since then either doesn't complie, or has the keyboard problem
Further information on request. Please email me directly as i am not on this list.
cliffw
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-10-06 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 19:58 cliff white [this message]
2003-10-06 20:13 ` Keyboard broken on iBook - linuxppc-2.5 latest Benjamin Herrenschmidt
2003-10-06 20:24 ` cliff white
2003-10-06 20:27 ` Benjamin Herrenschmidt
2003-10-06 22:37 ` cliff white
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=20031006125829.58943956.cliffw@osdl.org \
--to=cliffw@osdl.org \
--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