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] [day] [month] [year] [list]
Message-Id: <20201002071542.26477-1-miquel.raynal@bootlin.com>
Date:   Fri,  2 Oct 2020 09:15:42 +0200
From:   Miquel Raynal <miquel.raynal@...tlin.com>
To:     Serge Semin <Sergey.Semin@...kalelectronics.ru>,
        Miquel Raynal <miquel.raynal@...tlin.com>,
        Richard Weinberger <richard@....at>,
        Vignesh Raghavendra <vigneshr@...com>
Cc:     linux-kernel@...r.kernel.org, linux-mips@...r.kernel.org,
        Serge Semin <fancer.lancer@...il.com>,
        Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
        linux-mtd@...ts.infradead.org,
        Pavel Parkhomenko <Pavel.Parkhomenko@...kalelectronics.ru>,
        Lee Jones <lee.jones@...aro.org>
Subject: Re: [PATCH v3] mtd: physmap: Add Baikal-T1 physically mapped ROM support

On Sun, 2020-09-20 at 11:14:44 UTC, Serge Semin wrote:
> Baikal-T1 Boot Controller provides an access to a RO storages, which are
> physically mapped into the SoC MMIO space. In particularly there are
> Internal ROM embedded into the SoC with a pre-installed firmware,
> externally attached SPI flash (also accessed in the read-only mode) and a
> memory region, which mirrors one of them in accordance with the currently
> enabled system boot mode (also called Boot ROM).
> 
> This commit adds the Internal ROM support to the physmap driver of the MTD
> kernel subsystem. The driver will create the Internal ROM MTD as long as
> it is defined in the system dts file. The physically mapped SPI flash
> region will be used to implement the SPI-mem interface. The mirroring
> memory region won't be accessible directly since it's redundant due to
> both bootable regions being exposed anyway.
> 
> Note we had to create a dedicated code for the ROMs since read from the
> corresponding memory regions must be done via the dword-aligned addresses.
> 
> Signed-off-by: Serge Semin <Sergey.Semin@...kalelectronics.ru>
> Cc: Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>
> Cc: Pavel Parkhomenko <Pavel.Parkhomenko@...kalelectronics.ru>
> Cc: Lee Jones <lee.jones@...aro.org>
> Cc: linux-mips@...r.kernel.org

Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git mtd/next, thanks.

Miquel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ