An easy-to-fix hardware related bug still stuck

[Ma Xiaojun]

On Wed, Jan 23, 2013 at 12:29 PM, Dan Chen <seven.steps at gmail.com> wrote:
> Which is the preferred diff? Marco's (linked from LP) or your second one on
> BTS?

Thank you for your note.

The situation is that the b43 gives two firmware download link one for
3.2+ kernel, one for older kernel.
1. http://linuxwireless.org/en/users/Drivers/b43#If_you_are_using_the_b43_driver_from_3.2_kernel_or_newer:
2. http://linuxwireless.org/en/users/Drivers/b43#If_you_are_using_the_b43_driver_from_older_kernel:

Debian switched to firmware 1 already:
http://anonscm.debian.org/gitweb/?p=collab-maint/b43-fwcutter.git;a=blob;f=debian/firmware-b43-installer.postinst;h=468a4867d9ff73462faac7b8315aa4abfb2dd511;hb=HEAD
Ubuntu seems to stuck on firmware 2:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/raring/b43-fwcutter/raring/view/head:/debian/firmware-b43-installer.postinst

Marco's patch replace firmware 2 with firmware 1 and move 4331 from
unsupported to supported.
It can solve the problem of 4331 but no more.
My patch on BTS doesn't touch firmware downloading since it is already
switched in Debian.
My patch try to update the postinst script's logic to reflect latest
state as shown in b43 wiki:
http://linuxwireless.org/en/users/Drivers/b43#Supported_devices
I definitely moved 4331 to supported but other chips are also revised.

(Sorry Dan, forgot to reply list last time.)