On Thu, Feb 6, 2014 at 11:54 AM, Larry Finger <larry.fin...@lwfinger.net> wrote: > Because Broadcom uses Linux for the OS in their routers
Didn't know they made consumer routers or published any GPL packages, I think you meant people like Linksys do, not Broadcom. I'll search broadcom site more for this though. > Not all of Broadcom's drivers are suitable. For example, it has never seemed > fruitful to download 300-500 MB of stuff to extract approximately 1 MB of > firmware. My repository contains files that are no larger than ~10 MB. If it's critical download/space issue for devs to check for new firmware revs, I'll download and unpack any links to big GPL zipfiles that people send me. The 10MB was first reached with some microcode 5xx and up, now it's at least 20MB, but the links are in fwcutter_list.h for people. As usual, 7z compresses apsta.o the best to under 20% original size, so under 6MB for all those redistributable apsta.o's. > Windows drivers are stripped to the point that the firmware locations are > not easily determined, thus I avoid them. Wondered about that since all I've seen are the GPL apsta.o ones that objdump probably only works with (never tried to find any windows drivers with fw inside to try to mklist them). Anyway, my question was mostly about what the fw/mic xxx.xx and driver x.x.x.x number relation was (none really), and whether any new fw was always simply cuttable, loadable and expected to work as such (not necessarily). I get that now. Thanks. _______________________________________________ b43-dev mailing list b43-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/b43-dev
