Intel firmwares hit the base system
Published March 2nd, 2007 in FreeBSDWith help from mlaier and sam, I finally committed my first significant contribution to the src tree.
Few months ago, anholt gave me email addresses of people at Intel that would be willing to discuss terms under which we could redistribute their firmwares. After a few emails (and some months), we came to an agreement. I added support for restricted firmwares to firmware(9), mlaier/sam reviewed it and voila!
Commit is here and heads-up is here.
Update: Now, here comes the Press Release!
15 Responses to “Intel firmwares hit the base system”
- 1 Trackback on Aug 10th, 2007 at 3:39 am
Nice one Thoumie, that’s a nice step for Freebsd, I hope there will be hundreds more.
I don’t know why but i start thinking that the future won’t include Windows Vista or Windows programs at all.
Maybe the open source is the future, maybe it’s not but for what it’s worst you did a great job and you still doing it every days in Stillorgan.
But trust me, the coming months please focus a bit more on your personnal life and on bathroom cleaning :=)
Nik
nahh, keep on bringing home the good stuff for FreeBSD
Nik will do the bathroom cleaning
I am sorry to disappoint you, but bathroom cleaning is boring and i won’t do it anymore.
Thoumie will take care of that…
By the way how are the danish girls ? pictures ? :=)
Hah! Girls … i knew it
... it’s why we can’t get x.org 7.2 stable in ports 
Anyway, have fun it’s important to relax sometimes.
Fun is important, of course, he is drunk every single week end!
I think I’m going to start moderating comments.
The previous comment was brought to you by somebody who needed 6 hours to apply a patch.
Thats really great news! Much thanks you for this! When you planning to add 3945 support, and when you planning to MFC this to RELENG_6? Thanks in advance for answer/
I’ll MFC firmwares for iwi(4) in two weeks. Firmwares for ipw(4) will have to wait until we MFC latest ipw(4) changes to RELENG_6 (firmware(9) support being one of them).
The port of OpenBSD wpi(4) driver is still being worked on, there are still a couple of issues left to fix (note: I’m not the one working on it). The firmware will be committed at the same time.
Thank you for answer. And where i can get this version of wpi(4), that is have “couple of issues to fix”? I can to render assistance on testing. (I’m using HP nx7400 with 3495 in it) on -STABLE and -CURRENT.
I’ve put a snapshot of the development version here:
http://people.freebsd.org/~flz/local/wpi/wpi-perforce-20070315.tgz
Be sure to load the firmware before he driver itself. If you get bus_dmamem_alloc errors, just kldunload if_wpi and kldload if_wpi until it goes away (but don’t do that too quickly, I think I got some panics when doing this).
Thank you! I’ll test on this week-end, and provide you with details if you interested.
I’ve done some testing and if you are interested in results:
I have WPA and WPA2 on my AP
Toshiba Tecra m5 106
I made /etc/wpa_supplicant.conf and ssid and psk there.
*** wpi-freebsd-20061109.tgz (I used it before) ***
#kldload if_wpi
Everything works (connecting to AP, key negotiation, dhcpd) exept that on ttyv0 i still gets “rx tail flags error 702” ... but it’s “working”
*** wpi-perforce-20070315.tgz ***
ioctl[SIOCS80211, op 23, arg 0×0]: Invalid argument
Failed to initiate AP scan.
and on ttyv0 i have:
firmware status=0xffffffff need val=0×40400000
wpi0: timeout waiting for adapter to initialize
wpi0: could not lock memory
And it can’t connect.
i’ve been trying to get it working since yesterday on my hp nc6320 running current with no luck.
still can’t get past that ‘bus_dmamem_alloc’ error. kldloads/unloads do not seem to help at all.
i’m willing to help with testing etc too if you need it.
Hi,
I’ve had exactly the same result as ka73ka on my new Asus A8JS. In fact thanks ka73ka for posting, I wouldn’t have tried that version if I hadn’t seen your post.
Ron