Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1 |
|
#
7ba10b88 |
| 21-May-2017 |
Imre Vadász <imre@vdsz.com> |
Port initial UHS-1 support from FreeBSD (Only DDR52 for eMMC so far).
* Fix typo from FreeBSD commit: SDHCI_CTRL2_DRIVER_TYPE_A/_C_D vs. SDHCI_CAN_DRIVE_TYPE_A/_C/_D. And these Driver Type capab
Port initial UHS-1 support from FreeBSD (Only DDR52 for eMMC so far).
* Fix typo from FreeBSD commit: SDHCI_CTRL2_DRIVER_TYPE_A/_C_D vs. SDHCI_CAN_DRIVE_TYPE_A/_C/_D. And these Driver Type capability bits are in the CAPABILITIES2 register.
* Hide 1.8V VDD capability when the slot is detected as a removable card slot, as the spec explicitly states that the 1.8V VDD is only meant to be for embedded slots.
* This gives ca. 75 MiB/s read speed with the eMMC in my HP X2 210 detachable with the Intel Cherry Trail eMMC controller, in DDR52 mode.
Taken-From: FreeBSD (svn r315598)
show more ...
|
#
85ccd313 |
| 21-May-2017 |
Imre Vadász <imre@vdsz.com> |
A step to correctly handling command timeouts in the MMC layer.
- Now that properly issuing CMD6 is crucial (so data isn't written to the wrong partition for example), make a step into the
A step to correctly handling command timeouts in the MMC layer.
- Now that properly issuing CMD6 is crucial (so data isn't written to the wrong partition for example), make a step into the direction of correctly handling the timeout for these commands in the MMC layer. Also, do a SEND_STATUS when CMD6 is invoked with an R1B response as recommended by relevant specifications. However, quite some work is left to be done in this regard; all other R1B-type commands done by the MMC layer also should be followed by a SEND_STATUS (CMD13), the erase timeout calculations/handling as documented in specifications are entirely ignored so far, the MMC layer doesn't provide timeouts applicable up to the bridge drivers and at least sdhci(4) currently is hardcoding 1 s as timeout for all command types unconditionally. Let alone already available return codes often not being checked in the MMC layer ...
- For devices following the eMMC specification v4.41 or later, year 0 is 2013 rather than 1997; so correct this for assembling the device ID string properly.
* This omits all the parts specific to eMMC "partitions" from the FreeBSD change.
* Add the Intel sdhci controller ids to sdhci_pci.c to set the SDHCI_QUIRK_WAIT_WHILE_BUSY quirk there. This also disables DMA on apollo lake sdhci, while there and whitelists ADMA2 on Bay Trail and Braswell sdhci controllers.
Taken-From: FreeBSD (svn r315430)
show more ...
|
#
4d3ae590 |
| 21-May-2017 |
Imre Vadász <imre@vdsz.com> |
More style, comments, includes and unused params fixes for sdhci and mmc.
Taken-From: FreeBSD (svn r314811)
|
#
70a02aad |
| 20-May-2017 |
Imre Vadász <imre@vdsz.com> |
Style fixes for sdhci(4) and mmc(4) in comments, includes, unused params.
Taken-From: FreeBSD (svn r315466)
|
Revision tags: v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0 |
|
#
86d7f5d3 |
| 26-Nov-2011 |
John Marino <draco@marino.st> |
Initial import of binutils 2.22 on the new vendor branch
Future versions of binutils will also reside on this branch rather than continuing to create new binutils branches for each new version.
|
Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1 |
|
#
d6644679 |
| 16-Apr-2010 |
Sascha Wildner <saw@online.de> |
Bring in FreeBSD's MMC (MultiMediaCard) stack.
mmc(4) - The MMC bus sdhci(4) - Host controller driver mmcsd(4) - Memory card disk device driver
SD, SDHC and MMC cards should be supported (tested
Bring in FreeBSD's MMC (MultiMediaCard) stack.
mmc(4) - The MMC bus sdhci(4) - Host controller driver mmcsd(4) - Memory card disk device driver
SD, SDHC and MMC cards should be supported (tested with an SDHC card).
show more ...
|