I had to add an entry to sys/conf/files to get things to go -

is this intentional due to the 'newness' of the driver?

looking forward to testing it - thanks for undoing the fighting over
this chipset sephe!

- Chris

Since this driver is reverse engineered, the "attach" code path may be
not safe enough for it to go into 'kernel'.  I think loading it as
module is the safest way.  And (mini)PCIe parts (4311/4312, newer
amd64 based Dell laptops use them) probably do not work yet (missing
small fraction of initialization code).

Best Regards,
sephe

-- 
Live Free or Die

doh.. I think I'm in the latter category ..

pciconf -lv shows:

  none3@pci7:0:0: class=0x028000 card=0x03191468 chip=0x432814e4
    rev=0x01 hdr=0x00
    vendor   = 'Broadcom Corporation'
    device   = 'BCM43XNM 802.11n Network Adapter'
    class    = network

I'll probably try to force the probe tomorrow and watch the hilarity ensue!

Thanks again.

- Chris

-- 
Live Free or Die

Thanks for saving the trouble - does this mean support is not currently
in the driver, or that it is 'less supportable' (e.g. would need to do
some more reverse engineering, etc) - trying to estimate what the time
would take..

Thanks,

- Chris

It is not supported (no reverse engineering document).  But you can
try adding the PCI ids into the driver.  If there is 802.11 MAC, 11b/g
PHY and 2050 RF things may work.

Best Regards,
sephe

-- 
Live Free or Die

Thanks for the info..

for the record, this chip did not work after a simple pcidevs
update with error as follows

bwi0: <Broadcom BCM43XNM 802.11 Wireless Lan> [tentative] irq 11 at
device 0.0 on pci7
pcib5: device bwi0 requested unsupported memory range 0x0-0xffffffff
(decoding 0x0-0x0, 0x0-0x0)
bwi0: 0x4000 bytes at rid 0x10 res 3 failed (0, 0xffffffff)
bwi0: can't allocate IO memory
device_probe_and_attach: bwi0 attach returned 6

I'll try to keep checking the status on their spec 'engineering' page
here & there and if I  see anything promising will take a crack at it.

Thanks,

- Chris

Doh! missed this - good thing, because the sys/conf/files tweak didn't
work :)