Comment on OpenBSD 6.3 releasedparentComments−cat1998yhttp://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_...indicates: static const struct pci_matchid bwfm_pci_devices[] = { { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM43602 }, { PCI_VENDOR_BROADCOM, PCI_PRODUCT_BROADCOM_BCM4350 }, }; those are hex codes defined in:http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/pci...as: vendor BROADCOM 0x14e4 Broadcom product BROADCOM BCM4350 0x43a3 BCM4350 product BROADCOM BCM43602 0x43ba BCM43602 so if you're not sure, checking boot up dmesg on OpenBSD or lspci on linux should give the hexcode of your device which should match 0x14e4 + one of the other two..−peatmoss8yOoh! Interesting. I've a ~2 year old Macbook Pro with the 43602 chipset. Would be lovely to be able to run OpenBSD on it without wifi dongles.
Comments
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_...
indicates:
those are hex codes defined in:http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/pci...
as:
so if you're not sure, checking boot up dmesg on OpenBSD or lspci on linux should give the hexcode of your device which should match 0x14e4 + one of the other two..Ooh! Interesting. I've a ~2 year old Macbook Pro with the 43602 chipset. Would be lovely to be able to run OpenBSD on it without wifi dongles.