Free
Message: sndk

They do not have to reverse engineer anything. BAN...Msystems...Sandisk...etc, know exactly what e.Digitals does.  With that,  e.Digital knows exactly what they do, where they got their start and limits of ability.

When DM goes after infringement,  they're going to be looking at the physical characteristics driving an implementation.

I push the tiny cache occurrence, for it's right up front in plain view and will lead to the reasons why it's implemented tiny... more than likely it will be SRAM.

DRAM....refresh with circuitry....power eater ...cheap...

SDRAM....refresh with circuitry...power eater...semi cheap...

SRAM...does not need refresh... expensive

 e.Digital only needs to implement a small sized amount of it, because,  of the patented environment they push through it.

If one is to take full advantage of the methods and get rid of all the trash...the cache will be a tiny SRAM.

 Saving power means getting rid of refresh and assocated circuitry.....as well as virtual management files.

 

doni

Share
New Message
Please login to post a reply