Re: [9front] Hardware woes

[Dave MacFarlane <driusan@gmail.com>]

> see iwlpci() function:
>
>                 switch(pdev->did){
>                 default:
>                         continue;
>                 case 0x0084:    /* WiFi Link 1000 */
>                 case 0x4229:    /* WiFi Link 4965 */
>                 case 0x4230:    /* WiFi Link 4965 */
>                 case 0x4232:    /* Wifi Link 5100 */
>                 case 0x4236:    /* WiFi Link 5300 AGN */
>                 case 0x4237:    /* Wifi Link 5100 AGN */
>                 case 0x423d:    /* Wifi Link 5150 */
>                 case 0x423b:    /* PRO/Wireless 5350 AGN */
>                 case 0x0082:    /* Centrino Advanced-N 6205 */
>                 case 0x0085:    /* Centrino Advanced-N 6205 */
>                 case 0x422b:    /* Centrino Ultimate-N 6300 variant 1 */
>                 case 0x4238:    /* Centrino Ultimate-N 6300 variant 2 */
>                 case 0x08ae:    /* Centrino Wireless-N 100 */
>                 case 0x0083:    /* Centrino Wireless-N 1000 */
>                 case 0x0887:    /* Centrino Wireless-N 2230 */
>                 case 0x0888:    /* Centrino Wireless-N 2230 */
>                         break;
>                 }
>
> the device type is read from pci config space Rev register:
>
>                 ctlr->type = (csr32r(ctlr, Rev) >> 4) & 0xF;
>
> the differences are distinguished by that field, like
> the firmware name is indexed by that:
>
>                 fw = readfirmware(fwname[ctlr->type]);
>
> --
> cinap


Okay, I ordered a wired usb dongle with a chipset that nusb/ether says
it supports and gave the IWL driver a quick shot while I wait for that
to ship. it seems that the driver differences aren't as trivial as I
hoped.

I added 0x081b to the switch and it's loading the driver now, but the
ctlr->type id (4) conflicts with the id for Type5150. Since I don't
really care about that chipset right now, I  replaced the firmware for
Type 4 with iwm-7260-9 and took out the references for checking if
Type (==/!= Type5150) throughout the code.

It's using the driver, but after the handover and poweron in iwlinit,
it's finding a bad rom signature.

I had a quick look at the poweron and handover code that preceed the
check in iwlinit, and while handover is pretty generic, there's a
couple chipset specific paths through poweron, so I tried changing:

if(ctlr->type != Type4965 && ctlr->type <= Type1000)

to:

 if(ctlr->type != Type4965 && ctlr->type != Type7620 && ctlr->type <= Type1000)

(Type1000 == 6, which is in an odd order right in the middle of 5xxx
and 6xxx Types, so from what I can tell that "if" statement is just
using an accidental ordering in the identifiers to target 5xxx
chipsets) Still no luck, so I think this requires actually figuring
out what the differences between the iwl and iwm drivers are to get
the 7260 to initialize properly. (I also tried going into the
ctlr->type == Type4965 statement a little further down with no luck.)

I'll probably stop looking into this here, but I figured I'd let
anyone else who wants to look into it know what I found. You're
probably right that it's best to port the iwm driver, even though
Linux manages to get by with a single Intel driver.

- Dave