From: Tom Rini Date: Wed, 12 Mar 2014 12:08:23 -0400 Subject: [U-Boot] [PATCH] Add support for offset of a filesystem within a block-device In-Reply-To: <1394112635-21016-1-git-send-email-oe5hpm@oevsv.at> References: <1394112635-21016-1-git-send-email-oe5hpm@oevsv.at> Message-ID: <20140312160823.GS16805@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Thu, Mar 06, 2014 at 02:30:35PM +0100, Hannes Petermaier wrote: > For clear separation of user's (OS) filesystem to U-Boot and other's > stuff it is now possible to give the filesystem a specific offset and a > specific size. > For full consistency OS storage driver also has to support this and > has to use same offset and size. > > Following new parameters has been added to the block_dev_desc_t > structure: > - lba_offset : offset in blocks from which fs is reading/writing > - lba_fs : size in blocks of fs > > This two parameters are filled from the underlaying device-driver. > As default they are initialized for giving whole size of block-device > to the filesystem. > > In case of mmc-driver a function for modifiying drive geometry is > called 'board_mmc_geometry', this function is implemented as > '__weak', so it can be replaced by a board-specific function, which > can setup suitable offset and size for the filesystem. > This function is responsible for giving reasonable values, e.g. > lba_offset+lba_fs must not exceed available blocks of the device. > > Only MMC Driver and FATFS are modified to support this. > > Signed-off-by: Hannes Petermaier Sorry if I'm being dense here, but what is the usecase exactly? When we don't have a partition table of some sort? -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: