linux-kernel - Re: MMC block addressing mode.

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAPDyKFqfEQ6POgoSFL=t0nP62CB13DNL0m8m-Vzqaw0GMAV3qg@mail.gmail.com>
Date:   Thu, 20 Apr 2017 16:18:30 +0200
From:   Ulf Hansson <ulf.hansson@...aro.org>
To:     "Steven J. Hill" <Steven.Hill@...ium.com>
Cc:     linux-mmc <linux-mmc@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        David Daney <david.daney@...ium.com>,
        Jan Glauber <jan.glauber@...iumnetworks.com>
Subject: Re: MMC block addressing mode.

On 13 April 2017 at 21:49, Steven J. Hill <Steven.Hill@...ium.com> wrote:
> Uffe,
>
> The Cavium hardware requires knowledge of the card addressing mode.
> We need to either restore mmc_card_blockaddr(), or create another
> way to generate the same information. You previously suggested use
> of the 'blksz' value, however, it has the same value regardless of
> the card capacity. What would you suggest? Cheers.

Right. Can you explain what the Cavium hardware need it for?

Kind regards
Uffe