linux-kernel - Re: ioremap definition in generic io.h

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: <1285758446.12259.9.camel@needafix>
Date:	Wed, 29 Sep 2010 13:07:26 +0200
From:	Jonas Bonn <jonas@...thpole.se>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: ioremap definition in generic io.h

On Wed, 2010-09-29 at 12:53 +0200, Jiri Slaby wrote:
> On 09/29/2010 09:59 AM, Jonas Bonn wrote:
> > I'm wondering about the usefulness of the definition of ioremap and
> > __ioremap in asm-generic/io.h.  How is this intended to be used?  How
> > are the page tables for this mapping supposed to be constructed?
> 
> Which page tables? The functions there are for machines w/o MMU with 1:1
> phys:virt mapping.
> 

OK, thanks.  It's not clear from asm-generic/io.h that it's intended for
NOMMU systems only.  Aside from the ioremap definition, everything in
that file should be applicable generically... or am I missing something?

On another note, looking at the definitions of ioread32/iowrite32, they
imply a little-endian bus.  Some architectures (e.g. Microblaze) define
these to use host-native byte ordering instead.  Is there a _correct_
way these functions should be defined?

/Jonas

--
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/