From: "David A. Gatwood" <dgatwood@deepspace.mklinux.org>
To: Alain Birtz <abz@videotron.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Does USB keyboard LED supported in LinuxPPC ?
Date: Tue, 9 May 2000 21:59:40 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.3.96.1000509215922.5282C-100000@deepspace.mklinux.org> (raw)
In-Reply-To: <391811E0.CD5262DB@videotron.ca>
On Tue, 9 May 2000, Alain Birtz wrote:
> Does LinuxPPC 2000 support LED (like Cap Lock or Num Lock) on the USB
> keyboard ?
Doesn't seem to. At least it doesn't on my G4.
David
---------------------------------------------------------------------
A brief Haiku:
Microsoft is bad.
It seems secure at first glance.
Then you read your mail.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-05-10 4:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-09 13:25 Does USB keyboard LED supported in LinuxPPC ? Alain Birtz
2000-05-10 4:59 ` David A. Gatwood [this message]
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=Pine.LNX.3.96.1000509215922.5282C-100000@deepspace.mklinux.org \
--to=dgatwood@deepspace.mklinux.org \
--cc=abz@videotron.ca \
--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).