From: J Sloan <joe@tmsusa.com>
To: Pete Zaitcev <zaitcev@redhat.com>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: USB Keyboard problem
Date: Sat, 25 May 2002 20:24:28 -0700 [thread overview]
Message-ID: <3CF0556C.3080706@tmsusa.com> (raw)
In-Reply-To: <mailman.1022340633.6466.linux-kernel2news@redhat.com> <200205260304.g4Q34C301122@devserv.devel.redhat.com>
Pete Zaitcev wrote:
>>[...]
>>Just bought an "HP Multimedia Keyboard Hub" (USB).
>>Using with RedHat 7.2, kernels 2.4.9-81 and also
>>various 2.4.19-pre.
>>
>>
>
>Yeah. I am having a hell of a time with HP keyboards, and
>I would like very much if you can help.
>
>With 7.3 we roll a pretty stock 2.4.19-pre (called 2.4.18-4.x),
>
Oh yeah, it's pretty stock, as long as you
overlook the backported-from-2.5 scheduler -
;-)
next prev parent reply other threads:[~2002-05-26 3:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1022340633.6466.linux-kernel2news@redhat.com>
2002-05-26 3:04 ` USB Keyboard problem Pete Zaitcev
2002-05-26 3:24 ` J Sloan [this message]
2003-05-18 13:07 usb keyboard problem LeVA
-- strict thread matches above, loose matches on Subject: below --
2003-05-18 6:51 LeVA
2002-05-25 15:26 USB Keyboard problem Itai Nahshon
2002-05-25 17:46 ` Randy.Dunlap
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=3CF0556C.3080706@tmsusa.com \
--to=joe@tmsusa.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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