From mboxrd@z Thu Jan  1 00:00:00 1970
From: DVM <karl.robinsod@gmail.com>
Date: Sat, 28 Mar 2009 05:52:51 -0700 (PDT)
Subject: [U-Boot] Problems with ext2ls & SD
In-Reply-To: <22728281.post@talk.nabble.com>
References: <22728281.post@talk.nabble.com>
Message-ID: <22756563.post@talk.nabble.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


Further debugging reveals UBoot uses a fixed length for inodes (128 bye). The
inodes on my 2GB SD card are 256 bytes There was a patch that fizzled out
back in January looking at this

http://www.nabble.com/-U-Boot----PATCH--Fix-ext2-non-working-td21742132.html#a21742132

The superblock contains the inode length in the function 

static int ext2fs_read_inode()
...

	inodes_per_block = EXT2_BLOCK_SIZE (data) /
__le32_to_cpu(sblock->inode_size); 
...

	status = ext2fs_devread (((__le32_to_cpu (blkgrp.inode_table_id) + blkno)
<< LOG2_EXT2_BLOCK_SIZE (data)),
				 			 __le32_to_cpu(sblock->inode_size) * blkoff,
							 sizeof (struct ext2_inode),  /*HACK till I fix up struct size*/ 
							 (char *) inode); 


This seems to improve matters for me BUT I dont have any other hardware to
test on and I am no ext2fs guru. Does anyone else have any ideas?
-- 
View this message in context: http://www.nabble.com/Problems-with-ext2ls---SD-tp22728281p22756563.html
Sent from the Uboot - Users mailing list archive at Nabble.com.