[Applied][Precise] Add three new Vendor IDS to the BCM20702A0

[Leann Ogasawara]

I've gone ahead and applied patch 2/3 and patch 3/3 to Precise
master-next.  Patch 1/3 was already applied.  I've also modified the
commit messages to mark them as SAUCE.

For Oneiric, don't forget to add the SRU Justification to the bug.    

Thanks,
Leann

On Fri, 2012-01-27 at 18:42 -0500, James M. Leddy wrote:
> [Impact]
> Systems that were enabled and certified on ubuntu don't work with the
> stock version of oneiric. Their bluetooth devices will be disabled
> until they upgrade to precise.
> 
> [Development Fix] 
> Three patches were submitted upstream. One was included in 3.2, the
> other two are undergoing review.
> 
> [Stable Fix]
> Cherry-pick the first patch, clean merge for the other two.
> 
> [Test Case]
> Install oneiric on one of the effected machines. Try to use bluetooth.
> 
> sudo -i
> modprobe btusb
> echo "$USBID" >> /sys/bus/usb/drivers/btusb/new_id
> 
> Where USB is one of "0a5c 21e1", "0a5c 21e3", "0a5c 21e6". If this
> makes bluetooth work, than this SRU will help.
> 
> 
> [Regression Potential] 
> Small. There are no ID conflicts for these devices, so there should be
> no regressions for other bluetooth devices.
> 
> Buglink: https://bugs.launchpad.net/bugs/906832
> 
> Signed-off-by: James M. Leddy <james.leddy at canonical.com>
> 
> 
>