public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V5 1/2] ext4fs ls load support
Date: Thu, 09 Aug 2012 18:52:58 -0500	[thread overview]
Message-ID: <50244D5A.3080304@gmail.com> (raw)
In-Reply-To: <20120809215028.B6F0E20401A@gemini.denx.de>

On 08/09/2012 04:50 PM, Wolfgang Denk wrote:
> Dear Uma Shankar,
> 
> In message <1337961104-21198-1-git-send-email-uma.shankar@samsung.com> you wrote:
>> Signed-off-by: Uma Shankar <uma.shankar@samsung.com>
>> Signed-off-by: Manjunatha C Achar <a.manjunatha@samsung.com>
>> Signed-off-by: Iqbal Shareef <iqbal.ams@samsung.com>
>> Signed-off-by: Hakgoo Lee <goodguy.lee@samsung.com>
>> ---
>> Changes for v4:
>>         - Redesigned ext2, ext4 command interface
>>         - Removed ext2 folder from fs/
>>         - Memory Leak issue handled
>>
>> Changes for v3:
>>         - Copyright has been updated in respective files
>>         - ext4fs has been made independant of ext2fs.c
>>         - Fixed API namespace  
>>         - Removed endianness conversion API, used uboot defined API
>>           for the same
>>         - Fixed coding style issues
>>         - Moved README.ext4 file into doc folder
>>  
>> Changes for v2:
>>         - Code cleanup, changed comment style
>>         - camel case removed, resolved code alignment issues
>>         - memory allocation logic changed, removed busybox logic
>>         - Modified ext4 load to remove grub dependency (GPLv3)
>>         - Introduced new Config for ext4 write
>>  
>> Changes for v1:
>>         - Removed checkpatch warnings and errors
>>         - Moved common API's of ext2 and ext4 to one generic header file
>>
>> ---
>>  Makefile                   |    2 +-
>>  common/Makefile            |    6 +
>>  common/cmd_ext2.c          |  219 +----------
>>  common/cmd_ext4.c          |   96 +++++
>>  common/cmd_ext_common.c    |  259 +++++++++++++
>>  fs/Makefile                |    5 +-
>>  fs/ext2/dev.c              |  131 -------
>>  fs/ext2/ext2fs.c           |  897 --------------------------------------------
>>  fs/{ext2 => ext4}/Makefile |    8 +-
>>  fs/ext4/dev.c              |  145 +++++++
>>  fs/ext4/ext4_common.c      |  875 ++++++++++++++++++++++++++++++++++++++++++
>>  fs/ext4/ext4_common.h      |   63 +++
>>  fs/ext4/ext4fs.c           |  228 +++++++++++
>>  include/ext2fs.h           |   81 ----
>>  include/ext4fs.h           |  132 +++++++
>>  include/ext_common.h       |  197 ++++++++++
>>  16 files changed, 2028 insertions(+), 1316 deletions(-)
>>  create mode 100644 common/cmd_ext4.c
>>  create mode 100644 common/cmd_ext_common.c
>>  delete mode 100644 fs/ext2/dev.c
>>  delete mode 100644 fs/ext2/ext2fs.c
>>  rename fs/{ext2 => ext4}/Makefile (89%)
>>  create mode 100644 fs/ext4/dev.c
>>  create mode 100644 fs/ext4/ext4_common.c
>>  create mode 100644 fs/ext4/ext4_common.h
>>  create mode 100644 fs/ext4/ext4fs.c
>>  delete mode 100644 include/ext2fs.h
>>  create mode 100644 include/ext4fs.h
>>  create mode 100644 include/ext_common.h
> 
> As this is all untested code which replaces ext2 which is in active
> use by a large number of boards I decided to put this into a separate
> branch "ext4" for now so people can easiy test it.  If there are no
> problems, or the problems have been fixed in time, we can merge this
> branch around when -rc1 comes out.
> 

I reported already that the prior version that ext4 has issues with
sub-directories. I don't think that has been addressed in V5. Some
directories show up fine and some don't. So it's kind of random whether
u-boot can read a /boot directory. This was after full ubuntu installs.
I'd guess a simple test with a couple of files and directories will not
show the problem.

Rob

> Hope this is OK with you.
> 
> Best regards,
> 
> Wolfgang Denk
> 

  reply	other threads:[~2012-08-09 23:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 17:39 [U-Boot] [PATCH 1/2] ext4fs ls load support uma.shankar at samsung.com
2011-12-15 22:48 ` Graeme Russ
2011-12-16 16:30 ` Mike Frysinger
2011-12-28  2:22 ` [U-Boot] [PATCH V3 " uma.shankar at samsung.com
2012-01-05 15:25   ` Wolfgang Denk
2012-01-05 15:32   ` Wolfgang Denk
2012-01-08  4:26   ` Mike Frysinger
2012-01-09 17:54   ` [U-Boot] [PATCH V4 " uma.shankar at samsung.com
2012-03-22 15:49     ` Rob Herring
2012-03-27 15:10     ` Rob Herring
2012-05-25 15:51     ` [U-Boot] [PATCH V5 " Uma Shankar
2012-08-09 21:50       ` Wolfgang Denk
2012-08-09 23:52         ` Rob Herring [this message]
2012-08-10  0:07           ` Marek Vasut
2012-08-10  6:24           ` Wolfgang Denk
2012-08-13 11:52           ` Wolfgang Denk
2012-08-13 18:28             ` Rob Herring
2012-08-13 19:17               ` Wolfgang Denk
2012-08-13 20:30                 ` Rob Herring
2012-09-02 11:36                   ` Wolfgang Denk
2012-09-02 16:48                     ` Marek Vasut
2012-09-02 21:34                     ` Rob Herring
2012-09-12 22:49               ` Tom Rini
2012-09-12 22:57                 ` Rob Herring
2012-09-13  0:53                   ` Tom Rini
2012-09-13  9:20                     ` Marek Vasut
2012-09-13 14:29                       ` Tom Rini
2012-09-20 18:34                         ` Tom Rini

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=50244D5A.3080304@gmail.com \
    --to=robherring2@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