Date: Sat, 30 Nov 2013 14:11:25 -0800 From: Adrian Chadd <adrian@freebsd.org> To: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: [iwn] scan fixes! Message-ID: <CAJ-VmonEKtYNVxUXgmHLmZ7yeUD0yjz1MTjv1JAPU_Wx36gpNw@mail.gmail.com> In-Reply-To: <CAJ-VmokichutcLwakRwVQRzq=PeEUYCgbYqFP8Yr9KUydYK6eA@mail.gmail.com> References: <CAJ-VmokichutcLwakRwVQRzq=PeEUYCgbYqFP8Yr9KUydYK6eA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I've tested this now on the Intel 5100 and the Centrino-N 2200 (specifically to keep eadler@ happy!) It turns out that yes, the 2200 works fine, and it also exposes the firmware TLV "flags" field, which includes a bunch of things: iwn1: iwn_read_firmware_tlv: feature: 0x0000000b So that is 1011 - P2P (bit 3), NEWSCAN (bit 1), and PAN (bit 0.) The NEWSCAN bit changes the behaviour of the scan command a little. Seems to behave fine on both the 5100 (no flags TLV, so no NEWSCAN) and 2200 (NEWSCAN.) -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonEKtYNVxUXgmHLmZ7yeUD0yjz1MTjv1JAPU_Wx36gpNw>