From: "Steven J. Hill" <sjhill@cotw.com>
To: "Woodhouse, David" <dwmw2@infradead.org>, MTD List <mtd@infradead.org>
Subject: Question on 'doc_read_ecc'...
Date: Wed, 27 Sep 2000 09:07:49 -0500 [thread overview]
Message-ID: <39D1FF35.68F6B84@cotw.com> (raw)
If I am understanding things correctly, in 'doc_read_ecc' we
prevent the caller from reading across a 512 byte boundary and
that they cannot read more than 512 bytes at a time. Is this
correct for DoC2xxx devices and should it be the case for NAND
devices as well? I believe that for NAND devices it makes sense
since VFS and filesystems on average assume a 512 byte sector
size. Just looking for agreement on my thought process.
-Steve
--
Steven J. Hill - Embedded SW Engineer
Public Key: 'finger sjhill@mail.cotw.com'
FPR1: E124 6E1C AF8E 7802 A815
FPR2: 7D72 829C 3386 4C4A E17D
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-09-27 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-27 14:07 Steven J. Hill [this message]
2000-09-27 14:10 ` Question on 'doc_read_ecc' David Woodhouse
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=39D1FF35.68F6B84@cotw.com \
--to=sjhill@cotw.com \
--cc=dwmw2@infradead.org \
--cc=mtd@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