M-Systems Flash Disk compliance.

[Joel Sherrill]

Chris Caudle wrote:
> 
> >Hmmm, I originally thought that the DOC was
> >an IDE device;
> 
> No, the Disk-On-Chip is just a standard integrated circuit package that you
> connect to a memory bus.  The usual method of connection is to the ISA bus in
> a PC architecture.
> 
> >with the wear levelling alogorithm being internal to the
> >chip and provided by a BIOS extension.
> 
> Correct.  The problem comes because you have to make real mode calls to use
> the BIOS extension.  RTEMS runs in protected mode, so to use the BIOS
> extension, you would have to switch back to real mode, make the call, then
> switch back to protected mode.  Could get ugly.

Is there standard code to do this?  If so, then regardless of how ugly
it is, we could use the BIOS as a starting point.
 
> If you aren't going to use the BIOS extension that gets loaded at boot, that
> is when you need the TrueFFS filesystem code. I think that is called the
> "OSAK," the Operating System Adaptation Kit.  That is provided by M-Systems
> under license.

FWIW .. if they have one for posix threads or pSOS+, then it will
probably
just work.  A VxWorks-ish one would probably work given the
compatability
library announced on the list earlier.
 
> -- Chris Caudle

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel at OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985