From: David Woodhouse <dwmw2@infradead.org>
To: "Steven J. Hill" <sjhill@cotw.com>
Cc: MTD List <mtd@infradead.org>
Subject: Re: Question on 'doc_read_ecc'...
Date: Wed, 27 Sep 2000 15:10:29 +0100 [thread overview]
Message-ID: <23804.970063829@passion.cygnus.co.uk> (raw)
In-Reply-To: <39D1FF35.68F6B84@cotw.com>
sjhill@cotw.com said:
> 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.
Scrap the limitation. It was OK when the only use of doc2000 was NFTL, but
now it's broken. doc2000.c ought to do the right thing.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
prev parent reply other threads:[~2000-09-27 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-27 14:07 Question on 'doc_read_ecc' Steven J. Hill
2000-09-27 14:10 ` David Woodhouse [this message]
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=23804.970063829@passion.cygnus.co.uk \
--to=dwmw2@infradead.org \
--cc=mtd@infradead.org \
--cc=sjhill@cotw.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