Conversation

Notices

1. Embed this notice
   clacke (clacke@libranet.de)'s status on Thursday, 02-Nov-2023 14:16:06 JST clacke

   Apart from the control circuitry and maybe the datastream looking different, what would be the reason for someone picking one of NAND and NOR over the other for their persistent storage?

   I was expecting them to be functionally equivalent and thought the industry had arbitrarily picked NAND over NOR decades ago, but apparently Apple Sllicon uses NOR for their recovery firmware?

   • Embed this notice
     enterprisey (enterprisey@wiki.style)'s status on Thursday, 02-Nov-2023 14:17:01 JST enterprisey

     in reply to

     @clacke this is really straining my memory, but I think NAND and NOR have different properties in terms of persistence, performance, etc and that makes each type better suited to some tasks. I have no idea how or if that's true though

     clacke likes this.
   • Embed this notice
     clacke (clacke@libranet.de)'s status on Thursday, 02-Nov-2023 14:23:52 JST clacke

     in reply to

     • Howard Chu @ Symas

     @hyc So, read vs write, interesting.

     Is this intrinsic to NOR gates somehow, or is it due to historical path dependence and conventions of how people usually put them together?

   • Embed this notice
     Howard Chu @ Symas (hyc@mastodon.social)'s status on Thursday, 02-Nov-2023 14:23:54 JST Howard Chu @ Symas

     in reply to

     @clacke NOR has always been used for firmware, because it has faster read speeds than NAND, making it practical to execute code directly from it. Conversely, NAND has faster write speed. So NOR is also used when you don't expect to write often, which again is the firmware use case.