From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lars Munch Date: Fri, 30 May 2008 19:39:28 +0200 Subject: [U-Boot-Users] Sandisk mDoC H3 support In-Reply-To: <423b02220805070646s1c83b085i2911aa4f8b94abaf@mail.gmail.com> References: <423b02220805070646s1c83b085i2911aa4f8b94abaf@mail.gmail.com> Message-ID: <20080530173928.GA9151@firewall> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, May 07, 2008 at 04:46:04PM +0300, Micha Kalfon wrote: > Hello all, > > In the last few weeks I've been working on a u-boot driver for > Sandisk's (MSystems) mDoc H3 device - basically, it's a DiskOnChip > device which exposes a simple ATA interface to the software and works > differently from previous generation DoCs (see > http://www.linuxdevices.com/articles/AT2185129745.html for more). > > I implemented the following low-level features in u-boot which allow > using the DoC H3 as a boot device (currently all I need it for) : > > 1. Basic partitioning - allows statically allocating sectors for > numerous binary (raw) partitions. > 2. Writing IPL boot block - basically, the very initial 2KB of code > than run when the CPU boots. > 3. Reading and Writing of binary partitions - I place u-boot binary in > one partition to be loaded and run by the IPL and the linux kernel > uImage in another. > > Features are exposed to the user / bootscript as simple u-boot commands. > > > Does anyone see benefit from this to other u-boot users? If not, what > can be added / changed to make it so? Great! I for one would very much like to have support for this in u-boot. Regards Lars Munch