From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] Hardware woes
Date: Wed, 29 Jun 2016 17:49:05 +0200 [thread overview]
Message-ID: <33360206290d8284b8a53a1367b08c97@felloff.net> (raw)
In-Reply-To: <CAG2UyHrHgU4H+QrakSuCos88H+GB52rC3UNYEjqW2nY9Xpxhew@mail.gmail.com>
touching would indeed produce tons of noise. thats why i suggested you
press a button in an attept to produce a single packet response. but
i have no idea what your computer is like. there might not even be
physical buttons anymore.
your suspicion that it is in the wrong mode is plausible... the pc
mouse driver is not aware of any synaptic protocols. why the bios
set it to non-ps2 emulation mode is the question.
yes, i8042auxcmd() sends a raw byte to the mouse.
no, there is no driver to write the aux port from userspace,
tho you could make one with addarchfile() and writing a functions.
nusb/ether supports some chips as well as generic usb ethernet devices,
but i cannot guarantee if they will work. no real ethernet sucks, as
this also means it will be impossible to pxe boot this machine (very
convenient for writing drivers).
good luck.
--
cinap
next prev parent reply other threads:[~2016-06-29 15:49 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
2016-06-29 15:24 ` stanley lieber
2016-06-29 15:49 ` cinap_lenrek [this message]
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=33360206290d8284b8a53a1367b08c97@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).