From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Hawkins <dwh@ovro.caltech.edu>
Date: Fri, 02 May 2008 14:48:27 -0700
Subject: [U-Boot-Users] Configuring U-Boot for MPC8349E in little endian
 mode
In-Reply-To: <481B79DE.8030905@freescale.com>
References: <47230CE166B64744B0120173E4C2161E04D531CF@BLR-EC-MBX01.wipro.com>	<47230CE166B64744B0120173E4C2161E04D5352E@BLR-EC-MBX01.wipro.com>	<481B265B.8060601@freescale.com>
	<481B46D5.6050605@ovro.caltech.edu>
	<481B6FE4.3090904@freescale.com>
	<481B7832.5020203@ovro.caltech.edu>
	<481B79DE.8030905@freescale.com>
Message-ID: <481B8C2B.90605@ovro.caltech.edu>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Timur,

>> In either case, you would use the byte-conversion routines to
>> serialize the descriptor entries in memory, or in the source buffer,
>> into the correct endianness before performing enabling the DMA.
> 
> Very true.  However, this means that if the original data is in
> the wrong endian, you have to have a middle layer that modifies
> the data when copying from the source buffer to the DMA buffer. 
> This adds overhead.

This would be the key question for Vivek then.

Does his highest volume data set have any endianness issues
that need to be resolved?

>> If Vivek's application correctly serializes any endian-specific
>> data before using the MPC8349EA DMA controller, then he should
>> have no issues.
> 
> Yes, but it may take him weeks to find all the places in the where the
> endianness matters.

Indeed.

Conversely, it may take months to get a little-endian PowerPC
port working!

:)

Cheers,
Dave