From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Greg KH" <greg@kroah.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Andries Brouwer" <aebr@win.tue.nl>,
"Vojtech Pavlik" <vojtech@suse.cz>
Subject: Re: Trying to run 2.6.0-test3
Date: Mon, 18 Aug 2003 19:35:09 +0900 [thread overview]
Message-ID: <151801c36577$10e4f5a0$1aee4ca5@DIAMONDLX60> (raw)
In-Reply-To: 1061141113.21878.76.camel@dhcp23.swansea.linux.org.uk
"Alan Cox" <alan@lxorguk.ukuu.org.uk> replied to me.
> > accept a USB keyboard but they refused. The patch which I sent to Vojtech
> > Pavlik was ignored and these two keys continued not to work (except on my
> > machine). Finally Mike Fabian accepted a gift of a USB keyboard and this
> > defect in Linux got fixed. But only for somewhere around the last half of
> > the 2.4 releases, not for 2.6.
> > What will it take this time?
>
> Posting the patch with any luck ?
Hirofumi Ogawa posted a patch for the yen-sign pipe key on 2003.07.23 for
test1 but his patch still didn't get into test3. On a PS/2 keyboard that
seems to be the only key with any problem.
Yesterday when I finally tried a USB keyboard and found that the backslash
underbar has the same problem, maybe I was the first person to even try a
Japanese USB keyboard in 2.6, and maybe no one at all tried some number of
2.5 series kernels. As mentioned, usually I can only spend one day a week
testing 2.6. I'll try to spend one day next weekend trying to figure out
the new necessary patch. If I succeed, but if it gets ignored again, I'll
probably rejoin the set of users who never have time to test.
I really do think that if Andries Brouwer or Vojtech Pavlik would accept a
gift of a USB keyboard then this kind of bug would be avoided a lot earlier.
next prev parent reply other threads:[~2003-08-18 10:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 9:57 Trying to run 2.6.0-test3 Norman Diamond
2003-08-17 17:25 ` Alan Cox
2003-08-18 10:35 ` Norman Diamond [this message]
2003-08-18 11:00 ` Vojtech Pavlik
2003-08-23 12:29 ` Norman Diamond
2003-08-25 14:24 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2003-08-18 11:37 John Bradford
2003-08-17 7:59 Norman Diamond
2003-08-17 13:33 ` Russell King
2003-08-18 10:41 ` Norman Diamond
2003-08-18 11:21 ` Russell King
2003-08-15 8:11 Norman Diamond
2003-08-15 8:53 ` Felipe Alfaro Solana
2003-08-15 10:00 ` Norman Diamond
2003-08-15 11:53 ` Felipe Alfaro Solana
2003-08-15 13:20 ` Norman Diamond
2003-08-15 15:02 ` Felipe Alfaro Solana
2003-08-16 13:21 ` Norman Diamond
2003-08-15 10:14 ` Russell King
2003-08-15 12:39 ` Norman Diamond
2003-08-15 13:04 ` Mikael Pettersson
2003-08-17 1:51 ` Norman Diamond
2003-08-15 16:43 ` Joshua Kwan
2003-08-15 17:06 ` Randy.Dunlap
2003-08-15 17:15 ` Russell King
2003-08-15 17:16 ` Greg KH
2003-08-16 13:20 ` Norman Diamond
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='151801c36577$10e4f5a0$1aee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=aebr@win.tue.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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).