From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Hans Zhang <zhanghonghui@innofidei.com>
Cc: Richard Genoud <richard.genoud@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-mtd <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
zhouguangming@innofidei.com
Subject: Re: [PATCH] Make the mtdblock read/write skip the bad nand sector
Date: Fri, 22 Nov 2013 08:45:10 -0300 [thread overview]
Message-ID: <20131122114509.GB2414@localhost> (raw)
In-Reply-To: <528EBD0B.5010006@innofidei.com>
On Fri, Nov 22, 2013 at 10:10:19AM +0800, Hans Zhang wrote:
> On 2013/11/22 9:52, Ezequiel Garcia wrote:
> > On Fri, Nov 22, 2013 at 09:22:43AM +0800, Hans Zhang wrote:
> >> On 2013/11/21 18:59, Richard Genoud wrote:
> >>
> >> Here's my scenario, I want to write nand through mtdblock by dd command
> > You could get some better support by explaining why do you want to write
> > to a NAND through mtdblock. It sounds a bit ackward to me, but I'm sure
> > you have a good reason for it!
> >
> > Let's hear it :-)
>
> Thanks for your reply.
> This is for my embed system upgrade, I reserved one nand partition for filesystem
> environment which will load to DDR while uboot booting.
> This filesystem.uboot file should be able to read both by uboot and kernel, and
> maybe written by uboot and kernel. There will be no filesystems upon the nand in
> case the loader may not support some filesystem types while uboot booting.
>
> Seems that the trimmed environment of OS has get rid of the mtd-tools, So the dd
> command was the most convenience tools to use by hand.
>
I still don't understand why are you using mtdblock. Why can't you write
through the char device?
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-22 11:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 8:54 [PATCH] Make the mtdblock read/write skip the bad nand sector Hans Zhang
2013-11-21 10:59 ` Richard Genoud
2013-11-22 1:22 ` Hans Zhang
2013-11-22 1:52 ` Ezequiel Garcia
2013-11-22 2:10 ` Hans Zhang
2013-11-22 8:14 ` Richard Weinberger
2013-11-22 11:45 ` Ezequiel Garcia [this message]
2013-11-25 1:29 ` Hans Zhang
2013-11-25 10:11 ` Ezequiel Garcia
2013-11-25 10:23 ` Richard Genoud
2013-11-25 11:30 ` Hans Zhang
2013-11-25 11:52 ` Ezequiel Garcia
2013-11-25 12:16 ` David Woodhouse
2013-11-25 12:30 ` Ezequiel Garcia
2013-11-25 15:12 ` Peter Korsgaard
2013-11-25 15:46 ` David Woodhouse
2013-11-29 13:26 ` Pavel Machek
2013-12-10 7:43 ` Brian Norris
-- strict thread matches above, loose matches on Subject: below --
2013-11-21 8:39 Hans Zhang
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=20131122114509.GB2414@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.genoud@gmail.com \
--cc=zhanghonghui@innofidei.com \
--cc=zhouguangming@innofidei.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