From: David Wagner <david.wagner@free-electrons.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org, kmpark@infradead.org
Subject: Re: impact of 2X_PROGRAM on read operations
Date: Thu, 09 Jun 2011 14:44:46 +0200 [thread overview]
Message-ID: <4DF0C03E.90909@free-electrons.com> (raw)
In-Reply-To: <1307370761.3112.76.camel@localhost>
On 06/06/2011 04:32 PM, Artem Bityutskiy wrote:
> On Mon, 2011-06-06 at 14:12 +0200, David Wagner wrote:
>> Is there a way to safely read without 2X_PROGRAM enabled once it has
>> been flashed with a 2X_PROGRAM-enabled flasher (e.g. patched u-boot).
>
> Not sure about u-boot, but AFAIK 2x is a completely separate mode which
> gives you I/O speed-up but makes things incompatible with "normal" mode.
> E.g., you can mount JFFS2 only in one of the modes.
>
Ok, so I guess it doesn't make sense trying to address the issue of
incompatibilities.
I may have to check once again, but I'm pretty sure, however, that I
managed to flash a UBI image with a 2X_PROGRAM-enabled u-boot and read
it with a regular kernel. The u-boot code for 2X_PROGRAM handling seems
to basically be a copy-paste from the kernel.
If the diagram in my first mail is correct, that could not be possible.
Kyungmin, do you know what's wrong in my reasoning ?
Regards,
David Wagner.
--
David Wagner, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-06-09 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 12:12 impact of 2X_PROGRAM on read operations David Wagner
2011-06-06 14:32 ` Artem Bityutskiy
2011-06-09 12:44 ` David Wagner [this message]
2011-06-09 13:01 ` Kyungmin Park
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=4DF0C03E.90909@free-electrons.com \
--to=david.wagner@free-electrons.com \
--cc=dedekind1@gmail.com \
--cc=kmpark@infradead.org \
--cc=linux-mtd@lists.infradead.org \
/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.