summaryrefslogtreecommitdiffstats
path: root/sys/kern/kern_tc.c
diff options
context:
space:
mode:
authorken <ken@FreeBSD.org>2012-03-02 22:00:40 +0000
committerken <ken@FreeBSD.org>2012-03-02 22:00:40 +0000
commit951ff6f5dc68eff004a256c02b55e932b8936136 (patch)
tree60f9b0db23a2ad74e9df4bbe0f0ccb84d3e6cc5c /sys/kern/kern_tc.c
parent85b7bc5919cc1a7927b566cc2c3f632ed1af7656 (diff)
downloadFreeBSD-src-951ff6f5dc68eff004a256c02b55e932b8936136.zip
FreeBSD-src-951ff6f5dc68eff004a256c02b55e932b8936136.tar.gz
Fix a problem that was causing the mpt(4) driver to attach to MegaRAID
cards that should be handled by the mfi(4) driver. The root of the problem is that the mpt(4) driver was masking off the bottom bit of the PCI device ID when deciding which cards to attach to. It appears that a number of the mpt(4) Fibre Channel cards had a LAN variant whose PCI device ID was just one bit off from the FC card's device ID. The FC cards were even and the LAN cards were odd. The problem was that this pattern wasn't carried over on the SAS and parallel SCSI mpt(4) cards. Luckily the SAS and parallel SCSI PCI device IDs were either even numbers, or they would get masked to a supported adjacent PCI device ID, and everything worked well. Now LSI is using some of the odd-numbered PCI device IDs between the 3Gb SAS device IDs for their new MegaRAID cards. This is causing the mpt(4) driver to attach to the RAID cards instead of the mfi(4) driver. The solution is to stop masking off the bottom bit of the device ID, and explicitly list the PCI device IDs of all supported cards. This change should be a no-op for mpt(4) hardware. The only intended functional change is that for the 929X, the is_fc variable gets set. It wasn't being set previously, but needs to be because the 929X is a Fibre Channel card. Reported by: Kashyap Desai <Kashyap.Desai@lsi.com> MFC After: 3 days
Diffstat (limited to 'sys/kern/kern_tc.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud