On 12 Nov 2018, at 22:03, Adrian Chadd wrote:
> yeah, that we'll have to look into..
I was going to say that might be easy:
Index: sys/conf/files
===================================================================
--- sys/conf/files (revision 340282)
+++ sys/conf/files (working copy)
@@ -2577,6 +2577,7 @@ dev/ofw/ofw_subr.c optional fdt
dev/ofw/ofwbus.c optional fdt
dev/ofw/openfirm.c optional fdt
dev/ofw/openfirmio.c optional fdt
+dev/otus/if_otus.c optional otus
dev/ow/ow.c optional ow \
dependency "owll_if.h" \
dependency "own_if.h"
but you probably also want otusfw?
>
> On Mon, 12 Nov 2018 at 13:33, tech-lists <[email protected]> wrote:
>
>> On Mon, Nov 12, 2018 at 12:32:25PM -0800, Adrian Chadd wrote:
>>> If it's showing up like that then it's not an AR9170 device; it's a
>>> broadcom firmware device. :(
>>
>> yeah. In tiny lettering it has "v2" next to the WNDA3100 so this seems
>> to be a completely different chipset
>>
>> But what about the otus(4) manpage? Says you can compile device otus
>> into kernel, but buildkernel says device unknown.
>>
>> thanks,
>> --
>> J.
>>
>> _______________________________________________
>> [email protected] mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
>> To unsubscribe, send any mail to "[email protected]
>> "
>>
> _______________________________________________
> [email protected] mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[email protected]"
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "[email protected]"
