linux-kernel - Re: [PATCH] ARM: mach-qcom: fix support for ipq806x

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]

Date:   Fri, 21 Oct 2022 23:44:56 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Christian Marangi <ansuelsmth@...il.com>,
        Geert Uytterhoeven <geert+renesas@...der.be>
Cc:     Russell King <linux@...linux.org.uk>,
        Andy Gross <agross@...nel.org>,
        Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio <konrad.dybcio@...ainline.org>,
        Arnd Bergmann <arnd@...db.de>,
        Ard Biesheuvel <ardb@...nel.org>,
        "Russell King (Oracle)" <rmk+kernel@...linux.org.uk>,
        Nick Hawkins <nick.hawkins@....com>,
        John Crispin <john@...ozen.org>,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH] ARM: mach-qcom: fix support for ipq806x

On Fri, Oct 21, 2022 at 8:10 PM Christian Marangi <ansuelsmth@...il.com> wrote:

> Add a specific config flag for Qcom IPQ806x as this SoC can't use
> AUTO_ZRELADDR and require the PHYS_OFFSET set to 0x42000000.
>
> This is needed as some legacy board (or some wrongly configured
> bootloader) pass the wrong memory map and doesn't exclude the first
> ~20MB of RAM reserved for the hardware network accellerators.
>
> With this change we can correctly support each board and prevent any
> kind of misconfiguration done by the OEM.
>
> Signed-off-by: Christian Marangi <ansuelsmth@...il.com>

I had exactly this problem with the APQ8060 as well, then my problem
went away. I was under the impression that this was solved.

Is it not possible to use Geert's linux,usable-memory-range in
the chosen node to make the kernel stay off the memory?
(See examples by grep usable-memory in the kernel.)

Yours,
Linus Walleij