public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Egbert Eich <egbert.eich@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/4] Add Support for Storage Devices with Blocksizes != 512
Date: Wed, 10 Apr 2013 09:11:53 +0200	[thread overview]
Message-ID: <1365577917-32563-1-git-send-email-egbert.eich@gmail.com> (raw)

From: Egbert Eich <eich@suse.de>

Storage devices with more than 2TB generally use blocksizes of 4096 bytes,
So far u-boot was unable to boot from those devices as block sizes were 
hard coded to 512 bytes.

This patchset adds support for blocksizes != 512 byte to:
 - the ISO partition table.
 - the ext4. 

To be useful, one most likely needs:
   "disk/gpt: Fix GPT Partition handling for Blocksize != 512"
which was posted earlier.

With those fixes in place u-boot loads the kernel and initrd flawlessly       
from an ext2 fs on my 3TB USB hard drive which is set up with a GPT.              

I've also reviewed the FAT code, it seems to be ok already (except for a      
bug that I came across).                                                      
                                                                              
I may be persuaded to take a shot at other fs which are supported by          
a vanilla Linux kernel and I thus can test.                                   

Egbert Eich (4):
  disk/iso: Add Support for block sizes > 512 byte to ISO partition
    support
  fs/fat: Don't multiply fatsize  with sector size
  part/dev_desc: Add log2 of blocksize to block_dev_desc data struct
  fs/ext4: Support device block sizes != 512 bytes

 common/cmd_ide.c          |  5 ++++
 common/cmd_sata.c         |  1 +
 common/cmd_scsi.c         |  4 +++
 common/usb_storage.c      |  1 +
 disk/part_iso.c           |  3 +++
 drivers/block/ata_piix.c  |  1 +
 drivers/block/pata_bfin.c |  2 ++
 drivers/block/systemace.c |  1 +
 drivers/mmc/mmc.c         |  1 +
 fs/ext4/dev.c             | 62 ++++++++++++++++++++++++++++++-----------------
 fs/ext4/ext4_common.c     | 42 +++++++++++++++++---------------
 fs/ext4/ext4_common.h     |  2 +-
 fs/ext4/ext4_journal.c    |  6 ++---
 fs/ext4/ext4_write.c      | 32 ++++++++++++------------
 fs/ext4/ext4fs.c          | 14 ++++++-----
 fs/fat/fat_write.c        |  1 -
 include/common.h          |  2 +-
 include/ext4fs.h          |  1 +
 include/ext_common.h      | 12 +++------
 include/part.h            |  5 ++++
 20 files changed, 120 insertions(+), 78 deletions(-)

-- 
1.8.1.4

             reply	other threads:[~2013-04-10  7:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  7:11 Egbert Eich [this message]
2013-04-10  7:11 ` [U-Boot] [PATCH v2 1/4] disk/iso: Add Support for block sizes > 512 byte to ISO partition support Egbert Eich
2013-05-02 16:07   ` [U-Boot] [U-Boot, v2, " Tom Rini
2013-04-10  7:11 ` [U-Boot] [PATCH v2 2/4] fs/fat: Don't multiply fatsize with sector size Egbert Eich
2013-05-02 16:07   ` [U-Boot] [U-Boot, v2, " Tom Rini
2013-04-10  7:11 ` [U-Boot] [PATCH v2 3/4] part/dev_desc: Add log2 of blocksize to block_dev_desc data struct Egbert Eich
2013-05-02 16:08   ` [U-Boot] [U-Boot, v2, " Tom Rini
2013-04-10  7:11 ` [U-Boot] [PATCH v2 4/4] fs/ext4: Support device block sizes != 512 bytes Egbert Eich

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=1365577917-32563-1-git-send-email-egbert.eich@gmail.com \
    --to=egbert.eich@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