diff options
| author | Matt Carlson <mcarlson@broadcom.com> | 2011-11-28 09:41:03 +0000 |
|---|---|---|
| committer | Ben Hutchings <ben@decadent.org.uk> | 2012-10-10 03:31:34 +0100 |
| commit | 3a0d367c4e7e016ed18c2aec5e0734f20e3e45df (patch) | |
| tree | 0a8787d7aead910631470867373aee069f1f31a2 /drivers/bluetooth | |
| parent | c660b90b1ac6a005f3c46e7d359dcacf86007336 (diff) | |
| download | kernel_samsung_smdk4412-3a0d367c4e7e016ed18c2aec5e0734f20e3e45df.zip kernel_samsung_smdk4412-3a0d367c4e7e016ed18c2aec5e0734f20e3e45df.tar.gz kernel_samsung_smdk4412-3a0d367c4e7e016ed18c2aec5e0734f20e3e45df.tar.bz2 | |
tg3: Fix TSO CAP for 5704 devs w / ASF enabled
[ Upstream commit cf9ecf4b631f649a964fa611f1a5e8874f2a76db ]
On the earliest TSO capable devices, TSO was accomplished through
firmware. The TSO cannot coexist with ASF management firmware though.
The tg3 driver determines whether or not ASF is enabled by calling
tg3_get_eeprom_hw_cfg(), which checks a particular bit of NIC memory.
Commit dabc5c670d3f86d15ee4f42ab38ec5bd2682487d, entitled "tg3: Move
TSO_CAPABLE assignment", accidentally moved the code that determines
TSO capabilities earlier than the call to tg3_get_eeprom_hw_cfg(). As a
consequence, the driver was attempting to determine TSO capabilities
before it had all the data it needed to make the decision.
This patch fixes the problem by revisiting and reevaluating the decision
after tg3_get_eeprom_hw_cfg() is called.
Signed-off-by: Matt Carlson <mcarlson@broadcom.com>
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'drivers/bluetooth')
0 files changed, 0 insertions, 0 deletions