public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.biessmann@corscience.de>
To: Tony Lindgren <tony@atomide.com>, Peter Meerwald <pmeerw@pmeerw.net>
Cc: Enric Balletbo Serra <eballetbo@gmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	linux-mtd@lists.infradead.org
Subject: Re: OMAP3 NAND ECC selection
Date: Fri, 06 Dec 2013 18:35:02 +0100	[thread overview]
Message-ID: <52A20AC6.9060200@corscience.de> (raw)
In-Reply-To: <20131205171326.GA26766@atomide.com>

[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]

On 12/05/2013 06:13 PM, Tony Lindgren wrote:
> * Peter Meerwald <pmeerw@pmeerw.net> [131205 08:13]:
>>>>> I'd like to be able to update MLO and u-boot from within a booted Linux
>>>>> system on the device (I have to resort to u-boot for that where I can
>>>>> control the ECC scheme used)
>>
>>>> Meanwhile, to do this we use a small userspace program created by
>>>> Javier Martinez in order to flash the MLO in our OMAP3 boards. See
>>>> http://git.isee.biz/?p=pub/scm/writeloader.git;a=summary
>>
>>> we used another aproach here. See
>>> http://article.gmane.org/gmane.linux.drivers.mtd/43804
>>
>> pretty much what I have been looking for, thanks!
> 
> Hmm well both methods should work, but is there anything stopping us
> merging the module param patch to the mainline tree?

We could do so, should I provide a proper patch?
On the other hand I think this approach is a workaround to circumvent
the MTD architecture flaws mostly needed in embedded systems where we
control the whole environment. Should we really introduce this switch to
the whole bunch of users working with mainline distros on their beagle
style HW?
I think the user space tool approach is more useful there.

regards

Andreas Bießmann


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  parent reply	other threads:[~2013-12-06 17:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05  9:13 OMAP3 NAND ECC selection Peter Meerwald
2013-12-05  9:47 ` Enric Balletbo Serra
2013-12-05  9:59   ` Andreas Bießmann
2013-12-05 16:12     ` Peter Meerwald
2013-12-05 17:13       ` Tony Lindgren
2013-12-05 17:39         ` Javier Martinez Canillas
2013-12-05 18:26           ` Ezequiel Garcia
2013-12-05 18:58             ` Javier Martinez Canillas
2013-12-05 19:02             ` Gupta, Pekon
2013-12-05 19:06               ` Thomas Petazzoni
2013-12-05 19:24                 ` Brian Norris
2013-12-05 19:32                   ` Thomas Petazzoni
2013-12-05 19:38                     ` Tony Lindgren
2013-12-08 20:59                       ` Mike Dunn
2013-12-09  4:33                     ` Gupta, Pekon
2013-12-09 11:06                       ` Matthieu CASTET
2013-12-09 11:50                         ` Gupta, Pekon
2013-12-05 19:13             ` Brian Norris
2013-12-06 17:35         ` Andreas Bießmann [this message]
2013-12-06 14:54   ` Peter Meerwald

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=52A20AC6.9060200@corscience.de \
    --to=andreas.biessmann@corscience.de \
    --cc=eballetbo@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    --cc=tony@atomide.com \
    /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