From: Tim Hockin <thockin@sun.com>
To: linux-mtd@lists.infradead.org
Subject: writing to flash
Date: Thu, 19 Jul 2001 16:39:21 -0700 [thread overview]
Message-ID: <3B576FA9.C36441A@sun.com> (raw)
Is there a reason nothing uses copy_to() methods except map_ram?
It seems strange that for every byte I want to write to my flash chip, I
have to execute 3 one-byte writes, when I could use copy_to().
Is there any reason we don't?
--
Tim Hockin
Systems Software Engineer
Sun Microsystems, Cobalt Server Appliances
thockin@sun.com
next reply other threads:[~2001-07-19 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 23:39 Tim Hockin [this message]
2001-07-20 1:06 ` writing to flash Tim Hockin
-- strict thread matches above, loose matches on Subject: below --
2005-02-22 11:49 Writing " sunil m
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=3B576FA9.C36441A@sun.com \
--to=thockin@sun.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox