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: <1a297b360707101502t2670f0d7g5197b9c32ecb967c@mail.gmail.com>
Date:	Wed, 11 Jul 2007 02:02:23 +0400
From:	"Manu Abraham" <abraham.manu@...il.com>
To:	"vraghavan3@...l.gatech.edu" <vraghavan3@...l.gatech.edu>
Cc:	"Nobin Mathew" <nobin.mathew@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Reading a physical memory location

On 7/10/07, vraghavan3@...l.gatech.edu <vraghavan3@...l.gatech.edu> wrote:
>
> Thanks for the quick reply. But I was wondering as to why I would have to map
> the physical address to the virtual address when I know that the string is
> permanently in the physical memory because its loaded into flash. Is there a way
> to directly read from the physical memory location? Also, do the functions
> ioremap() and readl(va) work when called from within a kernel module?
>

Of course, if you look at almost any of the memory mapped device
drivers, you will find that ioremap/readl/writel is the backbone of
your infrastructure.


Manu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ