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>] [day] [month] [year] [list]
Message-ID: <CAES_P+-khQGqec2_xqVEU4m0b9WscvLUinQmPXi6zX_P4mP+hw@mail.gmail.com>
Date:   Wed, 11 May 2022 16:00:14 -0700
From:   noman pouigt <variksla@...il.com>
To:     linux-kernel@...r.kernel.org,
        kernelnewbies <kernelnewbies@...nelnewbies.org>
Subject: Mapping ram memory using ioremap

We are using part of DRAM as shared memory
between DSP and SoC. However, DSP
can only access higher 1GB of DRAM.

In order to map the aforementioned memory
I tried using ioremap and it blurted out the
warning as mentioned in this article.
https://lwn.net/Articles/409700/

What is the alternative to using ioremap to
map specific RAM memory region for use
in the driver as shared memory?

I tried memremap + reserved memory as well
and it failed.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ