This is the mail archive of the
ecos-devel@sources.redhat.com
mailing list for the eCos project.
Re: [ECOS] load data from floppy
- From: Jonathan Larmour <jifl at eCosCentric dot com>
- To: Gary Thomas <gary at mlbassoc dot com>
- Cc: Nick Garnett <nickg at ecoscentric dot com>,eCos development <ecos-devel at sources dot redhat dot com>
- Date: Wed, 30 Jul 2003 20:58:27 +0100
- Subject: Re: [ECOS] load data from floppy
- References: <87fzlkm263.fsf@dedasys.com> <m3d6govu7p.fsf@miso.calivar.com> <873chillr6.fsf@dedasys.com> <m3vfueve9h.fsf@miso.calivar.com> <87el0fdcdm.fsf@dedasys.com> <m3he5b4wod.fsf@miso.calivar.com> <87ispljwnh.fsf@dedasys.com> <m3vftkgv27.fsf@miso.calivar.com> <1059566838.10050.1699.camel@hermes> <m365lkgkky.fsf@miso.calivar.com> <1059576934.10050.1865.camel@hermes>
Gary Thomas wrote:
I think your idea of reasonable sized sectors as the basic granularity
is the right approach. (512 bytes is OK, but maybe this should be
configurable) We also need to think about all the rest of the "driver"
stuff like initialization, control, and maybe [shudder] a block cache.
Some FS implementations rely on it for sane performance (as in performance
isn't just slow but orders of magnitude slow because they rely on ability
to instantly read back what was written) so we'll have to support it. But
I'm sure it would be possible to have a "null" layer to make it optional.
And similarly there's write buffering.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine