summaryrefslogtreecommitdiffstats
path: root/share/man/man4/ahci.4
Commit message (Collapse)AuthorAgeFilesLines
* MFC r280451:mav2015-08-221-6/+0
| | | | | | | Remove from legacy ata(4) driver support for hardware, supported by newer and more functional drivers ahci(4), siis(4) and mvs(4). This removes about 3400 lines of code, unused since FreeBSD 9.0 release.
* Refactor enclosure manegement support in ahci(4). Move it out into separatemav2012-07-261-7/+10
| | | | | | | | | subdevice ahciem. Emulate SEMB SES device from AHCI LED interface to expose it to users in form of ses(4) CAM device. If we ever see AHCI controllers supporting SES of SAF-TE over I2C as described by specification, they should fit well into this new picture. Sponsored by: iXsystems, Inc.
* Avoid hard sentence break.marius2012-06-181-2/+3
| | | | MFC after: 3 days
* mdoc: minor Bl improvements.joel2012-06-021-2/+5
|
* General mdoc(7) and typo fixes.gjb2012-05-121-1/+1
| | | | | | PR: 167776 Submitted by: Nobuyuki Koganemaru (kogane!jp.freebsd.org) MFC after: 3 days
* Fix names of some Marvell SATA chips. It looks like chips with proprietarymav2012-03-021-1/+1
| | | | | | | | interface supported by mvs(4) are 88SX, while AHCI-like chips are 88SE. PR: kern/165271 Submitted by: Jia-Shiun Li <jiashiun@gmail.com> MFC after: 1 week
* Mention that Cold Presence Detection feature used for hot-plug detectionmav2011-12-061-4/+4
| | | | when interface power management is enabled.
* Add hw.ahci.force tunable to control whether AHCI drivers should attachmav2011-12-021-1/+4
| | | | | | | | | | to known AHCI-capable chips (AMD/NVIDIA), configured for legacy emulation. Enabled by default to get additional performance and functionality of AHCI when it can't be enabled by BIOS. Can be disabled to honor BIOS settings if needed for some reason. MFC after: 1 month
* Add support for "LED" enclosure management messages, defined by the AHCI.mav2011-05-171-1/+19
| | | | | | | | | When supported by hardware, this allows to control per-port activity, locate and fault LEDs via the led(4) API for localization and status reporting purposes. Supporting AHCI controllers may transmit that information to the backplane controllers via SGPIO interface. Backplane controllers interpret received statuses in some way (IBPI standard) to report them using present indicators.
* Change licenses of my manual pages to the recommended 2-clause form.mav2010-09-151-12/+11
| | | | Suggested by: joel
* Add links to cam(4).mav2010-03-041-2/+2
|
* Some style and language improvements.mav2010-03-021-12/+16
| | | | Submitted by: ru
* Note added FIS-based switching support.mav2010-01-281-6/+7
|
* MFp4:mav2009-08-301-1/+16
| | | | | | | | | | | - Add Command Completion Coalescing support. - Add SNTF support. - Add two more power management modes (4, 5), implemented on driver level. - Fix interface mode setting. - Reduce interface reset time. - Do not report meaningless protocol/transport versions. - Report CAP2 register content. - Some performance optimizations.
* PMP provides 16 targets (15 drives + itself).mav2009-07-251-1/+1
| | | | Approved by: re (implicitly)
* Separate the parallel scsi knowledge out of the core of the XPT, andscottl2009-07-101-0/+132
modularize it so that new transports can be created. Add a transport for SATA Add a periph+protocol layer for ATA Add a driver for AHCI-compliant hardware. Add a maxio field to CAM so that drivers can advertise their max I/O capability. Modify various drivers so that they are insulated from the value of MAXPHYS. The new ATA/SATA code supports AHCI-compliant hardware, and will override the classic ATA driver if it is loaded as a module at boot time or compiled into the kernel. The stack now support NCQ (tagged queueing) for increased performance on modern SATA drives. It also supports port multipliers. ATA drives are accessed via 'ada' device nodes. ATAPI drives are accessed via 'cd' device nodes. They can all be enumerated and manipulated via camcontrol, just like SCSI drives. SCSI commands are not translated to their ATA equivalents; ATA native commands are used throughout the entire stack, including camcontrol. See the camcontrol manpage for further details. Testing this code may require that you update your fstab, and possibly modify your BIOS to enable AHCI functionality, if available. This code is very experimental at the moment. The userland ABI/API has changed, so applications will need to be recompiled. It may change further in the near future. The 'ada' device name may also change as more infrastructure is completed in this project. The goal is to eventually put all CAM busses and devices until newbus, allowing for interesting topology and management options. Few functional changes will be seen with existing SCSI/SAS/FC drivers, though the userland ABI has still changed. In the future, transports specific modules for SAS and FC may appear in order to better support the topologies and capabilities of these technologies. The modularization of CAM and the addition of the ATA/SATA modules is meant to break CAM out of the mold of being specific to SCSI, letting it grow to be a framework for arbitrary transports and protocols. It also allows drivers to be written to support discrete hardware without jeopardizing the stability of non-related hardware. While only an AHCI driver is provided now, a Silicon Image driver is also in the works. Drivers for ICH1-4, ICH5-6, PIIX, classic IDE, and any other hardware is possible and encouraged. Help with new transports is also encouraged. Submitted by: scottl, mav Approved by: re
OpenPOWER on IntegriCloud