Sounds good. i was wondering about what the V2 stuff for the flash devices was, but my snapshot has no code files in those directories.
Any ideas? Thanks, And yes, CFI is where I want to go. That is how we want to reimplement our flash programming utility On Wed, 2006-11-29 at 11:29 +0000, Nick Garnett wrote: > Brian Austin <[EMAIL PROTECTED]> writes: > > > With ecos being so configurable, I do not see why flash variables have > > hard coded values. Is there an example of a configurable flash > > implementation for a certain chip flavor, or am I gonna have to come up > > with a solution myself? > > > An alternative approach is to switch to the V2 flash drivers and use > CFI to detect the flash device characteristics at runtime. This is > pretty much the default approach that we (eCosCentric) now take for > all flash support. > > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
