From: "hacklu.uboot" <hacklu.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] is any bug in cp?
Date: Mon, 18 Apr 2011 09:49:50 +0800 [thread overview]
Message-ID: <201104180949422307297@gmail.com> (raw)
In-Reply-To: 20110415102119.0200E1537B0@gemini.denx.de
thanks ,
I have understanded.
------------------
hacklu.uboot
2011-04-18
-------------------------------------------------------------
????????????Wolfgang Denk
???????????????2011-04-15 18:21:23
????????????hacklu.uboot
?????????u-boot
?????????Re:Re: Re: [U-Boot] is any bug in cp?
Dear "=?utf-8?B?aGFja2x1LnVib290?=",
In message <201104151715238470584@gmail.com> you wrote:
> em..
> how linux does that?
What exactly are you doing in Linux? Are we talking about user-space
access through a file sytem (and thus block devices) based on the MTD
layer? Or about raw access to the flash devices? Or about in-kernel
code directly accessing some CFI driver routines?
> does linux read the data to mem first before it write to the same bank of a nor flash?
For user space operations on file system level: yes.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
In any group of employed individuals the only naturally early riser
is _always_ the office manager, who will _always_ leave reproachful
little notes ... on the desks of their subordinates.
- Terry Pratchett, _Lords and Ladies_
next prev parent reply other threads:[~2011-04-18 1:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3.1302775202.27468.u-boot@lists.denx.de>
2011-04-15 6:01 ` [U-Boot] is any bug in cp? hacklu.uboot
2011-04-15 8:44 ` Wolfgang Denk
2011-04-15 9:15 ` hacklu.uboot
2011-04-15 10:21 ` Wolfgang Denk
2011-04-18 1:49 ` hacklu.uboot [this message]
2011-04-15 13:58 ` Charles Krinke
2011-04-18 1:47 ` hacklu.uboot
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=201104180949422307297@gmail.com \
--to=hacklu.uboot@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 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.