linux-kernel - Re: __LITTLE_ENDIAN vs. __LITTLE_ENDIAN

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:	Tue, 9 Oct 2007 14:34:24 -0400
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Timur Tabi <timur@...escale.com>
Cc:	Anton Altaparmakov <aia21@....ac.uk>,
	Jan Engelhardt <jengelh@...putergmbh.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: __LITTLE_ENDIAN vs. __LITTLE_ENDIAN_BITFIELD

On Tue, Oct 09, 2007 at 12:56:37PM -0500, Timur Tabi wrote:
> I'm sure they're correct, my problem is that how can my driver know what 
> they are?

If they are correct, then you should only need to know about byte order
in my experience.

> I was hoping that there would be some compile-time constant I could check 
> that would give me this information.
> 
> Yeah, I read that article some time ago when trying to diagnose the problem 
> I was seeing.  It does explain the point I'm trying to make.  We have a 
> device that's used on two product lines: one ARM-based, and one PowerPC.  
> The ARM is little-endian, and the PowerPC is big-endian.  The device can 
> support little-endian or big-endian data, as long as the bit-order matches 
> the byte-order.
> 
> For now, I'm going to have to assume that they do match.

Well that is certainly the normal way it is done.  I think a few odd
machines had options for doing different bit orders, but the normal
setup is that it matches since that is the simplest layout when trying
to implement bit shifts in hardware.

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