#
a10c6f55 |
| 11-Nov-2012 |
Neel Natu <neel@FreeBSD.org> |
IFC @ r242684
|
#
23090366 |
| 04-Nov-2012 |
Simon J. Gerraty <sjg@FreeBSD.org> |
Sync from head
|
#
c39df789 |
| 22-Oct-2012 |
Eitan Adler <eadler@FreeBSD.org> |
Now that device disabling is generic, remove the non-standard implementation from mpt
Don't MFC this to retain backwards compatibility.
Reviewed by: des, mjacob Approved by: cperciva
|
#
6fbce250 |
| 22-Oct-2012 |
Eitan Adler <eadler@FreeBSD.org> |
Remove unused code since the 5.x days
Reviewed by: des, scottl Approved by: cperciva MFC after: 1 week
|
#
6a068746 |
| 15-May-2012 |
Alexander Motin <mav@FreeBSD.org> |
MFC
|
#
38f1b189 |
| 26-Apr-2012 |
Peter Grehan <grehan@FreeBSD.org> |
IFC @ r234692
sys/amd64/include/cpufunc.h sys/amd64/include/fpu.h sys/amd64/amd64/fpu.c sys/amd64/vmm/vmm.c
- Add API to allow vmm FPU state init/save/restore.
FP stuff discussed with: kib
|
#
7ab97117 |
| 10-Apr-2012 |
Gleb Smirnoff <glebius@FreeBSD.org> |
Merge head r233826 through r234091.
|
Revision tags: release/8.3.0_cvs, release/8.3.0 |
|
#
bb16310a |
| 04-Apr-2012 |
Marius Strobl <marius@FreeBSD.org> |
Refine r233827; as it turns out, controllers with a device ID of 0x0059 can be upgraded to MegaRAID mode, in which case mfi(4) should attach to these based on the sub-vendor and -device ID instead (n
Refine r233827; as it turns out, controllers with a device ID of 0x0059 can be upgraded to MegaRAID mode, in which case mfi(4) should attach to these based on the sub-vendor and -device ID instead (not currently done). Therefore, let mpt_pci_probe() return BUS_PROBE_LOW_PRIORITY. While it, let mpt_pci_probe() return BUS_PROBE_DEFAULT instead of 0 in the default case.
MFC after: 3 days
show more ...
|
#
992e4f5d |
| 03-Apr-2012 |
Gleb Smirnoff <glebius@FreeBSD.org> |
Merge head r233826 through r233848 to projects/pf/head.
|
#
6fe8be54 |
| 03-Apr-2012 |
Marius Strobl <marius@FreeBSD.org> |
Fix probing of SAS1068E with a device ID of 0x0059 after r232411. Reported by: infofarmer
MFC after: 3 days
|
#
8833b15f |
| 03-Apr-2012 |
Gleb Smirnoff <glebius@FreeBSD.org> |
Merge head r232686 through r233825 into projects/pf/head.
|
#
24a0e7ee |
| 24-Mar-2012 |
Marius Strobl <marius@FreeBSD.org> |
As it turns out, mpi_cnfg.h already is included by mpt.h.
|
#
fd61f421 |
| 24-Mar-2012 |
Marius Strobl <marius@FreeBSD.org> |
- Use the PCI ID macros from mpi_cnfg.h rather than duplicating them here. Note that this driver additionally probes some device IDs for the most part not know to other MPT drivers, if at all. So
- Use the PCI ID macros from mpi_cnfg.h rather than duplicating them here. Note that this driver additionally probes some device IDs for the most part not know to other MPT drivers, if at all. So rename the macros not present in mpi_cnfg.h to match the naming scheme in the latter and but suffix them with a _FB in order to not cause conflicts. - Like mpt_set_config_regs(), comment out mpt_read_config_regs() as the content of the registers read isn't actually used and both functions aren't exactly up to date regarding the possible layouts of the BARs (these function might be helpful for debugging though, so don't remove them completely). - Use DEVMETHOD_END. - Use NULL rather than 0 for pointers. - Remove an unusual check for the softc being NULL. - Remove redundant zeroing of the softc. - Remove an overly banal and actually partly incorrect as well as partly outdated comment regarding the allocation of the memory resource.
MFC after: 3 days
show more ...
|
#
867099fa |
| 08-Mar-2012 |
Gleb Smirnoff <glebius@FreeBSD.org> |
Merge head up to r232685 to projects/pf/head.
|
#
aa6e8dfd |
| 02-Mar-2012 |
Kenneth D. Merry <ken@FreeBSD.org> |
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
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
show more ...
|
#
9dba179d |
| 17-Feb-2012 |
Bjoern A. Zeeb <bz@FreeBSD.org> |
IFC @231845
Sponsored by: Cisco Systems, Inc.
|
#
04016bcf |
| 11-Feb-2012 |
Marius Strobl <marius@FreeBSD.org> |
Flesh out support for SAS1078 and SAS1078DE (which are said to actually be the same chip): - The I/O port resource may not be available with these. However, given that we actually only need this re
Flesh out support for SAS1078 and SAS1078DE (which are said to actually be the same chip): - The I/O port resource may not be available with these. However, given that we actually only need this resource for some controllers that require their firmware to be up- and downloaded (which excludes the SAS1078{,DE}) just handle failure to allocate this resource gracefully when possible. While at it, generally put non-fatal resource allocation failures under bootverbose. - SAS1078{,DE} use a different hard reset protocol. - Add workarounds for the 36GB physical address limitation of scatter/ gather elements of these controllers.
Tested by: Slawa Olhovchenkov
PR: 149220 (remaining part)
show more ...
|
Revision tags: release/9.0.0 |
|
#
a73cbbef |
| 04-Nov-2011 |
Doug Ambrisko <ambrisko@FreeBSD.org> |
Change mpt(4) probe to be an exact match to a PCI device ID. The current code makes the mpt(4) check for 0x005A and mistakenly attach to a mfi(4) device 0x005B. Without this fix, mpt(4) will panic
Change mpt(4) probe to be an exact match to a PCI device ID. The current code makes the mpt(4) check for 0x005A and mistakenly attach to a mfi(4) device 0x005B. Without this fix, mpt(4) will panic if this mfi(4) card is in the system.
Reviewed by: mjacob
show more ...
|
#
fab4c373 |
| 16-Sep-2011 |
Peter Grehan <grehan@FreeBSD.org> |
IFC @ r225592
sys/dev/bvm/bvm_console.c - move up to the new alt-break order.
|
#
cf914969 |
| 15-Aug-2011 |
Justin T. Gibbs <gibbs@FreeBSD.org> |
Integrate FreeBSD/head into projects/zfsd/head as of SVN revision 224870.
|
#
87e255ac |
| 29-Jul-2011 |
Marius Strobl <marius@FreeBSD.org> |
- Staticize functions as appropriate and comment out unused ones. - Sprinkle some const where appropriate. - Consistently use target_id_t for the target parameter of mpt_map_physdisk() and mpt_is_r
- Staticize functions as appropriate and comment out unused ones. - Sprinkle some const where appropriate. - Consistently use target_id_t for the target parameter of mpt_map_physdisk() and mpt_is_raid_volume(). - Fix some whitespace bugs.
Approved by: re (kib)
show more ...
|
#
bd2228ab |
| 19-Jul-2011 |
Peter Grehan <grehan@FreeBSD.org> |
IFC @ r224187
|
#
935205e2 |
| 17-Jul-2011 |
Justin T. Gibbs <gibbs@FreeBSD.org> |
Integrate from Head into ZFSD feature branch as of revision r224141.
|
#
caa59dc8 |
| 13-Jul-2011 |
Marius Strobl <marius@FreeBSD.org> |
- For SAS but neither FC nor SPI controllers default to using MSI (still allowing their use to be disabled via device hints though). This matches what the corresponding Linux driver provided by L
- For SAS but neither FC nor SPI controllers default to using MSI (still allowing their use to be disabled via device hints though). This matches what the corresponding Linux driver provided by LSI does. Tested with SAS1064. - There's no need to keep track of the RIDs used. - Don't allocate MSI/MSI-X as RF_SHAREABLE. - Remove a comment which no longer applies since r209599. - Assign NULL rather than 0 to pointers.
MFC after: 1 month
show more ...
|
#
82b26378 |
| 13-Jul-2011 |
Marius Strobl <marius@FreeBSD.org> |
Remove extra empty lines.
|