lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 20 Apr 2017 16:28:09 -0500 From: "Steven J. Hill" <Steven.Hill@...ium.com> To: David Daney <ddaney@...iumnetworks.com>, Ulf Hansson <ulf.hansson@...aro.org>, Jan Glauber <jan.glauber@...iumnetworks.com> Cc: linux-mmc <linux-mmc@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: MMC block addressing mode. On 04/20/2017 04:24 PM, Steven J. Hill wrote: > On 04/20/2017 12:12 PM, David Daney wrote: >> >> Steven and Jan: Can we get around this requirement by: >> >> - Always set MIO_EMM_DMA[MULTI] = 1; This way by SECTOR mode may be unimportant. >> >> - Always set MIO_EMM_DMA[SECTOR] = SUITABLE_CONSTANT. >> > No, this does not work. The 1.88GB card plugged into my 78xx > board gives the output below. We cannot just blindly set the > MULTI bit for all cards. These results are identical for all > four combinations of SECTOR and MULTI values hardcoded. > ...for 3 of the 4 combinations. Obviously the correct one works.
Powered by blists - more mailing lists