Re: [9front] Hardware woes

[Dave MacFarlane <driusan@gmail.com>]

I got home today ready to dig in and look into this more
systematically after reading
up about all the different modes for synaptic drivers, how to query
and set them, the weird
encoding they do to fit the extended commands into the standard PS2
protocol, etc, booted
into 9front, and.. it worked just fine.

It turns out the problem is that resetmouse() resets the PS2
properties, but the mode
had already been set by the Linux driver from PS2 mode to the absolute
mode where it
includes raw details about touch pressure, size, etc (which 9front is
misinterpreting as
arbitrary PS2 events).. a reboot isn't, technically, "powering on", so
it isn't resetting the
mode to the PS2 emulating default value that it comes up as with on a
cold boot, but leaving
it wherever the last OS left it. As long as I physically power off the
machine and turn it back
on, it works just fine.

On Wed, Jun 29, 2016 at 11:49 AM,  <cinap_lenrek@felloff.net> wrote:
> 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



-- 
- Dave