From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?ISO-8859-1?Q?Andreas_Bie=DFmann?= <andreas.devel@googlemail.com>
Date: Sun, 21 Jul 2013 10:24:19 +0200
Subject: [U-Boot] [U-Boot,
 RFC] ext4fs: le32_to_cpu() used on a 16-bit field
In-Reply-To: <CAPnjgZ2FA00KOxhJOau_dooE_X5Ddhx6-fGwyOz+skcurGo4aw@mail.gmail.com>
References: <loom.20130716T085434-836@post.gmane.org>
	<20130719090305.16c47d8e@amdc308.digital.local>
	<CAPnjgZ2FA00KOxhJOau_dooE_X5Ddhx6-fGwyOz+skcurGo4aw@mail.gmail.com>
Message-ID: <51EB9AB3.8090407@googlemail.com>
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 all,

On 21.07.2013 06:32, Simon Glass wrote:
> +Tom
>
> On Fri, Jul 19, 2013 at 1:03 AM, Lukasz Majewski <l.majewski@samsung.com>wrote:
>
>> On Tue, 16 Jul 2013 08:14:35 +0000 (UTC) Rommel Custodio
>> sessyargc+uboot at gmail.com wrote,
>>
>> Hi Rommel,
>>
>>> Hi All,
>>>
>>> U-Boot 2013.07-rc3 [ELDK 5.2.1 / ELDK 5.3]
>>>
>>> Now I've started to use the new ext4 code. I need the "ext4write"
>>> command. Though there seems to be several problems with the ext2/ext4
>>> code.
>>>
>>> I am testing on an ml507 (PPC440, Big Endian).
>>> There are some cases where the a field is 16-bit but le32_to_cpu() is
>>> used. Some checks (ie eh_magic) fails to match even if I use a
>>> correctly ext4 formatted MMC/SD card.
>>>
>>> Does these seem right? Or am I mistaken?
>>
>> What kind of mailer program have you used to sent this e-mail?
>> I receive following errors:
>>
>> fatal: corrupt patch at line 111
>>
>> I cannot apply this patch with either git am -3 or git apply.
>>
>> Were you using git send-email?
>>
>
> It seems like we should try to fix this before the release?

+1

I can confirm that reading ext4 extended header on BE machine (avr32) is 
broken. I'm currently on it to get it working by using Rommel's patch.

Regards

Andreas Bie?mann