From: "Forever shall I be." <zinx@magenet.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.4.0-ac8 PS/2 mouse woes
Date: Fri, 12 Jan 2001 19:11:32 -0600 [thread overview]
Message-ID: <20010112191132.A548@bliss.zebra.net> (raw)
In-Reply-To: <20010112173811.A618@bliss.zebra.net> <E14HE9V-0005ID-00@the-village.bc.nu>
In-Reply-To: <E14HE9V-0005ID-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sat, Jan 13, 2001 at 12:02:35AM +0000
On Sat, Jan 13, 2001 at 12:02:35AM +0000, Alan Cox wrote:
> > pc_keyb.c.. I also have the cuecat patch applied, and use it over
> > the PS/2 mouse port, but I don't think it's interfering.. I doubt
> > this will be noticable to people not using the "Resolution" option to
> > speed up the mouse, and mine's rather insane:
>
> Can you tell me if the problem can be duplicated without the cuecat patch
> applied. It is quite possible the ps/2 mouse patch is buggy
Yes, and I tried out 2.4.0-ac7 too, just for kicks, and it doesn't break
with ac7..
>
> > Anyway, just letting you know, and very sorry for the lack of
> > information..
>
> Its most of the info I need. Since I churn through patches fast we can normally
> get a good guess at the culprit.
>
> Alan
>
Also, the Oops I got is apparently due to my own code, so I'll be trying
to fumble my way through fixing it :)
--
Zinx Verituse (See headers for gpg key info)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-13 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 23:38 [BUG] 2.4.0-ac8 PS/2 mouse woes Forever shall I be.
2001-01-13 0:02 ` Alan Cox
2001-01-13 1:11 ` Forever shall I be. [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=20010112191132.A548@bliss.zebra.net \
--to=zinx@magenet.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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