trying patch bwn for BCM4352

[Firecrow]

Hi all,
>From more research on the web I've concluded that it takes more than 
patching in the pci id, sorry for spamming the list.

~fire

On March 21, 2018 7:23:41 PM Firecrow <fire at firecrow.com> wrote:

> Hi all,
> sent this message while still composing it, I'm tying to get BCM4352 to 
> work on my freebsd current machine.
>
> here is some information about my machine and what I've been trying
>
> uname -a
> FreeBSD ant.firecrow.com 12.0-CURRENT FreeBSD 12.0-CURRENT #3: Wed Mar 21 
> 23:01:07 EDT 2018
>
> I'm working under the assumption that the broadcom chipset is compatible 
> with an existing driver it just needs the pci information linked in, so 
> I've tried to add the interfaces to if_bwn_pci.c
> >
> > diff src.orig/sys/dev/bwn/if_bwn_pci.c  src/sys/dev/bwn/if_bwn_pci.c
> > 54c54
> > < static int attach_untested = 0;
> > ---
> > > static int attach_untested = 1;
> > 86a87,89
> > >       BWN_BCM_DEV(BCM4352_D11AC ,     "BCM4352 802.11n Dual-Band:/",  0),
> > >       BWN_BCM_DEV(BCM4352_D11AC2G,    "BCM4352 802.11n 2G:/", 0),
> > >       BWN_BCM_DEV(BCM4352_D11AC5G,    "BCM4352 802.11n 5G:/", 0),
> > 91d93
> > <
> > 306a309
> > >
>
> dmesg shows that it recognizes the device, but the usual information from a 
> network device is not listed, as if the device is registered but not 
> treated as a network device.
> > dmesg | grep bwn
> > bwn_pci0: <Broadcom BCM4352 802.11n Dual-Band:/ Wireless> mem
> > 0xfc600000-0xfc607fff,0xfc400000-0xfc5fffff irq 35 at device 0.0 on pci6
> > bhndb0: <PCI-BHND bridge> on bwn_pci0
> > bhndb0: Using MSI interrupts on bwn_pci0
>
> all help welcome
> ~fire
> _______________________________________________
> freebsd-wireless at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe at freebsd.org"