From: Dave MacFarlane <driusan@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Hardware woes
Date: Wed, 29 Jun 2016 10:18:40 -0400 [thread overview]
Message-ID: <CAG2UyHrHgU4H+QrakSuCos88H+GB52rC3UNYEjqW2nY9Xpxhew@mail.gmail.com> (raw)
In-Reply-To: <d6cf618b8f3260a86bb77bc9e5b352a9@felloff.net>
On Wed, Jun 29, 2016 at 3:13 AM, <cinap_lenrek@felloff.net> wrote:
> ok, this is useless. what you want is to log the c parameter only
> which is the byte that was read.
>
> so just print("%.2ux", c); should do. then dont send me screenshots,
> but try to think about what you see, because i have no information
> what you did to the mouse to identify what the bytes are.
That's what I was afraid of, but I don't know what I'm looking for. What's
the expected output of, say, a left click? (It's probably still not very useful
with the noise, but the screenshot after the USB error was literally
just touching
the trackpad, moving about a millimetre to the right, then letting go.)
> you should determine the packet size first... like hold mouse steady, and then
> toggle the buttons, and see how many bytes are printed... once you
> have that you can try identifying where the bits are for the buttons...
>
Okay, but before I get to that my gut feeling tells me that resetmouse()
isn't setting the mode properly for a synaptics (the driver that Linux
says it's using for this) trackpad. It should just emulate a PS/2 mouse by
default according to the documentation that I found
(https://www.aquaphoenix.com/hardware/ledlamp/reference/synaptics_touchpad_interfacing_guide.pdf),
but that clearly isn't happening..
I gather the i8022auxcmd function sends a byte to the mouse. If I look
up the protocol to query the mode, can I just use that function to send
the appropriate byte(s) in resetmouse() and expect the response from
the mouse to get printed? And is there any way I can send arbitrary
bytes from the command line without recompiling the kernel/rebooting?
> there will not be a wireless driver soon, so plug the laptop on the
> ethernet or change the card.
There is no physical ethernet port and I'm pretty sure the Intel card is a
SoC. Are there any USB network dongles that are known to work?
(Either wifi or ethernet)
- Dave
next prev parent reply other threads:[~2016-06-29 14:19 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
2016-06-29 0:00 ` Dave MacFarlane
2016-06-29 7:13 ` cinap_lenrek
2016-06-29 14:18 ` Dave MacFarlane [this message]
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=CAG2UyHrHgU4H+QrakSuCos88H+GB52rC3UNYEjqW2nY9Xpxhew@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).