From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.lixom.net (lixom.net [66.141.50.11]) by ozlabs.org (Postfix) with ESMTP id A8DD8DDE2E for ; Thu, 7 Jun 2007 09:48:12 +1000 (EST) Date: Wed, 6 Jun 2007 18:54:40 -0500 To: Timur Tabi Subject: Re: MPC8349ea Random Device Generator driver Message-ID: <20070606235440.GA28400@lixom.net> References: <46672DB4.80504@freescale.com> <20070606220913.GA27820@lixom.net> <46673009.6000109@freescale.com> <20070606222456.GA28225@lixom.net> <466735F3.7040504@freescale.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <466735F3.7040504@freescale.com> From: olof@lixom.net (Olof Johansson) Cc: linuxppc-dev@ozlabs.org, sl@powerlinux.fr, Philippe Lachenal List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Jun 06, 2007 at 05:32:19PM -0500, Timur Tabi wrote: > Olof Johansson wrote: > > > - you can never assign a __le16 type to any other integer type or any > > other bitwise type. You'd get a warnign about incompatible types. Makes > > sense, no? > > Then why do the in_be functions return an unsigned int instead of a __be type? Isn't that > effectively removing the endian-ness from the type? Because they read a big endian register and returns the contents in the native byte order for the machine. -Olof