Steve,
A few Iwn drivers *are* supported, mine being iwn 4965 -- is
supported and has been committed to 8.0-CURRENT. You can find more
information about development on this hardware here :
http://www.clearchain.com/blog/posts/iwn. I'm pretty sure that there
is not that much work done on your
jT wrote:
Steve,
A few Iwn drivers *are* supported, mine being iwn 4965 -- is
supported and has been committed to 8.0-CURRENT. You can find more
information about development on this hardware here :
http://www.clearchain.com/blog/posts/iwn. I'm pretty sure that there
is not that much work
Sam,
I know you are busy, but can you explain what about my response was
wrong when you say doesn't require sysctl ack -- you mean
acknowledgment? I just would like to know for my future reference and
Steve sorry for my misinformation.
iwn firmware does not require a sysctl ack.
Sam
On Monday 17 November 2008 05:27:48 jT wrote:
I know you are busy, but can you explain what about my response was
wrong when you say doesn't require sysctl ack -- you mean
acknowledgment? I just would like to know for my future reference and
Steve sorry for my misinformation.
the firmware
The 4965 firmware license does not require an ack via the loader
tunable. This used to be true but was changed recently as I was
mistaken about the license (only iwi and ipw firmware requires the end
user acknowledge the EULA).
Everything else that was said seemed spot on.
Sam
jT wrote:
On Sun, Nov 16, 2008 at 09:19:49PM -0500, jT wrote:
Yes it will require a firmware blob as the 4965 one does. You are
required to take notice to the legal aspects of the blob via setting a
key in loader.conf.
The firmware blob here is simply a large binary file that is loaded
directly into
6 matches
Mail list logo
