All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Munch <lars@segv.dk>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Sandisk mDoC H3 support
Date: Fri, 30 May 2008 19:39:28 +0200	[thread overview]
Message-ID: <20080530173928.GA9151@firewall> (raw)
In-Reply-To: <423b02220805070646s1c83b085i2911aa4f8b94abaf@mail.gmail.com>

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

      parent reply	other threads:[~2008-05-30 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 13:46 [U-Boot-Users] Sandisk mDoC H3 support Micha Kalfon
2008-05-08 15:00 ` Jean-Christophe PLAGNIOL-VILLARD
2008-05-30 17:39 ` Lars Munch [this message]

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=20080530173928.GA9151@firewall \
    --to=lars@segv.dk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.