Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764660AbXJEVcq (ORCPT ); Fri, 5 Oct 2007 17:32:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1762412AbXJEVci (ORCPT ); Fri, 5 Oct 2007 17:32:38 -0400 Received: from de01egw01.freescale.net ([192.88.165.102]:53042 "EHLO de01egw01.freescale.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760900AbXJEVch (ORCPT ); Fri, 5 Oct 2007 17:32:37 -0400 Message-ID: <4706AD62.6030705@freescale.com> Date: Fri, 05 Oct 2007 16:32:18 -0500 From: Timur Tabi Organization: Freescale User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 MIME-Version: 1.0 To: Andreas Schwab CC: Anton Altaparmakov , Jan Engelhardt , Linux Kernel Mailing List Subject: Re: __LITTLE_ENDIAN vs. __LITTLE_ENDIAN_BITFIELD References: <4706822D.4070509@freescale.com> <470691EB.7020209@freescale.com> <4706A842.9030507@freescale.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 857 Lines: 23 Andreas Schwab wrote: > Timur Tabi writes: > >> The CPU shift operation, yes. I'm talking about shift operations on >> external memory-mapped devices. > > That is a property of how the device is wired to the bus. The cpu will > always put a value of 128 on the bus such that D7 = 1 and D0-D6 = 0. Yes, but is D7 on the left or on the right? Anyway, this is academic now. I now know that __LITTLE_ENDIAN_BITFIELD is not what I want, and that there's no macro that will tell how the lines from the CPU to external memory are mapped. -- Timur Tabi Linux Kernel Developer @ Freescale - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/