| 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
| ||
|
Message-ID: <20071009174623.GC4003@csclub.uwaterloo.ca> Date: Tue, 9 Oct 2007 13:46:23 -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 Fri, Oct 05, 2007 at 04:10:26PM -0500, Timur Tabi wrote: > Why not? I honestly don't know what x86 does, but I would think that if I > write a 32-bit value to a memory location, that when I examine that memory > location, all 32 bits will be in order. > > You're talking about byte endian. I'm talking about bit endian -- the > order of bits within a byte. Software cannot know what the bit endian is, > but external devices that have memory-mapped registers can know. The guy wiring up the hardware should connect the wires correctly. > The CPU shift operation, yes. I'm talking about shift operations on > external memory-mapped devices. Doesn't the bus usually have some definition of bit order which the device would have to adhere to? After all there must be address lines somewhere. Does this perhaps offer anything useful? http://www.linuxjournal.com/article/6788 -- 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/
Powered by blists - more mailing lists