Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
07/05/07 21:12
Modified:
  07/05/07 21:21

Read: times


 
#141520 - 1024 = Ki
Responding to: ???'s previous message
there is some ISO norm for that above (so, it should be KiB for kilobytes), but we all hopefully agree that it's really ridiculous.

Even if the commonly used method (k=1000 when talking SI, 1024 when talking computers) is imperfect, it's a defacto standard and those tend to work better than the written (and often artificially madeup) ones.

Now comes Steve, throwing the best known artificially madeup standard - the standard kilogram cylinder from Sevres - into my head... :-)

JW

PS. I found it, http://en.wikipedia.org/wiki/Kibibyte so it was IEC not ISO and it is kibi not kilo... But that's even more ricidulous.

List of 24 messages in thread
TopicAuthorDate
How to generate 100 Khz square wave 80C51            01/01/70 00:00      
   Tips            01/01/70 00:00      
      1 KHz            01/01/70 00:00      
         that's ...            01/01/70 00:00      
         SI Units            01/01/70 00:00      
            1024 = Ki            01/01/70 00:00      
   C interrupt overhead            01/01/70 00:00      
      RE: C interrupt overhead            01/01/70 00:00      
         and listen to the guru! :-)            01/01/70 00:00      
            several reasons            01/01/70 00:00      
               Yet another reason to avoid using HLL's!            01/01/70 00:00      
               Optimizations            01/01/70 00:00      
   Use Timer0 auo reload            01/01/70 00:00      
      using            01/01/70 00:00      
      interrupt vectoring vs. latency            01/01/70 00:00      
         Then the Interupt must be in ASM            01/01/70 00:00      
            do you mean...            01/01/70 00:00      
               No            01/01/70 00:00      
               Compiler generated IRQ vectors            01/01/70 00:00      
                  OOPS we both meant LJMP REALisr            01/01/70 00:00      
                  the original problem...            01/01/70 00:00      
         Interrupt Latency + Vectoring + Service            01/01/70 00:00      
   indufficient info            01/01/70 00:00      
   use MCS52 better option            01/01/70 00:00      

Back to Subject List