Most exciting bullet point: - Eliminate all UEFI/ME post-boot activity.https://twitter.com/qrs/status/924704712896712704 …
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Is there no way to just turn down the DRAM clock to the point where the propagation delay is negligible?
I'd be happy with c.2000 DRAM performance if it meant you could get by with near-zero need for per-chipset/soc-revision firmware logic.
so e.g. J-core doesn't need to do any DRAM training, but Intel isn't going to bother with this. Hashtag economics.
I mean from a standpoint of programming x86 early boot - can you clock dram down there so naive timing params work?
And what happens after you need to clock it back up to run the OS?
Why do you need to?
Wirth's Law, our insatiable desire for speed, reducing the agonizing slowness of waiting for memory on cache miss.
Law of no premature optimization: first make it work right, then make it fast, but only if you need to.
Are you volunteering your skills to go RE MRC/FSP code? :P
AFAIK you can still do that, but then everyone will complain that it's too slow.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.