From: DVM <karl.robinsod@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problems with ext2ls & SD
Date: Sat, 28 Mar 2009 05:52:51 -0700 (PDT) [thread overview]
Message-ID: <22756563.post@talk.nabble.com> (raw)
In-Reply-To: <22728281.post@talk.nabble.com>
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.
next prev parent reply other threads:[~2009-03-28 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 18:52 [U-Boot] Problems with ext2ls & SD DVM
2009-03-28 12:52 ` DVM [this message]
2009-03-28 19:06 ` Wolfgang Denk
[not found] ` <669754ad0903281214x77796b95x76062f1c428ecda8@mail.gmail.com>
2009-04-25 19:24 ` Wolfgang Denk
2009-03-31 20:49 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22756563.post@talk.nabble.com \
--to=karl.robinsod@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox