Is the iwi driver going to be synced with rev. 1.3x of HEAD? I'm using 1.36 along with a RELENG_6 tree, since it works better (read: it works). From the HEAD commit messages I understand that some MFCs would've been in order by now. Are there any show-stoppers that push that schedule ahead ? -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it.
On Monday 10 July 2006 16:40, Vlad GALU wrote:> Is the iwi driver going to be synced with rev. 1.3x of HEAD? I'm > using 1.36 along with a RELENG_6 tree, since it works better (read: it > works). From the HEAD commit messages I understand that some MFCs > would've been in order by now. Are there any show-stoppers that push > that schedule ahead ?no. The only thing that bugs me a bit, is that the change will break POLA for people using the old version. I have yet to hear from somebody using that successfully, though. I will get on MFCing it later today. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060710/84a70897/attachment.pgp
* *> >* I have "device iwi" in my kernel configuration. Should I remove it and *> >* use a module instead? Or is this supposed to work? *> This is from the firmware(9) support code. Add "options firmware" and you > should be fine. You will still need to load the firmware blobs as modules, > but that's another story.I have looked at man 9 firmware and man 9 module, and the /usr/share/examples/kld. My STABLE is as of July 20. firmware_get: failed to load firmware image iwi_bss iwi0: could not load firmware I started by posting this a week ago to -mobile, but, beyond the 'options firmware' suggestion, nobody there had any suggestions.