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)
@
On Mon, Nov 12, 2018 at 09:33:01PM +, tech-lists 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 b
yeah, that we'll have to look into..
-a
On Mon, 12 Nov 2018 at 13:33, tech-lists 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
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)
If it's showing up like that then it's not an AR9170 device; it's a
broadcom firmware device. :(
-a
On Mon, 12 Nov 2018 at 12:08, tech-lists wrote:
> Hi,
>
> context:
> freebsd-12-beta4 on amd64 and freebsd-12 on arm64, I'm trying right now
> with amd64 r340354.
>
> I have a Netgear WNDA3100
