From: Dave MacFarlane <driusan@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Hardware woes
Date: Tue, 28 Jun 2016 19:56:05 -0400 [thread overview]
Message-ID: <CAG2UyHop_1vPmJeDvW6hBGt_Ksf4_TYFyg4wcuE2yRNdVgpSOQ@mail.gmail.com> (raw)
In-Reply-To: <f92b9f87c8486521e78a767af873cd3b@felloff.net>
I've tried both ps2 and ps2intellimouse, and both have the same problem.
I added a statement to just print the parameters in ps2mouseputc
because I don't know what else is relevant, and this is what I get
from dragging my finger slightly to the right (is there a better way
to do this? Keeping in mind I don't have wifi on the machine so can't
just log it to a file to send..):
http://driusan.github.io/plan9/9frontmouse.jpg
(everything after the error message in the screenshot from unplugging
the usb mouse. I couldn't tell you what I was doing in the screenshot
before the error message. Something on the trackpad..)
On Mon, Jun 27, 2016 at 8:48 PM, <cinap_lenrek@felloff.net> wrote:
> for the mouse, it seems that your trackpad is sending packets in
> some strange way.
>
> the ps2 mouse packets are processed in /sys/src/9/pc/mouse.c in the
> function ps2mouseputc(), which gets called for each byte received
> from the ps2 port. so putting a debug print at the start of that
> function can reveal what we get. it might be just that you have
> to specify "ps2intellimouse" at the "mouseport is" question
> (defaults to ps2).
>
> this wireless card probably needs a new driver, given that openbsd
> made a new one (iwm(4)) for that card family. i have not looked
> into this.
>
> --
> cinap
--
- Dave
next prev parent reply other threads:[~2016-06-28 23:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 21:53 Dave MacFarlane
2016-06-27 23:31 ` [9front] " kokamoto
2016-06-27 23:45 ` Dave MacFarlane
2016-06-28 0:48 ` cinap_lenrek
2016-06-28 23:56 ` Dave MacFarlane [this message]
2016-06-29 0:00 ` Dave MacFarlane
2016-06-29 7:13 ` cinap_lenrek
2016-06-29 14:18 ` Dave MacFarlane
2016-06-29 15:24 ` stanley lieber
2016-06-29 15:49 ` cinap_lenrek
2016-06-29 23:45 ` Dave MacFarlane
2016-06-30 0:05 ` cinap_lenrek
2016-07-01 0:45 ` Dave MacFarlane
2016-07-01 10:27 ` cinap_lenrek
2016-07-01 20:42 ` Dave MacFarlane
2016-07-01 21:11 ` cinap_lenrek
2016-07-03 22:55 ` Dave MacFarlane
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=CAG2UyHop_1vPmJeDvW6hBGt_Ksf4_TYFyg4wcuE2yRNdVgpSOQ@mail.gmail.com \
--to=driusan@gmail.com \
--cc=9front@9front.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).