public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Romain Izard <romain.izard.pro@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] am335x_evm: Update, document Falcon Mode support
Date: Thu, 4 Jul 2013 07:39:48 +0000 (UTC)	[thread overview]
Message-ID: <kr38s4$ccm$1@ger.gmane.org> (raw)
In-Reply-To: 20130703223028.GE16630@bill-the-cat

Tom> +A further word of warning about using eMMC and partition tables.  When
Tom> +working with SD cards we can get away with erasing small areas at a time,
Tom> +however on eMMC we must keep erases aligned to eraseblocks and thus the
Tom> +first erase we issue will erase the partition table.

Peter> Really? I thought eMMC behaved just like SD cards?

Tom> Yes, really.  We know what the erase block size is, and round our
Tom> commands, probably because we really have to.  SD cards take care of
Tom> things for us, for better or worse.

But why do we bother with erasing the eMMC in the first place? The erase
commands are wholly optional, and only make sense as a TRIM mechanism,
which is not our case as we will fill the memory as soon as it has been
erased.

There is no problem in writing directly in the memory, even if it has
not been erased previously. Or is it a measure to detect interrupted
writes ?

Best regards,
-- 
Romain Izard

  reply	other threads:[~2013-07-04  7:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 20:09 [U-Boot] [PATCH 0/2] Update Falcon Mode docs Tom Rini
2013-07-03 20:09 ` [U-Boot] [PATCH 1/2] README.falcon: Note how we determine if we can boot the OS or not Tom Rini
2013-07-03 21:19   ` Peter Korsgaard
2013-07-03 20:09 ` [U-Boot] [PATCH 2/2] am335x_evm: Update, document Falcon Mode support Tom Rini
2013-07-03 21:28   ` Peter Korsgaard
2013-07-03 22:30     ` Tom Rini
2013-07-04  7:39       ` Romain Izard [this message]
2013-07-05 12:51         ` 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='kr38s4$ccm$1@ger.gmane.org' \
    --to=romain.izard.pro@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