"Is the NAND flash memory controller part what may have to do with EDIG?"

There's a lot of possibility between the early days of e.Digital and today.

For the early days with regard to removable memory.....I'd say not necessarily.

Removable memory manufacturers implement three basic functions....read / write / erase. Along with the three basic standards they implement other options such as FTL(flash translation layer) for developers to rely on for file address management(CHS to LBA) format considerations. NOTE that FTL is not an OS consideration but a translation layer for other OS's to pass through. This method belongs to Msystems and was adopted as a standard and uses details for directive structure(FAT) in the process.

e.Digital interfaces the three basic functions through their own I/O devise of off chip micro controller/API/cache schemes. For the original API there were some 30 calls which may have been be expanded on by now. Through this method they format the memory under their own I/O details and do not utilize the FTL format method standard....eliminating the directive structure issues.

It's the format e.Digital implements, combined with the cache schemes that are the brains of the deal and make better use of the memory expanding on what was normally a limited use, especially for NAND.

That said, and fast forward to today....can the e.Digital issues be implemented on chip?....yes. It's what I'm waiting for. Currently, it takes the CE device manufacturer to implement the methods utilizing a Zoran microcontroller that interfaces a removable.

If memory manufacturers implement the details on their own without e.Digital authority for embedded or removable memory considerations.... replacing/bypassing ie...on chip FTL issues.....where do we catch them?

And we all know what consideration triggers a potential infringer.

doni