Linked by Thom Holwerda on Tue 1st May 2007 13:08 UTC, submitted by Jack
Thread beginning with comment 236259
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Just a quick note: many of the Broadcom drivers are now supported in Feisty Fawn. My laptop's Broadcom 4319 card words flawlessly now - no more need for Driverloader. Yay!
But it is a driver that has been developed via trial and error; I don't want to put down the huge amount of work done, but I really can't sleep in bed straight knowing that a piece of equipment I rely on was developed via that process.
Why is it important? because what happens when something goes wrong, and maintenance needs to be done, the specifications aren' there, and broadcom aren't providing any engineering help to track down those issues - atleast in the case of the ipw3945 (and its replacement), it has been developed by Intel, fully opensourced and documented (hence we have 3945 support on other platforms).
Don't get me wrong, I much prefer when the OEM provides their own open-source driver. That said, so far the updated bcm43xx driver has worked flawlessly for me. Apparently, it incorporates some work done by the Apple engineers (in any case, there is a ieee80211-softmac driver also loaded at the same time that is linked to it).
I agree with you, it's not the best situation, but if the driver *is* stable, then it's certainly better than nothing! ;-)







Member since:
2005-07-02
Just a quick note: many of the Broadcom drivers are now supported in Feisty Fawn. My laptop's Broadcom 4319 card words flawlessly now - no more need for Driverloader. Yay!
We can only imagine that Dell will pre-configure these so that they are ready OOTB (or right after first boot, to make sure the kernel isn't distributed with pre-linked closed-source drivers).