Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763949AbXJEUHo (ORCPT ); Fri, 5 Oct 2007 16:07:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757959AbXJEUHi (ORCPT ); Fri, 5 Oct 2007 16:07:38 -0400 Received: from de01egw02.freescale.net ([192.88.165.103]:53142 "EHLO de01egw02.freescale.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751199AbXJEUHh (ORCPT ); Fri, 5 Oct 2007 16:07:37 -0400 Message-ID: <47069982.9030009@freescale.com> Date: Fri, 05 Oct 2007 15:07:30 -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: Jan Engelhardt , Linux Kernel Mailing List Subject: Re: __LITTLE_ENDIAN vs. __LITTLE_ENDIAN_BITFIELD References: <4706822D.4070509@freescale.com> <470691EB.7020209@freescale.com> <470694E0.7030408@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: 620 Lines: 17 Andreas Schwab wrote: > The bit mapping on your device is strictly internal to the device and > has nothing to do with bit order on the C level. Then I don't understand that point of defining __LITTLE_ENDIAN_BITFIELD. What does it mean for a C-level bitfield ordering to be little-endian if the processor is BIG_ENDIAN? -- 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/