Re: [9front] Hardware woes

[Dave MacFarlane <driusan@gmail.com>]

Okay, well, now I've got my choice of other hardware problems to try
and work on.

WiFi:
1. I've got one of these:
http://www.canakit.com/raspberry-pi-wifi.html gathering dust on a
shelf. The firmware in Linux is rt2870.bin (despite the chipset being
5390) and I noticed in /sys/src/9/pc/etherrt2860.c there's some code
about 2870, so figured there's a chance it'll just work. I plugged it
in and it's not even generating an event in /dev/usbevent. I know the
USB port works, because it's the same one I used to copy the firmware
into /lib/firmware. What would stop it from even noticing that the
dongle was plugged in?
2. I decided to look into the difference between the iwm driver from
OpenBSD (https://github.com/rpaulo/iwm/blob/master/driver/if_iwmreg.h)
and iwl from 9front
(http://www.9front.org/9front/sys/src/9/pc/etheriwl.c). From what I
can tell, every register and offset I compared seemed to have the same
format, so I'm tempted to just add the type to fwname[] and see what
happens. If that works, it'll be better than being forced to have a
usb port.. but I don't know how to figure out the ID for the type to
add to the enum above it. I added a print statement to setfwinfo() and
added ether0=type=iwl to my plan9.ini, but it doesn't seem to be
making it there. Is there something else I need to do to force the
driver or an easier way to probe the id?

Other:
3. 9front crashes whenever I plug in or unplug the power cable. I
assume there's a problem with the APM, but I can't seem to find where
that code lives.
4. I'm tempted to write a proper synaptic touch driver since the
packets seem to be pretty well documented, but the above are probably
more important..

On Wed, Jun 29, 2016 at 8:05 PM,  <cinap_lenrek@felloff.net> wrote:
> you got it! excellent :-)
>
> --
> cinap



-- 
- Dave