This is the mail archive of the ecos-devel@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

flash driver organization


Why are some flash drivers composed of code in include/foo.inl files (e.g.,
amd, atmel, intel 28f), and others as src/foo.c files (e.g., intel
bootblock, strata)?  Which is preferred for new drivers?

I need to cons up support for some SST parts, mainly the SST39VF400A.
SST30VF800A, and SST39VF160.  They use JEDEC-standard commands, the
same as the AMD 29x parts, but with smaller, uniform sector sizes.
Is it reasonable to simply add the SST parts to the AMD driver rather
than creating a new driver?  I see that the AMD driver already supports
some Toshiba and ST parts.  (And Fujitsu parts, but those and the AMD
parts are both made by FASL, so they're identical other than the vendor
ID.)

Thanks,
Eric


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]